Live  /  Heroku  /  Incident

Heroku: Resolved: Heroku Service Disruption

Heroku · heroku.comResolved2026-02-18 03:04 UTC
Public — what happened

Summary

Heroku reported a service disruption that began on February 18, 2026 at 01:49 UTC, though it did not say which parts of its platform or which customers were affected. The company said a fix it put in place worked, the service had stabilized, and the incident was marked resolved at 03:04. Heroku said it had not yet confirmed what triggered the problem and planned to look into the cause and steps to prevent it from happening again.

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.