SMS Delivery Failures between a Subset of Twilio Short Codes and Claro in Brazil
Twilio SMS delivery failures affect a subset of Twilio Short Codes that send to Claro network subscribers in Brazil. The SMS and Carrier Network SMS components in Latin America are degraded. Twilio has identified the cause and is working to resolve the issue.
State
Identified
Started
Ongoing for
1 h 53 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
29 min 26%
Identified
1 h 23 min 74%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing SMS delivery failures between a subset of Twilio Short Codes and Claro 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 failures between a subset of Twilio Short Codes and Claro 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 failures between a subset of Twilio Short Codes and Claro 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
157
Days with an incident
53
Median duration
6 h 1 min
This incident
69% shorter than the median
Other Twilio incidents
All incidentsTwilio·Voice Call Post Dial Delay, Audio Quality Degradation, and Silent and One-Way Audio Between Twilio Phone Numbers and Brazil
Voice calls between Twilio Phone Numbers and network subscribers in Brazil can have post dial delay, poor audio quality, and silent or one-way audio. The Voice and carrier network components in Latin America are affected. Twilio has identified the cause and works to resolve the issue.
Twilio·Customers Unable to View Balance in Console
Twilio customers could not view their balance in Console. The issue affected the Billing components. Twilio reports that the issue is resolved, and the outage lasted about 6 minutes.
Twilio·Voice Call Audio Quality Degradation Between Twilio and Multiple Networks in United Kingdom
Twilio voice call audio quality is degraded between Twilio and network subscribers on multiple networks in the United Kingdom. The affected components are Voice, Europe and CARRIER NETWORK - Voice, Europe. Twilio has identified the cause and work to resolve the issue is in progress.
Twilio·SMS Delivery Delays from Twilio to Sky United Kingdom
Twilio SMS delivery to Sky network subscribers in the United Kingdom had delays. The SMS, Europe and CARRIER NETWORK - SMS, Europe components were affected. Twilio reported that the incident is resolved, and it lasted about 5 hours.
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.
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.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.
https://outages.live/feed.xml?providers=twilio/feed subscribe https://outages.live/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane