outages.live
Live
HerokuIncident · 2026-08-06 16:17 UTC

Heroku Retroactive Feature Degradation

ResolvedOfficial update

Between 11:01 UTC on August 6, 2026 and 13:10 UTC on August 6, 2026, we identified a performance issue affecting Heroku release phase deploys. During this time, some customers experienced delayed completion of release phase commands during deploys, with some remaining in an `release phase executing` state longer than expected. We have confirmed that the issue is resolved. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

The latest update from Heroku.

State

Resolved

Started

87 d ago

2026-08-06 16:17 UTC

Lasted

1 min

until 2026-08-06 16:17 UTC

Worst impact

Degraded

Timeline

3 updates
16:1716:1816:1816:1816:18
DegradedNoticeUpdate postedTimes in UTC

Retroactive

1 min 0%

Resolved

1 min 100%

Updates

Times in UTC

As posted by Heroku

Update2026-08-06 16:19 UTC

Between 11:01 UTC on August 6, 2026 and 13:10 UTC on August 6, 2026, we identified a performance issue affecting Heroku release phase deploys. During this time, some customers experienced delayed completion of release phase commands during deploys, with some remaining in an `release phase executing` state longer than expected. We have confirmed that the issue is resolved. We apologize for how you and your business may have been affected by this incident. We will thoroughly investigate the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

Resolved2026-08-06 16:17 UTC

The issue is now resolved.

Retroactive2026-08-06 16:17 UTC

Heroku engineers are investigating an issue retroactively.

Affected components

1
Apps

Heroku in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

5

Median duration

52 min

This incident

100% 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 52 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.

Resolvedresolved 4 d ago

Heroku·Heroku Feature Degradation

Incident resolved.

Resolvedresolved 38 d ago

Heroku·Heroku Service Degradation

Engineers have remediated the issue.

Resolvedresolved 68 d ago

Heroku·Heroku Retroactive Feature Degradation

The issue is now resolved.

Resolvedresolved 75 d ago

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.cc/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.cc/feed.xml?providers=heroku
Slack
/feed subscribe https://outages.cc/feed.xml?providers=heroku

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane