Twilio reported this minor-impact incident on its official status page on Oct 28, 2026, 14:18 UTC. It has not been marked resolved yet.
Right now Twilio is operational. Live Twilio status →
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.
Overlapping incidents aren't necessarily related.
Twilio reported 507 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 6h 10m. See Twilio's uptime and incident history