RewindexOutage eventsDec 22, 2021
AWS us-east-1 outage, Dec 22, 2021
40 vendors posted 40 incidents between 12:00 and 15:00 UTC, against about 3 incidents from 3 vendors in the same hours on an ordinary week. 9 vendors named AWS in 9 incidents (6 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 12:41
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 us-east-1<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>8 vendors, 6 blamed AWS<br/>Firebolt, Bitbucket, HubSpot, CircleCI +4"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor<br/>Confluent"]:::names
root --> h4Vendors that named AWS
In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).
Within an hour
8 vendors
- Major incident
+0 min
Blames AWS
FireboltAmazon Elastic Compute outage
…ident has been resolved. The incident has been resolved. The issue has been identified by AWS and a fix is in progress. Waiting for a full recovery. We are experiencing an issue with AWS EC2 instances…
- Major incident
+17 min
Blames AWS
BitbucketBitbucket reliability web and api reliability and performance is degraded
…ite, API, Git cli operations, and Pipelines. The root cause was a power failure in one of AWS's datacenters in us-east. The issue has been resolved and Bitbucket services are operating normally.…
- Major incident
+17 min
Blames AWS
HubSpotHubSpot is currently unavailable for some customers.
…ustomers. Between 7:10 am and 9:13 am EST on December 22, our third-party cloud platform, AWS, experienced an outage that caused access issues and delays within HubSpot. HubSpot functionality has retu…
- Minor incident
+18 min
Blames AWS
CircleCIAWS EC2 incident affecting CircleCI
…AWS EC2 incident affecting CircleCI This incident has been resolved.…
- Incident, no impact listed
+25 min
Names AWS
MongoDB AtlasMongoDB Atlas: Cluster down alerts and difficulty creating clusters in AWS us-east-1
…MongoDB Atlas: Cluster down alerts and difficulty creating clusters in AWS us-east-1 This incident has been resolved.…
- Minor incident
+36 min
Names AWS
Elastic CloudConnectivity issue in AWS us-east-1
…Connectivity issue in AWS us-east-1 This incident has been resolved.…
- Minor incident
+44 min
Blames AWS
KlaviyoAWS incident affecting components of Klaviyo application
…AWS incident affecting components of Klaviyo application Open incidents for downstream providers are now resolved. Upon assessing impact, fewer than 1% of event-triggered marketing flow messages were…
- Major incident
+50 min
Blames AWS
JFrogJFrog Cloud service partial impact from AWS US East1 availability zone outage
…JFrog Cloud service partial impact from AWS US East1 availability zone outage This incident has been resolved.…
1 to 4 hours later
1 vendor
- Major incident
+1 h 40 min
Names AWS
ConfluentClusters running in AWS us-east1 (AZ use1-az4) experiencing degraded performance
…Clusters running in AWS us-east1 (AZ use1-az4) experiencing degraded performance This incident has been resolved.…
Same window, did not name anyone
31 incidents started during the event without naming AWS or another vendor. Some are part of it, some are a normal day’s background (about 3 in these hours).
Show all 31
- −32 minIncident, no impact listed
- −27 minMinor incident
- −26 minMinor incident
- −25 minMajor incident
- −15 minCritical incident
- −15 minMajor incident
- −14 minMajor incident
- −13 minMinor incident
- −11 minMinor incident
- −11 minMajor incident
- −5 minMinor incident
- −3 minMinor incident
- +1 minCritical incident
- +3 minMinor incident
- +4 minMinor incident
- +4 minMinor incident
- +6 minIncident, no impact listed
- +9 minCritical incident
- +14 minMajor incident
- +16 minCritical incident
- +18 minIncident, no impact listed
- +21 minMajor incident
- +26 minMajor incident
- +28 minMinor incident
- +37 minMajor incident
- +39 minMinor incident
- +39 minMajor incident
- +47 minMajor incident
- +58 minMinor incident
- +1 h 1 minMinor incident
- +1 h 8 minMajor incident
Detected automatically from 22 status pages opening incidents in the peak hour (normally at most 6). 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.