Sinch

sinch.com (opens in new tab)Status page (opens in new tab)

Status page says: Operational since Oct 19
Last 90 days: 92 incidents, 3 major or critical
Rewrites caught: None so far
Next deprecation: None announced

Sinch incidents per day, last 90 days

Select a day to jump to its incidents below.

How Sinch reports incidents

Compared with the 152 vendors that have enough incidents to compare. Each tick is one vendor; lower is better on every line.

Provisional. Built nightly from every archived version of each incident, last on Oct 19. Compare all vendors

First posted only after it was over

14% 7 of the 50 incidents we have in full detail

The first update already said resolved. Typical vendor: 6%.

Sinch: higher than most vendors.

Time to resolve

2 h 55 min median; 9 in 10 within 17 h 14 min

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

Sinch: around the middle.

Major or critical incidents

1.1 a month 13 in the last 365 days

Impact as the vendor labels it. Typical vendor: 1.2 a month.

Sinch: around the middle.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

Dependencies

What Sinch relies on and who relies on Sinch, as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.

Sinch depends on

Provider	Evidence	Signal
mobile/SMS carriers	blamed in 18 incidents; integration affected in 296 “…e: 2026-09-28 02:00 UTC A fix has been implemented and we are monitoring the results. The carrier has confirmed a degradation on their end, and they are currently working on resolving the issue. As so…” incident	Strong
AWS (sa-east-1)	blamed in 2 incidents; named as hosting in 1; together in 9 outage events “…Site CA1-H1 - Degradation AWS has confirmed that the faulty hardware has been fixed, which our monitoring also confirms. For clients that have switched traffic to CA1-H2 during the period, you can now…” incident	Strong
Meta	blamed in 1 incident; integration affected in 8 “…re writing to inform you that the issue regarding our Whatsapp API has now been resovled. WhatsApp have confirmed that an internal issue affected the delivery of some configurations of templates inclu…” incident	Likely
Bandwidth	integration affected in 2 “…DI SMS 365 \| Enterprise Messaging \| Delay in delivery of MO, MT and DLR Traffic towards Bandwidth USA and MediaFriends in United States Connections are stable now, Incident is resolved. Sinch DI Monit…” incident	Likely
Zoho CRM	integration affected in 1 “…Engage - Zoho CRM Temporary Outage We are writing to inform you regarding an incident that affected our Engage - Zoho CRM services during the below time-frame. Incident Start Time: 2026-10-09 07:00 UT…” incident	Weak
Okta	integration affected in 1 “…Service Degradation - Verification - Okta integration This incident has been resolved. Incident Start Time: 2026-08-27 00:20 UTC Incident End Time: 2026-08-27 03:35 UTC…” incident	Weak

Who depends on Sinch

Vendor	Evidence	Signal
Xero	blamed in 1 incident “…AU: Auto Super - Some customers are not receiving auto super approval codes via SMS Sinch has resolved the issue impacting Australian customers not receiving auto super approval codes via SMS. We apol…” incident	Likely
Segment	listed as a subprocessor	Likely
Klaviyo	listed as a subprocessor	Likely
Twilio	integration affected in 1 “…SMS Delivery Delays to Sinch Network in the United States We are no longer experiencing SMS delivery delays when sending messages Sinch network in the United States. This incident has been resolved.…” incident	Weak
Sentry	listed as a subprocessor	Weak

Runs in (named in its incidents): AWS sa-east-1 (1).

Outage events: AWS us-west-2, Sep 3 (timing), GitHub, Jul 24 (timing), Cloudflare, Nov 18, 2025 (timing), Microsoft Azure, Oct 29, 2025 (timing), AWS us-east-1, Oct 20, 2025 (timing), Google Cloud, Aug 6, 2025 (timing), Google Cloud, Jun 12, 2025 (timing), AWS, Sep 28, 2023 (timing) and 11 more.

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.

Changes and edits

Incidents Sinch rewrote or removed, and notable changes to the pages we watch.

~~Struck in red~~ is what Sinch removed. Blue is what they added.

Tuesday, September 22

1 incident change

Critical
05:40Critical incident
Service Degradation – Calling – AP-Southeast-1

Thursday, September 10

1 incident change

Major
07:26Major incident
Campaigns Stats are not available

Full Sinch change history

Pricing and pages we watch

Page	Versions	Last changed	Last checked	History
Privacy policy (opens in new tab)	1	2026-10-19	2026-10-19	No changes yet
Subprocessors (opens in new tab)	1	2026-10-19	2026-10-19	No changes yet
Terms of service (opens in new tab)	1	2026-10-19	2026-10-19	No changes yet