# Heroku status

> Is Heroku down? Live status, uptime history, and per-region response times, measured by our own probes since August 2026.

Published: 2026-08-18 | Canonical: https://yoping.me/status/heroku

## How we check Heroku

We watch api.heroku.com from all five of our probe regions, every 2 minutes. A region that sees a failure does not make this page say "down" on its own: a second region has to agree first, the same confirmation rule every YoPingMe monitor uses.

We pin the exact response code the platform API returns to an unauthenticated request rather than assuming any 2xx, since a bare request with no auth token is normally and correctly rejected, and a monitor that reads that rejection as downtime would misreport every healthy day.

The live board - the current verdict, 24-hour, 7-day, and 30-day uptime, and per-region response times - is on the HTML page at https://yoping.me/status/heroku. Those numbers change too fast to repeat honestly in a static mirror, so where an answer below says "the board above", it means that page.

## What is Heroku?

Heroku was one of the earliest platforms to let a developer deploy a web
application with a git push rather than provisioning servers by hand, and
a meaningful number of production applications, from early-stage
startups to established products that never migrated off it, still run
on it today. A deploy builds a container from your code, Heroku schedules
it onto one or more dynos, and its router directs incoming traffic to
whichever dynos are healthy.

That router is the part most worth understanding when something goes
wrong. Because Heroku sits between the internet and your actual
application code, a platform-level incident can make an app fully
unreachable even though nothing in your own code changed and no deploy
went out. From the outside, that looks identical to your app being
broken, an error page or a connection that never completes, which is
exactly why it is worth checking the platform's own health before
spending an hour debugging code that was never the problem.

Heroku incidents tend to be scoped rather than platform-wide: a specific
region's routing degraded, a particular add-on unavailable, or elevated
build times for new deploys, rather than every hosted application going
dark at once. A stuck deploy is its own distinct failure mode worth
knowing about too, since a build that hangs partway through can leave an
app serving a stale, previously-deployed version indefinitely while
looking, to a quick check, like nothing is wrong.

If your app is down and the board above shows Heroku itself healthy, the
more likely explanations are a crashed dyno, a bad release that needs
rolling back, or a downstream dependency of your own, such as a database
connection limit, rather than the platform.

## Frequently asked questions

### Is Heroku down right now?

Check the board above; it reflects our own probes, refreshed every couple of minutes from all five of our regions.

### My app hosted on Heroku is not loading. Is that a platform-wide outage?

Not necessarily. A single dyno crashing, a bad deploy, or a database connection limit hit on your own app can each look identical to a platform outage from the outside. If the board above shows Heroku healthy, check your own app's logs before assuming the platform is at fault.

### Does a Heroku incident usually take down every app on the platform?

Rarely all at once. Incidents are more commonly scoped to a specific component, the Common Runtime, a particular region, or a specific add-on, rather than every hosted app everywhere failing simultaneously.

### What is the difference between this page and Heroku's own status page?

Theirs reflects incidents their own team has confirmed and posted. Ours reflects what our own probes measure from outside Heroku's infrastructure, on a fixed schedule regardless of whether an official update has gone up yet.