SMS Delivery Delays from Twilio to Algar Telecom Brazil
SMS delivery delays affect messages from Twilio to Algar Telecom subscribers in Brazil. Twilio reports that it identified the cause and is working to fix the problem. The incident started 67 minutes ago.
State
Identified
Started
Ongoing for
1 h 53 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
7 min 6%
Identified
1 h 46 min 94%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing SMS delivery delays from Twilio to Algar Telecom network subscribers in Brazil. 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.
Twilio customers may be experiencing SMS delivery delays from Twilio to Algar Telecom network subscribers in Brazil. 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.
Twilio customers may be experiencing SMS delivery delays from Twilio to Algar Telecom network subscribers in Brazil. 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
2Twilio in the last 90 days
Full historyIncidents in 90 days
73
Days with an incident
40
Median duration
7 h 41 min
This incident
75% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays from Twilio to Claro Brazil
SMS delivery delays affect Twilio messages to Claro network subscribers in Brazil. The SMS and carrier network components in Latin America are degraded. Twilio identified the cause and is working to resolve the issue.
Twilio·MMS Delivery Failures from a Subset of Twilio Long Codes to GCI United States
Twilio MMS delivery failures affected a subset of Twilio Long Codes to GCI network subscribers in the United States. The components were MMS Long Code, North America and related carrier and ZIPWHIP messaging services. Twilio reports that the incident is resolved. It lasted about 32 minutes.
Twilio·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Networks in United States
Twilio MMS delivery receipts were delayed from a subset of Twilio Long Codes to subscribers on multiple small networks in the United States. Twilio reports that the incident is resolved. The outage lasted 8 hours and 3 minutes.
Twilio·MMS Delivery Delays and Delivery Receipt Delays from a Subset of Twilio Long Codes and Short Codes to AT&T United States
Twilio MMS delivery and MMS delivery receipts had delays for a subset of Twilio Long Codes and Short Codes to AT&T subscribers in the United States. The affected components include MMS Long Code and MMS Short Code in North America. Twilio reports that the incident is resolved. The incident lasted about 10 hours and 25 minutes.
Twilio·MMS Delivery Delays and Failures from a Subset of Twilio Short Codes to T-Mobile and Verizon United States
MMS delivery delays and failures affected a subset of Twilio Short Codes to T-Mobile and Verizon subscribers in the United States. Twilio reports that the incident is resolved. The incident lasted about 6 hours and 18 minutes.
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.
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.cc/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.
https://outages.cc/feed.xml?providers=twilio/feed subscribe https://outages.cc/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane