Live

Delivery Issue Qatar - Ooredoo Qatar

0

SMS delivery through Ooredoo Qatar in Qatar had failures and delays. Sinch reports that the incident is resolved. It lasted from 02:35 UTC to 05:23 UTC on 2026-11-18.

State

Resolved

Started

Lasted

2 h 40 min

Worst impact

Degraded

Timeline

3 updates
03:4504:2505:0505:4506:25
DegradedUpdate postedTimes in UTC

Investigating

2 h 40 min 100%

Updates

Times in UTC

As posted by Sinch

Resolved

This incident has been resolved. Incident Start Time: 2026-11-18 02:35 UTC Incident End Time: 2026-11-18 05:23 UTC

Investigating

We are continuing to investigate this issue.

Investigating

We are currently observing delivery issues in Qatar - Ooredoo Qatar. Incident Start Time: 2026-11-18 02:35 UTC Impact: Failed/ Delayed MT's/ Failed/ Delayed MO's/ Missing delivery receipts/ Late delivery receipts We will update as soon as we have more information. If you have any questions, please contact support@sinch.com.

Affected components

2
SMS - EMEAExternal Connectivity - SMS - EMEA

Sinch in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

65

Days with an incident

47

Median duration

2 h 55 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 days
median 2 h 55 min
90 days agoToday

Other Sinch incidents

All incidents
Sinch logo

SinchΒ·Delivery Issue Canada - Bell Canada

SMS delivery to Bell Canada in Canada does not work correctly for ShortCode and Toll Free, including external connectivity. Sinch reports that the incident is resolved. The outage lasted 52 minutes.

Resolved
Sinch logo

SinchΒ·Delivery Issue Chile - Claro

Sinch reported a delivery issue in Chile on the Claro network. The issue affected SMS - LATAM and External Connectivity - SMS - LATAM. Sinch reports that the incident is resolved. It lasted 30 minutes.

Resolved
Sinch logo

SinchΒ·Customer Support - Ticketing System

Sinch reports a major outage in its Customer Support ticketing system. The problem affected email parsing into the ticket system and the Customer Support area of Dashboard.sinch.com. Sinch resolved the incident on 14 November 2026, about 35 hours after it started.

Resolved
Sinch logo

SinchΒ·Delivery Issue SMS Verfication China

Sinch reports delivery problems for SMS Verification in China. The problem started on 12 November 2026 at 01:58 UTC. Sinch is investigating the issue and reports failed mobile terminated messages, missing delivery receipts, and late delivery receipts.

Degraded
Sinch logo

SinchΒ·Delivery Issue - United States - AT&T

Sinch reported a delivery issue for SMS Verification and SMS - US - 10DLC, and for External Connectivity - SMS - US - 10DLC, in the United States on the AT&T network. The impact was failed, delayed, or missing MT messages and delivery receipts. Sinch resolved the incident, which lasted about 3 hours and 41 minutes.

Resolved

Follow Sinch

Your coding agent knows when Sinch is down, and tells you when a failure is theirs, not yours. You can also get Sinch incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "sinch" and tell me if Sinch has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=sinch
Slack
/feed subscribe https://outages.live/feed.xml?providers=sinch

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane