Live

SMS Delivery Delays from Twilio to T-Mobile Czech Republic

0

Twilio reports SMS delivery delays to T-Mobile subscribers in the Czech Republic. The issue affects SMS in Europe. Twilio has identified the cause and is working to resolve the issue.

State

Identified

Started

Ongoing for

1 h 22 min

Worst impact

Degraded

Timeline

3 updates
01:2301:4402:0402:2402:45
DegradedUpdate postedTimes in UTC

Investigating

10 min 12%

Identified

1 h 12 min 88%

Updates

Times in UTC

As posted by Twilio

Identified

Twilio customers may be experiencing SMS delivery delays from Twilio to T-Mobile network subscribers in the Czech Republic. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.

Identified

Twilio customers may be experiencing SMS delivery delays from Twilio to T-Mobile network subscribers in the Czech Republic. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

Investigating

Twilio customers may be experiencing SMS delivery delays from Twilio to T-Mobile network subscribers in the Czech Republic. 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, EuropeCARRIER NETWORK - SMS, Europe

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

81

Days with an incident

42

Median duration

7 h 14 min

This incident

81% shorter than the median

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

33 days
median 7 h 14 min
90 days agoToday

Other Twilio incidents

All incidents

Twilio·Voice Call Silent and One-Way Audio Between a Subset of Twilio Phone Numbers and Multiple Networks in Colombia

Twilio reports silent and one-way audio on some voice calls between a subset of Twilio phone numbers and network subscribers in Colombia. The affected components are Voice, Latin America and CARRIER NETWORK - Voice, Latin America. Twilio has identified the cause and is working to resolve the issue.

Degraded

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

Twilio reports SMS delivery receipt delays from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. This affects SMS and the carrier network in Latin America. Twilio has identified the cause and is working to resolve the issue.

Degraded

Twilio·SMS Delivery Failures from Twilio to Lycamobile France

Twilio SMS delivery to Lycamobile network subscribers in France failed. The Twilio SMS and carrier network components in Europe were degraded. Twilio resolved the incident. The outage lasted 4 hours and 51 minutes.

Resolved

Twilio·Voice Call Failures from a Subset of Twilio Mobile Numbers to Telefonica Argentina

Twilio voice calls fail from some Twilio Mobile Numbers to Telefonica network subscribers in Argentina. The Voice, Latin America and CARRIER NETWORK - Voice, Latin America components are affected. Twilio identified the cause and is working to resolve the issue.

Degraded

Twilio·Voice Call Post Dial Delay from a Subset of Twilio Canada Phone Numbers to Rogers Wireless and Fido Canada

Twilio voice calls from some Twilio Canada phone numbers to Rogers Wireless and Fido subscribers in Canada had post dial delay. The affected components were Voice, North America and CARRIER NETWORK - Voice, North America. Twilio reports that the incident is resolved. It lasted about 5 hours and 13 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