RewindexOutage eventsSep 27, 2021
AWS outage, Sep 27, 2021
11 vendors posted 12 incidents between 08:00 and 17:00 UTC, against about 19 incidents from 16 vendors in the same hours on an ordinary week. 4 vendors named AWS in 5 incidents (2 of them blamed it). Vendors reported an AWS outage; AWS’s own incident for this date is not in the archive.
Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.
Times are UTC; lags are from when the first vendor named AWS.
- first vendor named AWS 08:14
How it spread
Vendors that named AWS, grouped by when they posted, and vendors that blamed one of the vendors AWS took down. Solid lines: the vendor named the other. Dashed: same window, not named.
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>3 vendors, 1 blamed AWS<br/>Logz.io, Snowflake, Firebolt"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Confluent"]:::blames
root --> h4
later["Later<br/>1 vendor<br/>Snowflake"]:::names
root --> laterVendors that named AWS
In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).
Within an hour
3 vendors
- Minor incident
+0 min
Names AWS
Logz.ioSome customers experience log ingestion delay in eu-central-1 region
…Some customers experience log ingestion delay in eu-central-1 region This incident has been resolved.…
- Minor incident
+8 min
Names AWS
SnowflakeAWS - US East (N. Virginia): MI-20210927
…AWS - US East (N. Virginia): MI-20210927 The Service Incident is now closed. A Root Cause Analysis (RCA) will be posted within the next ten business days. We apologize for the inconvenience caused by…
- Major incident
+17 min
Blames AWS
FireboltEngines may fail to start and stop
…cident has been resolved. Firebolt is fully operational. The issue has been identified on AWS side. We are waiting for a complete recovery. The issue has been partially resolved and we are waiting on…
1 to 4 hours later
1 vendor
- Major incident
+1 h 28 min
Blames AWS
ConfluentExperiencing degraded availability and latency in AWS in us-east-1
…Experiencing degraded availability and latency in AWS in us-east-1 AWS Degraded EBS Volume Performance incident impacted the availability and latency of some of our Kafka clusters in us-east-1. We mit…
Later
1 vendor
- Minor incident
+7 h 47 min
Names AWS
SnowflakeAWS - US East (N. Virginia): MI-20210927-2
…AWS - US East (N. Virginia): MI-20210927-2 The Service Incident is now closed. A Root Cause Analysis (RCA) will be posted within the next ten business days. We apologize for the inconvenience caused b…
Same window, did not name anyone
7 incidents started during the event without naming AWS or another vendor. Some are part of it, some are a normal day’s background (about 19 in these hours).
Show all 7
- −10 minMajor incident
- +28 minMinor incident
- +47 minMajor incident
- +50 minMinor incident
- +53 minMajor incident
- +55 minMinor incident
- +1 h 11 minMajor incident
Detected automatically from 6 status pages opening incidents in the peak hour (normally at most 5). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.