Heroku Status

Last updated February 15, 2022

Heroku Status provides the current status and incident history report for the Heroku platform. The status site covers all runtimes, as well as key add-ons necessary for smooth operation of production applications.

Accessing Heroku Status

The current status and history of platform issues is shown at:

https://status.heroku.com

The heroku CLI can be used to ascertain the current status:

$ heroku status
=== Heroku Status
Apps:      No known issues at this time.
Data:      No known issues at this time.
Tools:     No known issues at this time.

Status information

The status site includes the current status of the platform, and the most recent incidents, all broken down into three categories: apps, data, and tools.

Incident reporting will refresh every 30 seconds.

Apps and Runtime issues

Apps and Runtime issues are those that affect running, stable applications that have at least two web dynos or use a non-hobby database (or no database at all).

Components include:

  • Dynos
  • Routing
  • Scheduler

Data Service issues

Data Service issues are those that affect the health of Heroku data products.

Components include:

  • Heroku Postgres
  • Heroku Redis
  • Heroku Connect

Tools issues

Tools issues are those that affect developer workflow and management tools.

Components include:

  • Git-push deployments and the Deployment API
  • GitHub Sync
  • API / CLI / Heroku Dashboard (scaling up/down, changing configuration, etc.)
  • Logging
  • Unidling free dynos

The types of platform work that can result in notifications, and the types of notifications are documented in Platform Updates, Maintenance and Notifications.

Getting notified when there is an incident

You can sign up for email or SMS alerts when there are issues affecting the platform. Go to the status site and click on Subscribe. You can also follow the twitter feed, RSS feed, or connect to the status site via its API.

Actions to take when you suspect an outage

Check the status site if there is a current incident. If nothing is reported, or if you are experiencing something different than what is reported, contact our support team.

Heroku Status API v4

Get current status

The Heroku Status API has CORS support, allowing client-side JavaScript requests.

$ curl "https://status.heroku.com/api/v4/current-status"
{"status":[{"system":"Apps","status":"green"},{"system":"Data","status":"green"},{"system":"Tools","status":"green"}],"incidents":[],"scheduled":[]}

Get list of issues (optionally limited by date or count)

$ curl "https://status.heroku.com/api/v4/incidents?since=2019-11-01&per_page=1"
[{"id":1924,"title":"Logs for some customers were not forwarded to log drains.","state":"resolved","created_at":"2019-11-05T00:00:00.000Z","updated_at":"2019-11-05T00:43:21.770Z","resolved":false,"href":"https://status.heroku.com/api/v4/incidents/1924","full_url":"https://status.heroku.com/incidents/1924","duration":2460,"resolved_at":"2019-11-05T00:41:00.000Z","review":false,"systems":[{"name":"Tools","status":"green","services":["Tools"]}],"tags":["US","US"],"updates":[{"id":6131,"created_at":"2019-11-05T00:41:00.000Z","updated_at":"2019-11-05T00:43:25.093Z","incident_id":1924,"contents":"This incident has been resolved.","title":"Logs for some customers were not forwarded to log drains.","update_type":"resolved","systems":[]},{"id":6130,"created_at":"2019-11-05T00:00:00.000Z","updated_at":"2019-11-05T00:46:01.188Z","incident_id":1924,"contents":"From Oct 30 13:00 UTC until Nov 2 14:00 UTC logs for some customers in US Common Runtime and Virginia Private Spaces were not forwarded to the configured log drain, due to an internal issue with the logging systems dropping logs.","title":"Logs for some customers were not forwarded to log drains.","update_type":"retroactive","systems":[{"name":"Tools","status":"green","services":["Tools"]}]}]}]

Get a single issue by ID number

$ curl "https://status.heroku.com/api/v4/incidents/1924"
{"id":1924,"title":"Logs for some customers were not forwarded to log drains.","state":"resolved","created_at":"2019-11-05T00:00:00.000Z","updated_at":"2019-11-05T00:43:21.770Z","resolved":false,"href":"https://status.heroku.com/api/v4/incidents/1924","full_url":"https://status.heroku.com/incidents/1924","duration":2460,"resolved_at":"2019-11-05T00:41:00.000Z","review":false,"systems":[{"name":"Tools","status":"green","services":["Tools"]}],"tags":["US","US"],"updates":[{"id":6131,"created_at":"2019-11-05T00:41:00.000Z","updated_at":"2019-11-05T00:43:25.093Z","incident_id":1924,"contents":"This incident has been resolved.","title":"Logs for some customers were not forwarded to log drains.","update_type":"resolved","systems":[]},{"id":6130,"created_at":"2019-11-05T00:00:00.000Z","updated_at":"2019-11-05T00:46:01.188Z","incident_id":1924,"contents":"From Oct 30 13:00 UTC until Nov 2 14:00 UTC logs for some customers in US Common Runtime and Virginia Private Spaces were not forwarded to the configured log drain, due to an internal issue with the logging systems dropping logs.","title":"Logs for some customers were not forwarded to log drains.","update_type":"retroactive","systems":[{"name":"Tools","status":"green","services":["Tools"]}]}]}

Feedback

Log in to submit feedback.