Provider
HerokuIncident detail
Heroku Service Degradation
Resolved incidentMinor1 affected service
Timeline window
to
Get alerted the next time Heroku breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Investigating
We've identified a service degradation impacting Private Spaces in the Tokyo region due to an issue with an upstream cloud provider. Customers may be unable to restart dynos or scale up, because new instances can't boot. Running dynos are not expected to be impacted. We are working with the provider to monitor recovery. We'll provide an update in 60 minutes or sooner if additional information becomes available.
Monitoring
We are continuing to monitor a service degradation impacting Private Spaces in the Tokyo region due to an issue with an upstream cloud provider. The provider is reporting partial recovery, but some customers may still be unable to restart dynos or scale up. Running dynos are not expected to be impacted. We'll provide an update in 60 minutes or sooner if additional information becomes available.
Monitoring
We are continuing to monitor a service degradation impacting Private Spaces in the Tokyo region due to an issue with an upstream cloud provider. The provider reports continued progress toward recovery, but some customers may still experience failures when restarting dynos or scaling up. Running dynos are not expected to be impacted. We'll provide an update in 60 minutes or sooner if additional information becomes available.
Resolved
Incident resolved.
Monitoring
Beginning at 15:30 UTC and continuing until 20:31 UTC on November 11, 2026, Private Spaces customers in the Tokyo region may have been unable to restart dynos or scale up due to an issue with an upstream cloud provider. Running dynos were not impacted. The issue has been resolved and the service is operating normally.
Keep exploring
More from Heroku
Neighboring incidents on Heroku's timeline and the rest of their record on OutageDeck.