Skip to main content
Sinch

Services | Operator Services | Potential delay in delivery of MO, MT and DLR | TT#MNOC-64657

Degraded Lasted 21h 50m · started · Sinch's page

Level
confirmed
Worst impact
Degraded
Components
SMS 365 Operator US
Regions
us
Down Index
27of 100

What to do

  • Check whether you use Sinch SMS 365 Operator US in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 21h 50m it lasted.

    Anything that failed between 2026-07-06 21:35 UTC and 2026-07-07 19:25 UTC may need a replay.
  • Subscribe to Sinch's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=sinch works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Sinch 4

  1. identified

    Ticket Number: MNOC-64657 Services: SMSx Description: We observed queues related to MO, MT and DLR traffic within our SMSx platform. Few customers may have observed a potential delay in delivery for MO, MT and DLR traffic on 06 July, 2026 between 19:20 - 20:35 GMT. Our technical teams are actively working on the root cause and are monitoring for stability. We will continue to provide updates as more information becomes available. We appreciate your patience and understanding. Impact: Mobile Terminating (MT) Traffic: Potential delay in delivery Mobile Originated (MO) Traffic: Potential delay in delivery DR Notification: Potential delay in delivery Incident Start Date & Time (GMT) : 06 July, 2026 If you have any questions, please contact the Operator Service NOC immediately at operatorservices.noc@sinch.com or +1 470.300.8394 (select ‘Support’ from the menu, option 2 for Digital Interconnect, and then option 1) and reference this notification.

    provider

  2. identified

    Engineering continues to work on this issue. A secondary queueing period was observed between 21:49-22:22 GMT and has recovered with messages processing normally at this time.

    provider

  3. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  4. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-338075a3fb

Is Sinch still down?

No, this incident was resolved 2026-07-07 19:25 UTC. For Sinch's live state, see https://down.guide/sinch.

How long did it last?

21h 50m, from 2026-07-06 21:35 UTC to 2026-07-07 19:25 UTC, by the times Sinch posted.

What was affected?

Sinch named SMS 365 Operator US in us.

What caused it?

Sinch hasn't published a root cause. If it does, it shows here.

Where does this come from?

Sinch's official status page, https://status.sinch.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.