Compare the status, incidents stats and history between AWS and Vercel
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...
We have observed authentication issues to private registries using npm access tokens. Affected users may see 4xx errors when installing private packages. Manually regenerating tokens appears to res...
We're investigating some monthly performance emails that were sent in error.
We are currently investigating reports of elevated projects being paused despite the specified Spend Limit not being reached, resulting in incorrect notifications and paused deployments. This does ...
14-day free trial · No credit card required · No code required