Is Heroku down right now?
Checking…Verifying live status…
Our latest checks found Heroku responding normally. Live verification is running now.
Your report feeds the live outage-velocity detector. One click per 30 s.
Live latency (probe round-trip, ms)
User reports, last 24 hours
Outage history
last 30 days
Recent outages and issues we recorded for Heroku, based on our own checks. An episode opens on the second check that finds a problem, since a single adverse reading is not reported, and closes when a check finds the service normal again.
No problemsProblemsOutageNot monitored
What Heroku reported
last 30 days
Taken from Heroku's own published incident feed. These are their words about their own service, shown here so you can compare them with what we measured. Scheduled maintenance and test posts are filtered out.
Comments
Comments are hosted and moderated via Disqus. Spam is filtered automatically, readers can flag anything, and the thread loads only when you scroll to it so the rest of the page stays fast.
Comments are loading in our built-in box because Disqus was blocked or unavailable. Spam and abuse are filtered automatically, and comments are hidden once 3 readers flag them.
How we check Heroku
No evidence of problems with Heroku. Our last recorded check found it behaving normally. That does not rule out a fault affecting only some users or regions.
Every check runs a four-tier cascade and stops at the first tier that gives a clear answer: Heroku's official status feed, then a direct HTTP probe, then an ICMP network ping, and finally reports from visitors. The Verification tier box above tells you which one produced the verdict you are looking at. When enough separate people report a problem for it to be well outside what Heroku normally sees, that counts as evidence too, which is how a partial fault can show here before an operator's own status page catches up.
Heroku (heroku.com) is re-checked continuously, and this page picks up any change on its own, with no refresh needed.
Common Heroku problems users report
- Dynos failing to start or crashing after a deploy
- git push heroku hanging or failing to build
- Heroku Postgres connections timing out
- Dashboard and API unavailable while apps keep serving
What to do when Heroku is not working
First check the banner above. If it shows evidence of problems, the fault is most likely on Heroku's side and waiting is usually the only option. If it shows nothing wrong, run heroku logs --tail, which separates a platform error from your own application crashing on boot. Then check whether an add-on rather than Heroku is the thing failing, since each one has its own status page.
About Heroku
Heroku is a cloud platform that lets developers build, run, and scale web applications and APIs without managing infrastructure. When Heroku is down, deployed applications become inaccessible, databases go offline, and background jobs fail to execute. Users lose access to their running services and cannot deploy new code.
Official Heroku resources
Cross-check an incident with the company's own channels:
- Official Heroku status pageTheir own incident dashboard
- Heroku help centerSupport articles and contact options
- @herokustatus on XOften the fastest official acknowledgement
Frequently asked questions
Is Heroku down right now?
No. Our checks are finding no problems with Heroku right now. That verdict is live, and the banner at the top of this page carries it too. We re-check Heroku continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.
What usually goes wrong with Heroku?
The problems visitors report most often on this page are website / app down, can't connect, 5xx error pages, API errors, builds / pipelines stuck, slow or laggy and can't log in. Those are the options the report button offers for Heroku, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.
Why is Heroku failing for me when this page says it is fine?
Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With Heroku specifically, the build system, the dyno runtime, the routing layer and the add-ons are separate, and add-ons such as Postgres and Redis are run by third parties with their own status pages. Your app can serve traffic perfectly while deploys fail completely. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.
How do I tell whether it is Heroku or my own connection?
For Heroku, open your app's URL and compare it with the Heroku dashboard. The app serving while the dashboard fails is theirs and invisible to your users. The app erroring while the dashboard loads points at your dyno or an add-on. A problem that follows you across networks and devices is very unlikely to be yours.
What should I do while Heroku is down?
If this page shows evidence of problems, the fault is most likely on Heroku's side. Specifically: avoid restarting dynos repeatedly. A restart needs the platform you are waiting on, and a dyno that fails to come back leaves you worse off than one that was still serving. Read the logs before assuming the platform is at fault. Reporting it here helps other people see they are not alone.
How does status.buzz check Heroku?
Continuously, around the clock. Heroku does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe heroku.com directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what Heroku says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.
Does Heroku have an official status page?
Yes, at status.heroku.com, and it is linked further up this page. That is Heroku's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.
Is status.buzz affiliated with Heroku?
No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to Heroku or heroku.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need Heroku's own support, not us.
Other infrastructure services
Live status. Each dot updates automatically.
No comments yet. Be the first to describe what you're seeing.