CheckUpstream has measured Heroku at 99.878% uptime over the last 90 days and 99.970% over the last 12 months. 6 incidents were recorded in the past 12 months; the most recent resolved 22 days ago after 1 hour. Status signals are polled from Heroku's official status feed, alongside independent probes and community reports.
1 year uptime
99.970%
364 of 365 days clean · 2h 37m total downtime
Fewer incidents in the last 30 days than 27% of 234 tracked services.
If you're a paying Heroku customer, outages in these windows may count against Heroku's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/heroku/badge.svg
Frequently Asked Questions
›Is Heroku currently down?
Heroku is currently Operational. CheckUpstream tracks Heroku in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
›When did Heroku last have an outage?
Heroku's last resolved incident started 22 days ago and lasted 1h 17m (degraded performance).
Heroku's 30-day customer-perceived uptime is 99.970%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
›How do I monitor Heroku in production?
Sign up to CheckUpstream and add Heroku to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
›How does CheckUpstream track Heroku?
We poll Heroku's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.