Compare the status, incidents stats and history between AWS and Linode
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 experiencing elevated API error rates in a single Availability Zone (usgw1-az1) in the US-GOV-WEST-1 Region. We are working to mitigate the issue while we isolate the root cause.
We are investigating increased delays in EC2 instance and Status Check metrics, including DescribeInstances and DescribeInstanceStatus API results, in a single Availability Zone (use2-az1) in the U...
We are investigating increased API error rates for the EC2 APIs in the US-EAST-1 Region. This is mainly affecting the DescribeInstanceTypes, DescribeInstanceTypeOfferings and DescribeReservedInsta...
Our team is actively investigating an ongoing issue impacting the Linode Kubernetes Engine (LKE) in our Washington, DC (IAD) region, specifically concerning DNS resolution and autoscaling. Rest ass...
Our team is investigating a service issue that affects the Linode Cloud Manager and API. During that time, some users may experience issues when attempting to access these systems. We will share ad...
Our team is investigating an issue affecting connectivity in our London (LON1) data center During this time, users may experience intermittent connection timeouts and errors for all services deploy...
How much time you'll save your team, by having the outages information close to them?
14-day free trial · No credit card required · Cancel anytime