SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Multiple Networks in New Zealand
Twilio reports SMS delivery receipt delays from some Twilio short codes to multiple networks in New Zealand. This affects the SMS, APAC and CARRIER NETWORK - SMS, APAC components. Twilio is investigating the issue.
State
Investigating
Started
Ongoing for
58 min
Worst impact
Degraded
Timeline
1 updateInvestigating
58 min 100%
Updates
Times in UTCAs posted by Twilio
Twilio customers may be experiencing SMS delivery receipt delays from a subset of Twilio Short Codes to network subscribers on multiple networks in New Zealand. Our team is actively investigating this issue. Message delivery may succeed, but delivery receipts may be delayed. 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
89
Days with an incident
43
Median duration
6 h 53 min
This incident
86% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Networks in Chile
Twilio reports SMS delivery delays from a subset of Twilio Long Codes to subscribers on multiple networks in Chile. The SMS and carrier network components in Latin America are affected. Twilio has identified the cause and work to resolve the issue continues.
Twilio·SMS Delivery Delays from Twilio to Claro Dominican Republic
Twilio SMS delivery delays affected Claro network subscribers in the Dominican Republic. Twilio reported the incident as resolved. The incident lasted about 3 hours and 46 minutes.
Twilio·TwiML ConversationRelay Documents Page Error
The ConversationRelay documentation page on the Twilio docs site had an error. Links on that page sent users to a login prompt instead of other documentation pages. Twilio reported the issue as resolved after 116 minutes.
Twilio·Voice Call Failures from a Subset of Twilio Phone Numbers to Chile
Twilio voice calls from a subset of Twilio phone numbers to network subscribers in Chile failed. Voice in Latin America and the carrier network for Voice in Latin America had degraded service. Twilio resolved the incident after 3 hours and 45 minutes.
Twilio·Voice Call Audio Quality Degradation from a Subset of Twilio Mobile Numbers to Claro Colombia
Twilio voice call audio quality was degraded from some Twilio Mobile Numbers to Claro network subscribers in Colombia. Voice in Latin America was affected. Twilio reports that the incident is resolved. It lasted about 36 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