Compare the status, incidents stats and history between Azure and Heroku
Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.
Impact Statement: As early as 22:00 UTC on 08 Jan 2025, we noticed a partial impact to some of the Azure Services in East US 2 due to a configuration change in a regional networking service. This c...
Starting at 18:44 on 26 December 2024, a power incident in a single availability zone in the South Central US region impacted the availability of multiple Azure services.Impacted ServicesVirtual Ma...
What happened?Between 18:44 UTC on 26 December 2024 and 19:30 UTC on 27 December 2024, a power incident in a single availability zone in the South Central US region impacted the availability for mu...
Beginning at 15:35 UTC on 2025-01-09, data.heroku.com is not available for customers in all regions, including Dataclips. Customers experienced redirect loops when attempting to authenticate. Our e...
Our engineers have identified the issue and are working to fix the problem with `yarn install` build timeouts in Ruby builds.
Customers experiencing build timeouts using Node.js 20 can temporarily workaround the issue by running `heroku config:set UV_USE_IO_URING=0`. Our engineers have identified the issue and are wor...
14-day free trial · No credit card required · No code required