Live / Heroku / Incident
Heroku: Resolved: Heroku Service Degradation
Heroku · heroku.comResolved2026-11-11 21:15 UTC
Public — what happened
Summary
Heroku said customers using Private Spaces in its Tokyo region could have trouble restarting dynos or adding capacity, because new instances could not start. The company attributed this to a problem at an upstream cloud provider and said dynos that were already running were not affected. Heroku posted hourly updates saying the provider was reporting gradual recovery. In its final update it said the problem ran from 15:30 to 20:31 UTC on November 11, 2026, and that service was back to normal.
Timeline
- Started — 2026-11-11 18:18 UTC
- Update — 2026-11-11 18:16 UTC (3 updates)
- Resolved — 2026-11-11 21:15 UTC · 2h 57m 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
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.