Loading status…
Loading status…
Heroku status · Hosting & Platforms · checked (21s ago)
No — Heroku is not down. All Heroku systems are reported operational.
According to Heroku's official status page, Heroku was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Heroku's feed reported no outage in 100.00% of our checks.
Everything above is read from Heroku's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Heroku in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Heroku is a platform-as-a-service for running applications from a Git push, with add-ons for Postgres, Redis and a large third-party marketplace. Long the default answer for deploying a web app without managing servers.
Heroku's status API reports two environments separately — Production and Development — and isuptime reads the Production one, since that is what running applications depend on. Heroku's colour scheme is worth knowing: green is fine, blue means maintenance, yellow is degraded and red is an outage. isuptime treats maintenance as degraded rather than as an outage, because scheduled work is announced and expected.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Heroku's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Heroku was down.
9 other services isuptime tracks were also reporting a problem as of the same check, 21s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Heroku's status endpoint.
Every incident Heroku has published in the last 12 months.
Heroku has not published a single incident in the last 12 months. That is a statement about Heroku's posting habits as much as its reliability — a status page only records what its owner decides to record.
Check `heroku logs --tail` for your app before assuming a platform problem: an H10 app crash, an H12 request timeout at 30 seconds, or an R14 memory quota exceeded are all your dyno rather than Heroku. Eco dynos sleep when idle and are slow on the first request. Add-on outages are posted by the add-on provider, not on Heroku's status page.
Heroku is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.