rewindex

CompaniesSinchIncidents

Sinch: Calling Degradation - US East

MinorStatus: resolvedStarted Resolved (15 h)1 updatestatus.sinch.com (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Dec 7, 2021 · 47 vendors, 59 incidents

Sinch’s incident depends on AWS (declared dependency, named as a cause before); it did not name AWS. (hop 1, posted +1 h 56 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

depends on AWSknown dependencyAWS 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, DopplerKnown dependency8 vendorsBandwidth, Sinch, Smartsheet +5Sinch (this incident)posted +1 h 56 min
depends on AWSknown dependencyAWS 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, DopplerKnown dependency8 vendorsBandwidth, Sinch, Smartsheet+5Sinch (this incident)posted +1 h 56 min
Sinch 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
  dr["Known dependency<br/>8 vendors<br/>Bandwidth, Sinch, Smartsheet +5"]:::hop2
  root -.->|"depends on AWS"| dr
  me["Sinch (this incident)<br/>posted +1 h 56 min"]:::me
  root -.->|"known dependency"| 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.

Timeline of updates

  1. resolved

    Dear Client, We are writing to inform you that this incident is now resolved. Incident start time: 2021-12-07 17:10 UTC Incident end time: 2021-12-08 00:30 UTC This issue was caused due to degradation on our cloud hosting providers platform. If you have any further questions or concerns please do not hesitate to reach out to support@sinch.com Sincerely, Sinch

From Sinch’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

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 status.sinch.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Sinch, started 2021-12-07 17:46 UTC, resolved after 15 h, 1 update(s).

Title
Calling Degradation - US East
Vendor
Sinch
Date
URL
https://rewindex.com/company/sinch/incidents/n6wlspzc9r5c

Sinch profileRecent Sinch incidentsAll outages on December 7, 2021Sinch in December 2021MarkdownJSON