Compare the status, incidents stats and history between AWS and Netlify
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.
8:17 PM PDT We are investigating increased API error rates for DetachVolume, AttachVolume, and AssociateIamInstanceProfile in the AP-SOUTH-1 Region. We have identified the root cause and are worki...
3:57 AM PDT We are experiencing delays creating, deleting, and updating Route 53 health checks. This is also affecting provisioning and scaling workflows for services like ELB, EKS, and RDS that ...
4:01 AM PDT We are investigating increased API error rates in the AF-SOUTH-1 Region. Existing instances are unaffected. 4:21 AM PDT We are experiencing elevated API errors and latency with the...
From 21:02 UTC to 21:06 UTC there were increased errors on our Origin Servers, Standard and High-Performance Edge Network, API, and Build System. The team has found the root cause and mitigated the...
Beginning at 16:44 UTC, we observed increased latency and errors in our API and build system. The affected components have returned to normal and the team continues to monitor.
Starting at 11:29 UTC our legacy TCP load balancer with IP 104.198.14.52 is suffering connection timeouts due to an upstream provider problem. Customers still pointing to this Load Balancer via A r...
Increase the productivity and efficiency of your team. Enable monitoring for your services, and start receiving real-time alerts when your external dependencies have outages.
Start today for FREE