# Sinch: Verification Service Degradation

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2019-11-12 08:33 UTC · Resolved: 2019-11-12 14:24 UTC · Duration: 5.8 h
- Updates: 1
- [Vendor status page: https://status.sinch.com/incidents/y9zmc6ny4l6f](https://status.sinch.com/incidents/y9zmc6ny4l6f)
- [Company: Sinch](https://rewindex.com/company/sinch.md)

## Part of an outage event

- [AWS outage, Nov 12, 2019: 11 vendors, 12 incidents](https://rewindex.com/events/2019-11-12-aws)
- This incident blames AWS as the cause. (hop 1, posted +53 min vs the first vendor naming AWS)
- Evidence: “…Verification Service Degradation AWS informs that tje issue was resolved at 1:26 AM PST and our service has been stable since.…”

```mermaid
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 --> later
  me["Sinch (this incident)<br/>posted +53 min"]:::me
  h1 --- me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **resolved** 2019-11-12 14:24 UTC: AWS informs that tje issue was resolved at 1:26 AM PST and our service has been stable since.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/sinch/incidents/y9zmc6ny4l6f · Markdown: https://rewindex.com/company/sinch/incidents/y9zmc6ny4l6f.md · JSON: https://rewindex.com/api/v1/companies/sinch/incidents/y9zmc6ny4l6f · Generated 2026-10-20T03:13:44.845Z