Skip to main content
Heroku logo

Is Heroku Down?

No — Heroku is up

Reachable from all 8 checked regions

Average response time: 336ms

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
579ms
Avg response, 30 days

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

30-day history

62-day clean streak
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 30 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 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.

dfw
232ms
DNS 194ms TCP 1ms TLS 4ms TTFB 228ms
ewr
112ms
DNS 73ms TCP 2ms TLS 6ms TTFB 104ms
fra
692ms
DNS 28ms TCP 1ms TLS 4ms TTFB 329ms
gru
426ms
DNS 274ms TCP 1ms TLS 7ms TTFB 420ms
iad
174ms
DNS 148ms TCP 2ms TLS 5ms TTFB 164ms
jnb
556ms
DNS 356ms TCP 0ms TLS 6ms TTFB 546ms
lax
212ms
DNS 177ms TCP 2ms TLS 6ms TTFB 203ms
lhr
288ms
DNS 23ms TCP 1ms TLS 4ms TTFB 279ms

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 up to 17 cities across three 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 — the most recent check ran from 8 of them.
  • 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 up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required