Rewindex

RewindexOutage eventsFeb 13, 2025

AWS outage, Feb 13, 2025

11 vendors posted 10 incidents between 22:00 on Feb 13 and 05:00 on Feb 14 UTC, against about 10 incidents from 8 vendors in the same hours on an ordinary week. 8 vendors named AWS in 8 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.

    15. first vendor named AWS 22: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 hour2 vendors, 1 blamed AWSCourier, Teleport1 to 4 hours later5 vendors, 4 blamed AWSCoralogix, SingleStore, Aptible, Snowflake +1Later1 vendor, 1 blamed AWSGrafana Cloud
AWSown incident not archivedWithin an hour2 vendors, 1 blamed AWSCourier, Teleport1 to 4 hours later5 vendors, 4 blamed AWSCoralogix, SingleStore, Aptible,Snowflake +1Later1 vendor, 1 blamed AWSGrafana Cloud
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/>2 vendors, 1 blamed AWS<br/>Courier, Teleport"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>5 vendors, 4 blamed AWS<br/>Coralogix, SingleStore, Aptible, Snowflake +1"]:::blames
  root --> h4
  later["Later<br/>1 vendor, 1 blamed AWS<br/>Grafana Cloud"]:::blames
  root --> later

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

2 vendors

  • +0 min

    Blames AWS

    Minor incident

    CourierCourier Send and Message Event Slowdown

    …essage Event Slowdown The team has identified the issue related to network connections on AWS which resulted in a backup of messages on our pipeline. Messages are flowing through as expected, and the…

  • +33 min

    Names AWS

    Minor incident

    TeleportRegional Backend Connectivity Errors

    …customers \(<5\) with a custom backend configuration experienced a connectivity issue in us-west-2 lasting around 30 minutes due to a Cilium failure that was inadvertently blocking connections betwee…

1 to 4 hours later

5 vendors

  • +1 h 9 min

    Blames AWS

    Major incident

    Coralogix[EU2] - Partial outage in EU2 region

    …ident has been resolved. The root cause of the issue is related to a regional incident in AWS EU-NORTH-1. Incident details can be found here: https://health.aws.amazon.com/health/status. We are active…

  • +1 h 12 min

    Blames AWS

    Major incident

    SingleStoreAWS outage in Stockholm region causing connectivity issues

    …AWS outage in Stockholm region causing connectivity issues Issue has been resolved https://health.aws.amazon.com/health/status See the above update from AWS. An ongoing outage in Stockholm region is c…

  • +1 h 18 min

    Blames AWS

    Major incident

    AptibleOperations blocked - Route 53 propagation delays

    …Operations blocked - Route 53 propagation delays This incident has been resolved. This incident has been resolved. We are noticing Route 53 record requests succeeding in a normal time frame, and are l…

  • +1 h 28 min

    Names AWS

    Minor incident

    SnowflakeAWS - Europe (Stockholm): INC0126513

    …AWS - Europe (Stockholm): INC0126513 Current status: We've coordinated with our third-party service provider to implement the fix for this issue, and we've monitored the environment to confirm that se…

  • +1 h 33 min

    Blames AWS

    Minor incident

    Elastic CloudAvailability issues with aws-eu-north-1c (AWS Stockholm)

    …Availability issues with aws-eu-north-1c (AWS Stockholm) AWS has confirmed that they have entirely resolved the outage.…

Later

1 vendor

Same window, did not name anyone

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

Show all 2

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