Compare the status, incidents stats and history between AWS 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.
We are investigating connectivity issues affecting instances in a single Availability Zone (apne1-az4) in the AP-NORTHEAST-1 Region.
We can confirm increased latencies and increased API error rates for Amazon Bedrock when using Titan, Cohere and Mistral models in the US-EAST-1 Region. We can confirm the impact is related to the ...
We are investigating increased API error rates for the EC2 APIs in the SA-EAST-1 Region. This is mainly affecting the RunInstance API. During this time, customers may receive a 500 Response from th...
Beginning at 19:37 PM UTC on April 9, 2025 and continuing until 19:49:15 PM UTC on April 9, 2025, Heroku Platform API was unavailable during automatic database failover. During this time some reque...
Engineers are investigating an issue with high request latencies and reduced availability for HTTP requests on custom domains for a subset of US Common Runtime customers.
Beginning at 16:30 UTC on March 25, 2025, some API events are not being captured in application logs. These log lines are proceeded by the `app[api]` identifier and include details of deploys, rest...
14-day free trial · No credit card required · No code required