Rewindex

RewindexOutage eventsDec 15, 2021

AWS outage, Dec 15, 2021

49 vendors posted 49 incidents between 15:00 and 18:00 UTC, against about 4 incidents from 4 vendors in the same hours on an ordinary week. 15 vendors named AWS in 16 incidents (11 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.

    7. first vendor named AWS 15:32
Named AWSNamed another vendorDid not name anyoneEach column is 30 minutes

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.

AWSown incident not archivedWithin an hour15 vendors, 11 blamed AWSDaily, Gusto, Logz.io, Firebolt +11
AWSown incident not archivedWithin an hour15 vendors, 11 blamed AWSDaily, Gusto, Logz.io, Firebolt+11
Rendered on the server with pele from the Mermaid source below. Each box lists the first few vendors; every vendor is listed further down.
Mermaid source
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>15 vendors, 11 blamed AWS<br/>Daily, Gusto, Logz.io, Firebolt +11"]:::blames
  root --> h1

Vendors that named AWS

In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).

Within an hour

16 vendors

  • +0 min

    Blames AWS

    Major incident

    DailyConnectivity issues

    …e resolved. We're continuing to see issues across our platform as a result of the ongoing AWS outage. You'll likely experience problems joining calls, accessing the Dashboard, or using the REST API. W…

  • +1 min

    Blames AWS

    Major incident

    GustoGusto.com is currently inaccessible due to an AWS outage.

    …Gusto.com is currently inaccessible due to an AWS outage. This incident has been resolved. Gusto systems are operational and customer support phone lines have been re-opened.…

  • +6 min

    Blames AWS

    Incident, no impact listed

    Logz.ioPossible login problems

    …Possible login problems The login problem is over. AWS have reported resolution of their issues, as well as our auth provider. Our monitoring also shows the resolution.…

  • +15 min

    Blames AWS

    Minor incident

    FireboltAWS Networking issues

    …AWS Networking issues This incident has been resolved. This incident has been resolved. We are experiencing connection issues across multiple regions.…

  • +19 min

    Blames AWS

    Major incident

    LeverSystem issues stemming from AWS connectivity errors

    …System issues stemming from AWS connectivity errors AWS has confirmed that the connectivity issue is resolved. More information on the incident can be found here: https://status.aws.amazon.com/ Users…

  • +20 min

    Blames AWS

    Major incident

    Sigma ComputingAWS-based Sigma Sites Are Down

    …AWS-based Sigma Sites Are Down This outage was due to a third-party provider (AWS). At 08:10am the issue was identified and addressed by AWS. For more information please visit: https://status.aws.amaz…

  • +25 min

    Blames AWS

    Major incident

    CockroachDBCockroachDB unavailability in AWS US-West2 region

    …CockroachDB unavailability in AWS US-West2 region The networking connectivity issues in AWS US-WEST2 have been resolved and we are seeing no issues within CockroachCloud.…

  • +25 min

    Blames AWS

    Minor incident

    TrelloLog in and sign ups on mobile aren't working

    …Log in and sign ups on mobile aren't working This incident was caused by a larger AWS outage, and has now been resolved.…

  • +26 min

    Blames AWS

    Critical incident

    SmartsheetBridge service affected by AWS incident.

    …Bridge service affected by AWS incident. This incident has been resolved.…

  • +30 min

    Names AWS

    Incident, no impact listed

    ConfluentConfluent Cloud Clusters in AWS us-west-2 may be experiencing connectivity issues

    …Confluent Cloud Clusters in AWS us-west-2 may be experiencing connectivity issues We have identified the issue which was first observed at 15:34 UTC which affected connectivity to AWS US West 2 region…

  • +32 min

    Names AWS

    Major incident

    Temporal CloudDegraded service in us-west

    …Degraded service in us-west AWS us-west connectivity is restored and we are no longer degraded…

  • +33 min

    Names AWS

    Incident, no impact listed

    DatadogDelayed AWS Metrics Collection

    …Delayed AWS Metrics Collection This incident has been resolved.…

  • +33 min

    Names AWS

    Major incident

    NetlifyDegraded performance issues with AWS nodes in us-west-1

    …Degraded performance issues with AWS nodes in us-west-1 Third-party network services backing our service have recovered and there are no more effects on our customers or site visitors. We'll continue…

  • +35 min

    Names AWS

    Incident, no impact listed

    ConfluentConfluent Cloud UI Inaccessable

    …identified the issue which was first observed at 15:34 UTC which affected connectivity to AWS US West 2 region. The issue has been resolved at 15:56 UTC and service is operating normally.…

  • +36 min

    Blames AWS

    Minor incident

    InfluxData (InfluxDB Cloud)AWS US-West-2 outage affecting all services

    …AWS US-West-2 outage affecting all services This incident has been resolved.…

  • +36 min

    Blames AWS

    Critical incident

    PandaDocAWS incident: application is down

    …AWS incident: application is down We’re all set! PandaDoc services are available. If you experience any issues with this, please reach out to us at support@pandadoc.com.…

Same window, did not name anyone

33 incidents started during the event without naming AWS or another vendor. Some are part of it, some are a normal day’s background (about 4 in these hours).

Show all 33

Detected automatically from 37 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.