Vendor record
Heroku
Checked
Front door check counts and Heroku’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Heroku endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- api.heroku.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Heroku product, region or your app worked.
How we count front door checksHeroku says
Incident posts from Heroku’s status page, with its titles, impact levels and times. They say what Heroku chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
7
incidents Heroku posted, last 180 days
Median recorded duration: 1h 17m. From 7 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Heroku Feature Degradation
MinorHeroku’s postStarted, per Heroku
Closed in our record(1h 34m)
Heroku Service Degradation
MinorHeroku’s postStarted, per Heroku
Closed in our record(1h 17m)
Heroku Feature Degradation
MinorHeroku’s postStarted, per Heroku
Closed in our record(24m)
Heroku Service Disruption
MinorHeroku’s postStarted, per Heroku
Closed in our record(1h 17m)
Heroku Retroactive Service Disruption
MinorHeroku’s postStarted, per Heroku
Closed in our record(33m)
2 older records
Heroku Service Degradation
MinorHeroku’s postStarted, per Heroku
Closed in our record(8h 44m)
Heroku Feature Disruption
MinorHeroku’s postStarted, per Heroku
Closed in our record(1h 52m)
Your code, your dependencies
See which of your code paths call Heroku
Connect GitHub or GitLab to find where your public or private repository uses Heroku. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Heroku status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Heroku currently down?
Heroku's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Heroku last have an outage?
The most recent closed incident record began 22 days ago and spans 1h 34m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Heroku?
No. CheckUpstream checks Heroku’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Heroku in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Heroku?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.