Is Heroku down?
No, Heroku is not down.
Heroku’s status page reports no incidents, api.heroku.com responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsstatus.heroku.com
- Reachable6 of 6 regionsPlatform API · api.heroku.com
- Reports in the last hour0Normal
Heroku’s status page
From status.heroku.com. Read at
- AppsOperational
- DataOperational
- ToolsOperational
Planned maintenance, : Heroku Platform Maintenance.
Not working for me
Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.
Last 24 hours
No problems in the last 24 hours, median response 203 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (api.heroku.com)
By region
| Region | Platform API api.heroku.com |
|---|---|
| N. Virginia us-east-1 | 401 · 86 ms |
| Oregon us-west-2 | 401 · 142 ms |
| Frankfurt eu-central-1 | 401 · 173 ms |
| Singapore ap-southeast-1 | 401 · 297 ms |
| Tokyo ap-northeast-1 | 401 · 196 ms |
| São Paulo sa-east-1 | 401 · 265 ms |
Two regions check Heroku every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check
Last 90 days
We have checked Heroku ourselves since Oct 28, 2026. Earlier days come from its status page.
5 days with problems in the last 90 days.
Recent incidents
Incidents: 0 in the last 30 days and 5 in the last 90, lasting a median of under 1 min.
- Heroku Feature DegradationDegraded1 h 27 min
- Heroku Service DegradationDegraded51 min
- Heroku Retroactive Feature DegradationDegradedunder 1 min
- Heroku Feature DegradationDegradedunder 1 min
- Heroku Retroactive Feature DegradationDegradedunder 1 min
If Heroku isn’t working for you
Heroku is Salesforce's platform as a service for running web apps on managed containers called dynos, with Postgres and add-ons.
Common Heroku errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
H10 - App crashed | A web dyno crashed, or the web dyno timed out while booting. | Your side | Run heroku logs --tail to find the crash and fix the startup error. Source |
H12 - Request timeout | An HTTP request took longer than 30 seconds to complete, so the router returned an error. | Your side | Move slow work to background jobs and check slow queries. Source |
H14 - No web dynos running | The app has no web dynos scaled up. | Your side | Scale web dynos up, for example heroku ps:scale web=1. Source |
R14 - Memory quota exceeded | A dyno is using more memory than its size allows and is swapping. | Your side | Reduce memory use or move to a larger dyno. Source |
H99 - Platform error | An internal error in the Heroku platform; Heroku says H99 and R99 are the only codes that represent platform errors. | An outage | No action needed from you: try again in a minute and check status.heroku.com. Source |
Is it just you?
- Run heroku logs --tail: H and R error codes tell you whether the problem is your app or the platform.
- H99 and R99 are platform errors; nearly every other code points at your app or its configuration.
- Check heroku ps to make sure web dynos are running.
- Check status.heroku.com for incidents affecting your region or add-ons.
Alternatives to Heroku
Questions
Your web dyno crashed or failed to start. Heroku logs show the underlying exception; it is almost always in the app or its configuration.
H99 and R99 are platform errors. Most other H and R codes describe your app's behavior, such as crashes, timeouts or memory use.
Sources: devcenter.heroku.com, status.heroku.com
Get alerted when Heroku breaks your app.
If your product or your team depends on Heroku, its outage is your outage, and your users will blame you, not Heroku. Point a Site Qwality monitor at the Heroku endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.