RewindexOutage eventsNov 12, 2019
AWS outage, Nov 12, 2019
11 vendors posted 12 incidents between 07:00 and 17:00 UTC, against about 9 incidents from 9 vendors in the same hours on an ordinary week. 6 vendors named AWS in 7 incidents (5 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 07:40
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/>5 vendors, 4 blamed AWS<br/>Opsgenie, Elastic Cloud, Wise, JFrog +1"]:::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/>JFrog"]:::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
5 vendors
- Critical incident
+0 min
Blames AWS
OpsgenieOpsgenie EU - We observe increased error rates due to the outage in Cloud Provider AWS in EU Region
…Opsgenie EU - We observe increased error rates due to the outage in Cloud Provider AWS in EU Region The incident has been resolved. ~%40 error rate in Web requests ~%2 error rate in Api requests.…
- Major incident
+26 min
Names AWS
Elastic CloudAvailability problems within AWS eu-central-1c Availability Zone
…Availability problems within AWS eu-central-1c Availability Zone Final affected clusters have been restored. This incident is resolved.…
- Incident, no impact listed
+39 min
Blames AWS
…were fully or partially disabled. The root cause of the incident was a network issue with Amazon Web Services which has now been resolved. Our systems are back to normal.…
- Minor incident
+48 min
Blames AWS
JFrogDegraded performance for AWS EUC1 region
…Degraded performance for AWS EUC1 region This incident caused by Amazon Web Services outage in EU-West-1 region (Frankfurt) has been resolved.…
- Minor incident
+53 min
Blames AWS
SinchVerification Service Degradation
…Verification Service Degradation AWS informs that tje issue was resolved at 1:26 AM PST and our service has been stable since.…
1 to 4 hours later
1 vendor
- Major incident
+1 h 3 min
Blames AWS
ConfluentAWS eu-central-1 network failures affecting all clusters
…AWS eu-central-1 network failures affecting all clusters This incident has been resolved.…
Later
1 vendor
- Major incident
+8 h 48 min
Names AWS
JFrogPartial outage affecting Pro/ProX customers in AWS EUW1
…Partial outage affecting Pro/ProX customers in AWS EUW1 This incident has been resolved.…
Same window, did not name anyone
5 incidents started during the event without naming AWS or another vendor. Some are part of it, some are a normal day’s background (about 9 in these hours).
Show all 5
- +39 minMajor incident
- +40 minMinor incident
- +53 minIncident, no impact listed
- +56 minIncident, no impact listed
- +58 minMinor incident
Detected automatically from 9 status pages opening incidents in the peak hour (normally at most 4). 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.