Live / Heroku / Incident
Heroku: Resolved: Heroku Feature Disruption
Heroku · heroku.comResolved2026-05-05 18:03 UTC
Public — what happened
Summary
Heroku reported a feature disruption that it listed as starting at 14:57 UTC on May 5, 2026. In its final update at 18:03 UTC, the company said further investigation showed that impact had begun at a different time than it first understood. Heroku said it revised the start time in its status post to better match when customers may have first noticed problems, and it apologized for any confusion. The post does not describe which features were affected or name a cause, and the incident is marked resolved.
Timeline
- Started — 2026-05-05 14:57 UTC
- Resolved — 2026-05-05 18:03 UTC · 3h 06m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Heroku against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Heroku: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Heroku report →
More from Heroku