Skip to main content
Sinch logo

Is Sinch Down?

No — Sinch is up

Reachable from all 8 checked regions

Average response time: 216ms

Last checked · checks run every 6 hours

Official status page: https://status.sinch.com

Sinch uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
95ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 12 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

12-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: no data
Sep 3: no data
Sep 4: no data
Sep 5: no data
Sep 6: no data
Sep 7: no data
Sep 8: no data
Sep 9: 100.00% uptime, 16 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 30 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru
174ms
DNS 158ms TCP 1ms TLS 6ms TTFB 173ms
iad
234ms
DNS 212ms TCP 2ms TLS 6ms TTFB 234ms
jnb
213ms
DNS 185ms TCP 0ms TLS 11ms TTFB 213ms
lax
137ms
DNS 104ms TCP 2ms TLS 13ms TTFB 136ms
lhr
70ms
DNS 34ms TCP 2ms TLS 11ms TTFB 69ms
nrt
163ms
DNS 144ms TCP 1ms TLS 6ms TTFB 162ms
ord
382ms
DNS 360ms TCP 1ms TLS 6ms TTFB 381ms
sin
355ms
DNS 335ms TCP 2ms TLS 9ms TTFB 355ms

What Sinch does

Sinch is a cloud communications provider. Businesses send SMS and MMS, place and receive voice calls, run WhatsApp and RCS conversations, and deliver one-time passcodes through its APIs. It sits behind other companies' login flows, delivery notifications and support messaging, so an outage reaches their customers rather than only their own staff.

What an outage looks like

One-time passcodes and verification texts stop arriving, so users cannot complete sign-in on services that rely on Sinch. Outbound SMS and MMS queue or fail. Voice calls fail to connect or drop. WhatsApp, RCS and other channel messages are not delivered. API requests return errors or time out.

What to do about it

Read status.sinch.com, and read it narrowly. It breaks SMS out by region and by United States number type, listing short code, toll free and 10DLC separately, and it lists SMPP, HTTP and REST as separate components per region. Find the exact combination your traffic uses before concluding you are affected. Verification is its own group, so passcodes can fail while other sending works.

Is it down for everyone, or just you?

If this page says Sinch is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Twilio
Twilio
Plivo
Plivo
Vonage
Vonage
8x8
8x8

Sinch outage FAQ

My SMS is failing but a colleague's is fine. Is Sinch down?
Probably for your route only. Sinch reports SMS by region and, in the United States, by number type: short code, toll free and 10DLC are separate components on status.sinch.com. Traffic on one can fail while the others deliver normally. Find which number type and region your messages use, then check that specific row rather than the headline.
Users cannot log in because codes are not arriving. Where do I look?
Check the Verification group on status.sinch.com, which lists Flash Call Verification, SMS Verification and Verification Text to Speech separately from ordinary messaging. Passcode delivery can fail while other traffic is unaffected. If Verification is operational, the delay may sit with the mobile carrier instead, which the status page cannot show you.
Does the API protocol I use matter during an outage?
Yes. status.sinch.com lists SMPP, HTTP and REST as separate components, each broken out by region, so an incident can affect one integration path while another delivers normally. Check the protocol your application actually uses. Switching protocols mid-incident is rarely practical, but knowing which is affected tells you whether to wait or to fail over elsewhere.
Will queued messages send after the outage?
Behaviour depends on the product and the route, so treat it as uncertain rather than assuming either outcome. Resending in bulk during an incident is the action most likely to cause duplicates, because held and resent copies can both deliver once the route recovers. Check delivery reports for the affected window before sending anything a second time.
Is it Sinch or the receiving carrier?
Sinch hands messages to mobile carriers, and that last hop is outside its control, so a carrier problem produces the same missing text as a Sinch incident. status.sinch.com covers Sinch's own components only. If everything there is operational and your delivery reports show messages accepted and sent, the delay most likely sits downstream at the carrier.

How we measure this

  • We request Sinch's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Sinch publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Sinch goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required