Heroku Outage History

27 incidents recorded over the last 365 days, 27 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Heroku status99.99% uptime history

Every Recorded Heroku Incident

Heroku incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 18, 2026Degradation StartedIncident Resolved-7 minResolved
Aug 10, 2026UpdateWe are aware of an issue that affected the ability to provision new Heroku Data add-ons. To remediate, we completed a rollback of a recent change and validated that all services have been restored. We apologize for…-6 minResolved
Aug 6, 2026UpdateBetween 11:01 UTC on August 6, 2026 and 13:10 UTC on August 6, 2026, we identified a performance issue affecting Heroku release phase deploys. During this time, some customers experienced delayed completion of release…-186 minResolved
Jul 6, 2026UpdateIncident Resolved57 minResolved
Jun 19, 2026Resolved: Heroku Retroactive Service Disruption<p>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…0 minResolved
Jun 19, 2026UpdateWe 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…-75 minResolved
Jun 9, 2026Resolved: Heroku Retroactive Feature Disruption<p>The issue is now resolved.</p>0 minResolved
Jun 9, 2026UpdateWe noted a feature disruption that impacted the Heroku Platform API that impacted multiple Heroku services, starting at 15:32 UTC. Customers may have observed issues with authentication, application deployments and…-54 minResolved
May 22, 2026Resolved: Heroku Retroactive Feature Disruption<p>The issue is now resolved.</p>0 minResolved
May 8, 2026Resolved: Heroku Service Disruption<p>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…0 minResolved
May 5, 2026Resolved: Heroku Feature Disruption<p>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…0 minResolved
Apr 29, 2026Resolved: Heroku Retroactive Feature Disruption<p>The issue is now resolved.</p>0 minResolved
Mar 12, 2026Resolved: Heroku Feature Disruption<p>The issue is now resolved.</p>0 minResolved
Feb 23, 2026Resolved: Heroku Retroactive Feature Degradation<p>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…0 minResolved
Feb 21, 2026Resolved: Heroku Platform Maintenance<p>The maintenance is now complete. All functionality has now returned to normal.</p>0 minResolved
Feb 18, 2026Resolved: Heroku Service Disruption<p>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…0 minResolved
Feb 7, 2026Resolved: Heroku Platform Maintenance<p>The maintenance is now complete. All functionality has now returned to normal.</p>0 minResolved
Feb 6, 2026Resolved: Heroku Platform Maintenance<p>The maintenance is now complete. All functionality has now returned to normal.</p>0 minResolved
Jan 15, 2026Resolved: Heroku Feature Disruption<p>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.</p> <p>We apologize…0 minResolved
Nov 4, 2025Resolved: Heroku Feature Disruption<p>This has been resolved.</p>0 minResolved
Oct 20, 2025Resolved: Service Disruption on Heroku<p>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…0 minResolved
Sep 26, 2025Resolved: Issue with Heroku Platform API<p>Services restored at 18:35:30 UTC on September 26, 2025.</p>0 minResolved
Sep 24, 2025Resolved: Investigating an issue with elevated H99 Errors<p>Beginning at 23:17 UTC on September 24, 2025 and continuing until 00:39 UTC on September 25, 2025, impacted customers experienced elevated H99 errors on network runtime in US & EU. This issue is now…0 minResolved
Sep 22, 2025Resolved: Investigating an Issue with Heroku AI responses for gpt-oss-120b model<p>Engineers confirmed an issue with the vendor's gpt-oss-120b model has been restored.</p>0 minResolved
Sep 16, 2025Resolved: Issue with DNS for New Apps and Domains<p>The upstream DNS issue impacting Heroku has been resolved. New apps and domains created during and after the time of will resolve effectively within normal DNS timeframes in all regions. Customers should no…0 minResolved
Sep 9, 2025Resolved: Investigating increased dyno relocations in Cedar Common Runtime<p>A kernel update has been deployed to all Common Runtime regions. Dyno relocations have resumed regular activity levels.</p>0 minResolved
Sep 9, 2025Resolved: Issue with Cedar Private Spaces<p>The incident is now resolved.</p>0 minResolved

How to Read This Heroku Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Heroku acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Heroku outage in this window ran 57 min, against a mean recovery of 3 min. If you depend on Heroku in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.