Compare the status, incidents stats and history between Linode and AWS
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.
Provisioning is degraded due to ongoing issue. Services are recovering. We are still monitoring.
Our team is investigating an emerging service issue affecting Linode job processing (power on, reboot, shutdown, Cloud Firewall apply, etc.) in the US-SEA region. We will share additional updates a...
Our team is investigating an issue that affected connectivity in our IN-MAA (Chennai) and IN-BOM-2 data centers, related to a suspected outage with one of our peering partners. During this time, u...
We are investigating increased processing times for queued queries in the US-WEST-2 Region.
We are investigating increased network latency between the US-EAST-1 and US-EAST-2 Regions. We have identified the scope of impact and are actively working to restore normal network performance. We...
Between 7:26 PM and 8:13 PM PDT we experienced increased packet loss and latency in a single availability zone(apne1-az1) in the AP-NORTHEAST-1 Region. The issue has been resolved and services are ...
14-day free trial · No credit card required · No code required