Live  /  Heroku  /  Incident

Heroku: Resolved: Heroku Service Disruption

Heroku · heroku.comResolved2026-05-08 18:53 UTC
Public — what happened

Summary

Heroku reported a service disruption that began on 2026-05-08 at about 03:55 UTC and affected its databases and web applications. In its final update at 18:53 UTC, the company said a fix had been applied to all remaining affected customers and that both services were fully working again for everyone. Heroku apologized and said it would carry out a full investigation to determine the trigger and underlying cause, and to set out steps to prevent a repeat; no cause had been stated in the text provided.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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

The full archive is on the Heroku status & history page.

Related: Heroku status & history. SquidGrid is not affiliated with Heroku.