Twilio: Possible 503 Errors for Messaging Traffic in the Australia Region
Affected components: Programmable Messaging APIPROGRAMMABLE MESSAGING - Programmable Messaging API
Timeline of updates
- investigating
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.
- identified
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.
- identified
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.
- identified
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.
- monitoring
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.
- resolved
Customers in the Australia Region are no longer encountering 503 Errors for Messaging Traffic. This incident has been resolved.
Changes Rewindex caught on this incident
- Incident updated: Possible 503 Errors for Messaging Traffic in the Australia Region
- Incident updated: Possible 503 Errors for Messaging Traffic in the Australia Region
- Incident updated: Possible 503 Errors for Messaging Traffic in the Australia Region
- Incident updated: Possible 503 Errors for Messaging Traffic in the Australia Region
- Incident updated: Possible 503 Errors for Messaging Traffic in the Australia Region
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8ea7794a5091675b…Version 2 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
1b0360b018d69b76…Version 3 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
71839e2f91131d58…Version 4 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
4456dbb59708b0b1…Version 5 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
54d41fe399efe6eb…Version 6 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
2fc1cf320fe515b5…
Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Twilio, started 2026-10-28 14:18 UTC, resolved after 7.2 h, 6 update(s); edited after publishing.
- Title
- Possible 503 Errors for Messaging Traffic in the Australia Region
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/lq2y20qkm8q5
Twilio profileRecent Twilio incidentsAll outages on October 28, 2026Twilio in October 2026MarkdownJSON