Skip to main content

Is Heroku Down?

No — Heroku is up

Reachable from all 8 checked regions

Average response time: 332ms

Last checked · checks run every 6 hours

Official status page: https://status.heroku.com

Heroku uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
459ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 11 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

11-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: blocked from automated checks
Aug 13: 100.00% uptime, 8 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 31 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 37 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn
701ms
DNS 0ms TCP 5ms TLS 10ms TTFB 337ms
bom
675ms
DNS 1ms TCP 2ms TLS 6ms TTFB 669ms
cdg
280ms
DNS 0ms TCP 2ms TLS 4ms TTFB 275ms
dfw
44ms
DNS 0ms TCP 0ms TLS 6ms TTFB 40ms
ewr
37ms
DNS 0ms TCP 1ms TLS 6ms TTFB 32ms
fra
668ms
DNS 0ms TCP 1ms TLS 4ms TTFB 302ms
gru
493ms
DNS 0ms TCP 3ms TLS 7ms TTFB 483ms
iad
23ms
DNS 1ms TCP 1ms TLS 4ms TTFB 16ms
jnb
443ms
DNS 0ms TCP 0ms TLS 5ms TTFB 429ms

What Heroku does

Heroku is a platform-as-a-service, owned by Salesforce, that runs applications from a git push without the operator managing servers. Its status page groups everything into three systems: Apps, covering running dynos and the router; Data, covering Heroku Postgres, Redis and Kafka; and Tools, covering the CLI, dashboard and build pipeline.

What an outage looks like

Deployed applications return H-series router errors, most often H10 app crashed, H12 request timeout or H99 platform error, which appear in the Heroku logs rather than in application code. Builds queue without starting, or fail at the release phase. Database-backed pages break while static routes still answer, which points at Data rather than Apps.

What to do about it

Read status.heroku.com and note which of the three systems is affected, because Apps, Data and Tools fail independently: a Tools incident blocks deploys while running applications serve traffic normally. Do not roll back a release to fix an H99, which is a platform error rather than a fault in your code. Heroku exposes the same state as JSON at status.heroku.com/api/v4/current-status.

Is it down for everyone, or just you?

If this page says Heroku is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Heroku outage FAQ

Is Heroku down or has my app crashed?
Heroku's H-codes distinguish them. H10 app crashed usually means your process exited, while H99 platform error is Heroku's own fault. Check status.heroku.com against your log timestamps: an H10 during a green Apps line points at your dyno, and a cluster of H99s or router timeouts across unrelated apps points at the platform.
My app is running but I cannot deploy. Is that the same outage?
Probably not. Heroku reports Tools separately from Apps, and the build pipeline, CLI and dashboard sit under Tools. A Tools incident stops new deploys and dashboard access while already-running dynos keep serving traffic normally. Check the Tools line rather than assuming a deploy failure means your users are affected.
Does a Heroku outage affect my Postgres database?
Not necessarily. Data is its own system, covering Heroku Postgres, Redis and Kafka, and it can be healthy while Apps is degraded, or the reverse. An app that returns errors only on database-backed routes points at Data. Read both lines during an incident, because the remedy differs: a Data fault is not fixed by restarting dynos.
How long do Heroku outages usually last?
Heroku does not publish a target restoration time, and duration varies with the system affected. The status page posts incident updates as they develop and keeps a public history, along with scheduled maintenance announced in advance. Following the incident thread is more reliable than estimating from past outages, since the causes differ each time.

How we measure this

  • We request Heroku's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Heroku publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Heroku goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required