Amazon Web Services

aws.amazon.com (opens in new tab)Status page (opens in new tab)

Status page says: Major outage since Oct 19, no open incident posted
Last 90 days: 8 incidents
Rewrites caught: None so far
Next deprecation: None announced

Amazon Web Services incidents per day, last 90 days

Select a day to jump to its incidents below.

How Amazon Web Services reports incidents

Compared with the 152 vendors that have enough incidents to compare. Each tick is one vendor; lower is better on every line.

Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors

First posted only after it was over

4% 1 of the 28 incidents we have in full detail

The first update already said resolved. Typical vendor: 6%.

Amazon Web Services: around the middle.

Time to resolve

2 h 16 min median; 9 in 10 within 28 h 35 min

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

Amazon Web Services: around the middle.

Major or critical incidents

0.3 a month 3 in the last 365 days

Impact as the vendor labels it. Typical vendor: 1.2 a month.

Amazon Web Services: lower than most vendors.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

Dependencies

What Amazon Web Services relies on and who relies on Amazon Web Services, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.

Amazon Web Services depends on

Provider	Evidence	Signal
Anthropic	integration affected in 1 “…Fable 5 and Mythos 5 Access (us-east-1) Claude Fable 5 and Claude Mythos 5 models remain unavailable for all users in all regions. We are resolving this Health event. For further details please view t…” incident	Weak

Who depends on Amazon Web Services

Vendor	Evidence	Signal
Chargebee	blamed in 33 incidents; together in 6 outage events “…ervice Degradation We experienced a brief service interruption in the US region due to an AWS platform issue, which resulted in intermittent API failures for some merchants. All services have complete…” incident	Strong
Aptible	blamed in 25 incidents; named as hosting in 10; together in 9 outage events “…Operation failures due to AWS Outage This incident has been resolved. AWS is experiencing an issue with their APIs in us-east-1, and many services are impacted at this time. This may lead to failed op…” incident	Strong
JFrog	blamed in 22 incidents; named as hosting in 72; together in 8 outage events “…JFrog platform services outage affecting a subset of AWS customers due to AWS infrastructure issues This incident has been resolved. A fix has been implemented and we are monitoring the results. The i…” incident	Strong
Confluent	blamed in 15 incidents; named as hosting in 150; integration affected in 6; together in 15 outage events “…Elevated error rates in AWS me-south-1 and me-central-1 regions This incident has been resolved. AWS regional recovery is expected to be extended in both me-central-1 and me-south-1 regions. Customers…” incident	Strong
Wiz	blamed in 14 incidents; named as hosting in 1; integration affected in 1; together in 5 outage events “…Intermittent login issues - EU1 and EU2 - due to AWS issues This incident has been resolved.…” incident	Strong
Braze	blamed in 13 incidents; together in 4 outage events “…Connectivity to US cluster seeming due to AWS incident Systems have remained operational since the earlier incident. Due to the recent continued incidence of AWS chassis instability for the dedicated…” incident	Strong
Keeper	blamed in 12 incidents; named as hosting in 3; together in 3 outage events “…Email delivery in US region due to AWS US-EAST outage All Keeper email delivery services in US-EAST-1 were restored around 4AM PST. All Keeper email delivery services in US-EAST-1 were restored around…” incident	Strong
Prisma	blamed in 11 incidents; named as hosting in 12; together in 2 outage events “…Accelerate is slow to provision new query engines in eu-west-3 This incident has been resolved. This incident has been resolved. We have identified an upstream infrastructure provider issue affecting…” incident	Strong
Coralogix	blamed in 11 incidents; named as hosting in 7; together in 4 outage events “…User interface availability issues - Due to AWS Incident in Amazon Elastic Load Balancing (Ireland) We have mitigated the AWS issue by switching off the impacted AZ and are currently not seeing anymor…” incident	Strong
Firebolt	blamed in 10 incidents; named as hosting in 2; together in 7 outage events “…AWS Outage affecting Start/Stop Engines AWS has announced all services are restored, although there is a backlog of requests in their services. We are seeing engines start and stop succesfully, althou…” incident	Strong
Grafana Cloud	blamed in 9 incidents; named as hosting in 112; integration affected in 4; together in 5 outage events “…Outage for prod-eu-central-0 due to AWS S3 outage. This incident has been resolved.…” incident	Strong
Xero	blamed in 9 incidents; together in 9 outage events “…red sporadically on 6-7 May and 12 May, affecting login and platform navigation. ### 2. AWS infrastructure outage \(8 May\) A third-party AWS infrastructure incident caused degraded platform perfo…” incident	Strong
AssemblyAI	blamed in 8 incidents; named as hosting in 2; together in 2 outage events; listed as a subprocessor “…eaming usage on the EU endpoint. The team has identified the issue and it is caused by an AWS Operational Issue on their Amazon Elastic Compute Cloud (Ireland). Our team is in touch with AWS and monit…” incident	Strong
Asana	blamed in 8 incidents; together in 7 outage events “…App Down Incident: AWS infrastructure had [an outage affecting core services](https://aws.amazon.com/message/101925/), which our application depends on, in the Virginia \(us-east-1\) region. After…” incident	Strong
Pipedream	blamed in 8 incidents; together in 4 outage events “…iple services are experiencing a service disruption as a result of a downstream provider (AWS). We are closely monitoring the status. Multiple services are experiencing a service disruption as a resul…” incident	Strong

And 45 more.

Outage events: AWS us-west-2, Sep 3, AWS, Jul 16, AWS us-east-1, May 8, AWS us-east-1, Oct 20, 2025.

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.