Resolved: Heroku Service Disruption
Incident resolved.
Incident resolved.
We noted an issue that impacted Heroku Platform API services in all regions. Customers may have experienced broken pipeline API calls to ‘pipelines/:id/latest-builds’, and issues viewing the pipeline dashboard. We confirmed this incident was due to a recently deployed change, and have reverted this change to resolve the issue. We will continue to monitor the environment to ensure stability and pre…
The issue is now resolved.
The issue is now resolved.
We have successfully applied the fix to all remaining affected customers. Heroku databases and web applications are now fully operational for all customers. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.
The issue is now resolved.
The issue is now resolved.
Customers using Heroku in the Common Runtime may have experienced intermittent dyno disruptions earlier today between 17:50 UTC and 20:24 UTC. The issue has been resolved after we disabled a related service and rolled back a recent change. We’re validating the update in lower environments and will continue monitoring for stability.
The maintenance is now complete. All functionality has now returned to normal.
We’ve confirmed that the solution implemented to mitigate the issue causing the service disruption was successful. Engineers have observed that the service is stable and have resolved the incident. Customers should no longer see any impact. We will fully investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future. We apolo…
The maintenance is now complete. All functionality has now returned to normal.
The maintenance is now complete. All functionality has now returned to normal.
At 13:46 UTC, on January 15, 2026, teams completed validation and confirmed the incident has been resolved after the new certificate was propagated to all impacted environments. We apologize for how this incident may have affected you and your business. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a rep…
This has been resolved.
We sincerely apologize for the impact this issue caused you and your business. Our goal is to provide world-class service to our customers, and we are continuously assessing and improving our tools, processes, and architecture to provide our customers with the best service possible. Please find the Root Cause Analysis here. If you have additional questions or need further support, please open a ca…