Australia SMS Carrier Partner Maintenance
<p>Our SMS carrier partner in Australia is conducting an emergency maintenance from 19 November 2026 at 04:30 PST until 19 November 2026 at 05:30 PST. During the maintenance window, there could be intermittent delays delivering SMS to and from Australia handsets.<br><br>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p>
The latest update from Twilio.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Twilio
<p>Our SMS carrier partner in Australia is conducting an emergency maintenance from 19 November 2026 at 04:30 PST until 19 November 2026 at 05:30 PST. During the maintenance window, there could be intermittent delays delivering SMS to and from Australia handsets.<br><br>We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.</p>
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
164
Days with an incident
54
Median duration
5 h 34 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·Transactional Email Delays in AP
Our engineers have investigated and resolved an issue with transactional email. From 5:41AM PST to 6:15AM PST on Wednesday, 11/18/26, customers may have experienced elevated latency when sending transactional email. The issue has been resolved and all impacted services are operating normally.
Twilio·Voice Call Failures from a Subset of Twilio phone numbers in Brasil
Voice calls fail from a subset of Twilio phone numbers in Brasil, which affects SIP Interface US1 and Programmable Voice US1. Twilio reports that the incident is resolved and that it lasted about 47 minutes.
Twilio·SMS Delivery Delays and Failures from a Subset of Twilio Short Codes to Bell and Bell Aliant Canada
Twilio SMS delivery delays and failures affect a subset of Twilio Short Codes to Bell and Bell Aliant subscribers in Canada. The affected components are SMS Short Code, North America and CARRIER NETWORK - SMS Short Code, North America. Twilio reports the status as identified and is working to resolve the issue.
Twilio·Speech Recognition Failures in US1
Twilio reported speech recognition and real-time transcription failures in US1. The affected components include Recording Transcriptions, Speech Recognition (Gather Speech), and Realtime Transcriptions in US1, and Realtime Transcriptions in PROGRAMMABLE VIDEO. Twilio reported the incident as resolved after 2 hours and 48 minutes.
Twilio·Programmable Messaging API Errors
Twilio had errors on the Programmable Messaging API and its SMS, MMS, and RCS Messaging components. The incident is resolved. It lasted 52 minutes, from 23:52 UTC on 17 November 2026 to 00:44 UTC on 18 November 2026.
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