Possible 503 Errors for Messaging Traffic in the Australia Region
Customers in the Australia Region are no longer encountering 503 Errors for Messaging Traffic. This incident has been resolved.
The latest update from Twilio.
State
Resolved
Started
4 d ago
2026-10-28 14:18 UTC
Lasted
7 h 14 min
until 2026-10-28 21:32 UTC
Worst impact
Degraded
Timeline
6 updatesInvestigating
1 h 3 min 14%
Identified
5 h 42 min 79%
Monitoring
29 min 7%
Updates
Times in UTCAs posted by Twilio
Customers in the Australia Region are no longer encountering 503 Errors for Messaging Traffic. This incident has been resolved.
Our engineers have deployed a fix, and are monitoring to confirm that affected customers in the Australia Region are no longer encountering 503 Errors for Messaging Traffic. We expect to provide another update in 30 minutes or as soon as more information becomes available.
Our engineers have identified the issue with possible 503 Errors for Messaging Traffic for some customers in the Australia Region and are continuing on working to deploy a fix. We expect to provide another update in 4 hours or as soon as more information becomes available.
Our engineers have identified the issue with possible 503 Errors for Messaging Traffic for some customers in the Australia Region and are continuing on working to deploy a fix. We expect to provide another update in 2 hours or as soon as more information becomes available.
Our engineers have identified the issue with possible 503 Errors for Messaging Traffic for some customers in the Australia Region and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available.
Our monitoring systems have detected a potential issue with potential failing in cell messaging-ingress-gateway-0. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
52
Days with an incident
38
Median duration
9 h 35 min
This incident
25% shorter than the median
Other Twilio incidents
All incidentsTwilio·SMS Delivery Delays from a Subset of Twilio Short Codes to Google Voice United States
Twilio reports SMS delivery delays from a subset of Twilio Short Codes to Google Voice subscribers in the United States. The delays affect SMS Short Code and CARRIER NETWORK SMS Short Code in North America. Twilio identified the cause and is working to resolve the issue.
Twilio·SMS Delivery Failures from Twilio to KDDI Japan
SMS delivery failures from Twilio to KDDI network subscribers in Japan affected SMS in the APAC region. Twilio reports that the incident is resolved. The outage lasted about 4 hours and 8 minutes.
Twilio·Silent Network Authentication (SNA) Missing Redirects and Gateway API (Lookup API) High Latency on KPN in Netherlands
The incident has been resolved and API transactions for Silent Network Authentication (SNA) on KPN in Netherlands and Lookup API transactions involving KPN in Netherlands are operating normally.
Twilio·Silent Network Authentication (SNA) Missing Redirects on Smart in Philippines
The incident has been resolved and API transactions for Silent Network Authentication (SNA) on Smart in Philippines are operating normally.
Twilio·Automated Alert: Minimal Customer Impact
We have fully investigated the issue affecting verifications to Ivory Coast, and it was determined that the impact was limited to a small set of customers, who have been contacted individually to address any concerns. All systems are operational.
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