Live

SMS Delivery Delays from Twilio to Telenor Pakistan

0

Twilio SMS delivery to Telenor network subscribers in Pakistan did not work normally. The SMS and Carrier Network SMS components in APAC had degraded performance. Twilio reports that the incident is resolved. The incident lasted about 8 hours and 18 minutes.

State

Resolved

Started

Lasted

8 h 18 min

Worst impact

Degraded

Timeline

4 updates
13:2115:2617:3019:3521:39
DegradedUpdate postedTimes in UTC

Investigating

1 h 39 min 20%

Monitoring

6 h 39 min 80%

Updates

Times in UTC

As posted by Twilio

Resolved

The incident has been resolved and SMS delivery from Twilio to Telenor network subscribers in Pakistan is operating normally.

Monitoring

We have observed a recovery in SMS delivery from Twilio to Telenor network subscribers in Pakistan and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

Investigating

Twilio customers may be experiencing SMS delivery delays from Twilio to Telenor network subscribers in Pakistan. Our team is actively investigating this issue. We will provide another update in 2 hours or as soon as more information becomes available.

Investigating

Twilio customers may be experiencing SMS delivery delays from Twilio to Telenor network subscribers in Pakistan. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

Affected components

2
SMS, APACCARRIER NETWORK - SMS, APAC

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

153

Days with an incident

53

Median duration

6 h 18 min

This incident

1.3× the median

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

33 days
median 6 h 18 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·SMS Delivery Delays from Twilio to Sky United Kingdom

Twilio SMS delivery delays affect messages to Sky network subscribers in the United Kingdom. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. Twilio has identified the cause and work continues to resolve the issue.

Degraded

Twilio·Gateway API (Lookup API) Failure Increase in Canada

Twilio Lookup API transactions in Canada failed. The incident affected Lookup Identity Match and Legacy Identity MatchAndAttributes, including CARRIER NETWORK components. Twilio reports that the incident is resolved. The outage lasted 3 hours and 59 minutes.

Resolved

Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Liberty Mobile Puerto Rico

Twilio reports SMS delivery delays from a subset of Twilio Short Codes to Liberty Mobile subscribers in Puerto Rico. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio has identified the cause and is working to resolve the issue.

Degraded

Twilio·On Call Engineers are Investigating an issue with processing profile events

Twilio reported an issue that affected newly created profiles and the processing of profile events. Twilio investigated the issue. The issue is resolved. It lasted 86 minutes.

Resolved

Twilio·SMS Delivery Delays from a Subset of Twilio Short Codes to T-Mobile United States

Twilio SMS delivery delays affected a subset of Twilio Short Codes to T-Mobile subscribers in the United States. The incident is resolved. It lasted about 2 hours and 21 minutes.

Resolved

Follow Twilio

Your coding agent knows when Twilio is down, and tells you when a failure is theirs, not yours. You can also get Twilio 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 "twilio" and tell me if Twilio 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=twilio
Slack
/feed subscribe https://outages.live/feed.xml?providers=twilio

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane