Rewindex

CompaniesDailyIncidents

Daily: Audio and video calls impacted by an ongoing incident in us-east-1

MajorStatus: resolvedStarted Resolved (20 h)3 updatesstspg.io (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Dec 7, 2021 · 71 vendors, 77 incidents

Daily’s incident blames AWS as the cause. (hop 1, posted +1 h 53 min vs the first vendor naming AWS)

“…Audio and video calls impacted by an ongoing incident in us-east-1 AWS has resolved the regional issues in us-east-1. We have re-activated the us-east-1 region for new audio and video calls. AWS has r…”

Swipe sideways to see the whole diagram.

AWS us-east-1own incident not archivedWithin an hour11 vendors, 9 blamed AWSAptible, Firebolt, Honeycomb +81 to 4 hours later16 vendors, 12 blamed AWSMaven Central, Pusher, Confluent +13Later3 vendors, 2 blamed AWSSegment, Confluent, DopplerDaily (this incident)posted +1 h 53 min
AWS us-east-1own incident not archivedWithin an hour11 vendors, 9 blamed AWSAptible, Firebolt, Honeycomb +81 to 4 hours later16 vendors, 12 blamed AWSMaven Central, Pusher,Confluent +13Later3 vendors, 2 blamed AWSSegment, Confluent, DopplerDaily (this incident)posted +1 h 53 min
Daily is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS us-east-1<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>11 vendors, 9 blamed AWS<br/>Aptible, Firebolt, Honeycomb +8"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>16 vendors, 12 blamed AWS<br/>Maven Central, Pusher, Confluent +13"]:::blames
  root --> h4
  later["Later<br/>3 vendors, 2 blamed AWS<br/>Segment, Confluent, Doppler"]:::blames
  root --> later
  me["Daily (this incident)<br/>posted +1 h 53 min"]:::me
  h4 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Core Call Experience

Timeline of updates

  1. investigating

    Users close to the us-east-1 (Northern Virginia) region of AWS may be unable to join video calls. We are investigating.

  2. monitoring

    We have attempted to work around this AWS issue for users that would normally be routed to our us-east-1 resources by temporarily removing all of our us-east-1 DNS records from our AWS API Gateway configurations whilst we wait for AWS to recover the region. We'll continue to monitor the situation.

  3. resolved

    AWS has resolved the regional issues in us-east-1. We have re-activated the us-east-1 region for new audio and video calls.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Daily profileRecent Daily incidentsMarkdownJSON