Heroku status: is it down right now?
Our own check of heroku.com from Europe and the US, every 3 minutes, with recent history.
heroku.com responded. The page answered normally in 82 ms.
heroku.com responded.
The page answered normally in 82 ms.
Checked (2 minutes ago) from Europe and the US, automatic every 3 minutes.
Run a website? Hear about it before your visitors do.
Heroku is up right now. Visual Sentinel watches your own site the same way and alerts you when a check fails or the page looks broken. Add your address and we'll check it now. No account needed.
This checks the response from heroku.com. It does not test playback, login or every Heroku feature.
Heroku status history
Our own checks from Europe and the US. Green means every check passed, amber means some checks failed, red means most checks in that period failed.
Outages our checks detected
None since Oct 13. A problem has to fail two checks in a row before we record it.
Watch your own site
This page is for their outage. Your own site can fail the same way. See its first check free, then try a paid plan for 7 days (card required).
Monitor my siteabout this service
About Heroku
Heroku is a platform-as-a-service owned by Salesforce, running Rails, Node, Python, Java, PHP, Go, and other app stacks with managed add-ons for PostgreSQL, Redis, Kafka, and hundreds of third-party services. Outages typically affect the dyno runtime (apps crash or fail to start), Heroku Postgres (database connections fail or slow), the build system (deploys queue up), Heroku CI, or the Platform API (breaks automation and CLI operations). Because Heroku hides infrastructure from developers, outages are more painful than on raw AWS since you cannot mitigate from below the platform layer.
The official Heroku status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours.
outage patterns
How Heroku outages affect production workloads
Developer-platform outages have outsized impact because they cascade. When Heroku is degraded, every customer's build pipeline, deploy hook, or webhook delivery can stall, and the failure mode often looks like a customer problem before engineers realize the dependency is the cause. CI runs hang, status checks never report, and queued jobs pile up silently.
The live check above provides independent public-endpoint evidence from EU and US, including status and response timing. That helps separate a broad reachability problem from a local client issue, but it does not execute your private API call, build, webhook, or deploy. Test the exact dependency path before attributing the incident to Heroku.
Common signs Heroku is having issues
- API rate limits returning earlier than the documented thresholds
- Webhook deliveries showing 5xx errors or unusual latency tail
- Deploy or build hooks accepted by Heroku but never firing downstream
- OAuth or token endpoints failing intermittently for the same client credentials
What to do when Heroku is degraded
When Heroku is having trouble, the fastest mitigation is usually feature-flagging the dependency off if your application can degrade gracefully. Check the multi-region results on this page first; if both regions report healthy but your application still sees failures, the issue is likely your network path or DNS, not Heroku itself.
monitor 24/7
Monitor Heroku automatically.
Get independent uptime alerts when the public Heroku endpoint fails a confirmed check. Solo and Starter check every 5 minutes; Business and Agency check every 60 seconds.
5-minute checks from Solo
Business and Agency support 60-second uptime checks.
Multi-region
EU & US checks. Catch regional outages.
Alerts where you work
Email and push on every plan, plus team and incident channels by plan.
free first check · 7-day trial, card required · from $15/month
why independent monitoring
Provider status references
and endpoint checks answer different questions.
Independent endpoint evidence
The regional check can show that a public endpoint is failing before or after a provider posts broader incident context. It does not validate every product subsystem.
Scheduled alerts
Monitor Heroku on your plan interval and route confirmed endpoint failures through the notification channels available to your workspace.
Multi-region verification
EU and US results can reveal a regional difference in public-endpoint reachability. Confirm the exact workflow and provider region you use.
Historical data
Track Heroku uptime over time. See trends, identify recurring issues, and make informed decisions about your dependency.
Frequently asked questions
Is Heroku down right now?
See the latest check of heroku.com and its timestamp at the top of this page. If Heroku is down, you can also check the official status page for extra context.
How do I check if Heroku is having issues?
This page checks the public Heroku endpoint from EU and US. You can also monitor that endpoint on a schedule and receive confirmed-failure alerts through the channels available on your plan. Test the exact provider feature you use for a complete diagnosis.
How can I get alerted when Heroku goes down?
Add heroku.com to Visual Sentinel and its first check is free. To keep monitoring, start a 7-day trial (card required) or subscribe now: Solo and Starter check every 5 minutes, Business and Agency every 60 seconds, with email, push and chat alerts.
Where can I find Heroku outage context?
The official Heroku status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Visual Sentinel checks the public Heroku endpoint independently from EU and US. Paid Business and Agency plans support 60-second uptime checks.
Can I still deploy to Heroku during a build-system outage?
No. Builds run on Heroku's build infrastructure; a build-system outage queues all incoming deploys. Running apps continue to serve traffic, but you cannot ship new code. Consider releasing a pre-built container via Container Registry if you need to bypass the build queue in an emergency.
Does a Heroku Postgres outage affect my app even if the dyno is healthy?
Yes, if your app depends on the database. Well-architected apps with read replicas or graceful-degradation patterns weather brief database incidents. Apps with a single primary and no caching fail as soon as the connection pool exhausts.
Often checked together with Heroku
Many sites and apps run on these platforms, so one cloud problem can affect services that look unrelated.