Live  /  Heroku  /  Incident

Heroku: Resolved: Heroku Retroactive Feature Degradation

Heroku · heroku.comResolved2026-02-23 23:31 UTC
Public — what happened

Summary

Heroku said that some customers running apps in its Common Runtime may have had intermittent dyno disruptions earlier on 2026-02-23, between 17:50 UTC and 20:24 UTC. The company reported the problem as resolved at 23:31 UTC, saying it turned off a related service and rolled back a recent change. Heroku added that it is testing the update in lower environments and will keep watching for stability.

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.