Heroku lists these components: Apps.

When did the incident start and end?

It started at 2026-11-11 18:18 UTC. This page shows the end time when Heroku marks it resolved.

How do I get alerts for Heroku?

Subscribe to the Heroku live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Heroku. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

HerokuIncident ·

Heroku Service Degradation

Q: What happened?

Heroku reported "Heroku Service Degradation" on its status page at 2026-11-11 18:18 UTC. Heroku Apps do not work correctly for Private Spaces in the Tokyo region. Heroku has identified the cause as an issue with an upstream cloud provider. Heroku is working with the provider to monitor recovery.

DegradedOfficial update

Heroku Apps do not work correctly for Private Spaces in the Tokyo region. Heroku has identified the cause as an issue with an upstream cloud provider. Heroku is working with the provider to monitor recovery.

State

Open

Started

Ongoing for

31 min

Worst impact

Degraded

Timeline

1 update

18:1818:2518:3318:4118:49

DegradedUpdate postedTimes in UTC

Open

31 min 100%

Updates

Times in UTC

As posted by Heroku

Open

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.

Affected components

Apps

Heroku in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 10 min

This incident

55% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 h 26 min

median 1 h 10 min

90 days agoToday

Other Heroku incidents

All incidents

Heroku·Heroku Feature Degradation

The upstream errors have been resolved, and normal operations have been restored. This incident is now resolved.

Resolved

Heroku·Heroku Feature Degradation

Incident resolved.

Resolved

Heroku·Heroku Service Degradation

Engineers have remediated the issue.

Resolved

Heroku·Heroku Retroactive Feature Degradation

The issue is now resolved.

Resolved

Follow Heroku

Your coding agent knows when Heroku is down, and tells you when a failure is theirs, not yours. You can also get Heroku incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "heroku" and tell me if Heroku has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.live/feed.xml?providers=heroku

Slack

/feed subscribe https://outages.live/feed.xml?providers=heroku

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane