Is Heroku down?
Vendor reports no incidentWhat Heroku reports
Heroku reports no incident on its status page.
As of the last successful poll, 2026-10-22 23:40 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked 2 minutes ago
Our checks of Heroku pass from all 10 regions we check.
As of Oct 22, 2026, 11:47 PM UTC, RealUptime's checks of Heroku passed in all 10 regions that returned a reading.
Heroku publishes no status feed we can read, so the only reading here is our check reading on the left.
Heroku response time, by region
Check your own site while you wait on Heroku
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Heroku. It cannot diagnose Heroku's own systems.
What we measured, function by function
Heroku answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
Email me when Heroku reports an incident on its status page, and again when it reports it resolved.
Get an email when Heroku reports an incident
Email me when Heroku reports an incident on its status page, and again when it reports it resolved. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 517msstatus code: 400checked: Oct 22, 2026, 11:44 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Heroku normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 808msstatus code: 400checked: Oct 22, 2026, 11:47 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Heroku normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 158msstatus code: 400checked: Oct 22, 2026, 11:29 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Heroku normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 944msstatus code: 400checked: Oct 22, 2026, 11:38 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Heroku normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 1562msstatus code: 400checked: Oct 22, 2026, 11:33 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Heroku normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 513msstatus code: 400checked: Oct 22, 2026, 11:40 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Heroku normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 565msstatus code: 400checked: Oct 22, 2026, 11:44 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Heroku normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 919msstatus code: 400checked: Oct 22, 2026, 11:39 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Heroku normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 1110msstatus code: 400checked: Oct 22, 2026, 11:41 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Heroku normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 1046msstatus code: 400checked: Oct 22, 2026, 11:43 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Heroku normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Heroku, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Heroku yet, which is not evidence that nothing is wrong.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Heroku since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Heroku covering any window you pick, with our check readings and Heroku's own claim at the time, side by side.
Full check history for Heroku: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversPut this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/heroku)<a href="https://realuptime.io/outages/heroku"><img src="https://realuptime.io/outages/heroku/badge.svg?days=30" alt="Heroku uptime by RealUptime's checks" height="20"></a>The badge shows the share of our checks that passed over the last 30 days. The window is printed on it, so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
To cite this page: RealUptime, "Is Heroku down?", https://realuptime.io/outages/heroku. The readings change with every check, so give the date you read them.
Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.
What we check
What our check can and cannot see
A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.
Host checked: api.heroku.com