- Level
- confirmed
- Worst impact
- Degraded
- Components
- Client Web US1, Client Web AU1, Client Web IE1
- Regions
- apac
What to do
Check whether you use Twilio Client Web US1, Client Web AU1, Client Web IE1 in apac. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 5h 3m it lasted.
Anything that failed between 2026-10-17 17:07 UTC and 2026-10-17 22:11 UTC may need a replay.Subscribe to Twilio's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Twilio 8
- investigating
Multiple customers have reported that they are receiving 53000 errors on the Singapore edge client causing unregistered events. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
provider
- investigating
We are currently investigating an issue with 53000 errors on the Singapore edge client causing unregistered events. We expect to provide another update in 30 minutes or as soon as more information becomes available
provider
- investigating
We are currently investigating an issue with 53000 errors on the Singapore edge client causing unregistered events. We expect to provide another update in 1 hour or as soon as more information becomes available
provider
- investigating
We are no longer observing the issue with 53000 errors on the Singapore edge client causing unregistered events, our engineering teams are still investigating the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available.
provider
- monitoring
We are no longer observing the issue with 53000 errors on the Singapore edge client causing unregistered events. Our engineering teams are continuing to monitor to ensure full service recovery. We will provide another update in 1 hour or as soon as more information becomes available.
provider
- monitoring
We are no longer observing the issue with 53000 errors on the Singapore edge client causing unregistered events. Our engineering teams are continuing to monitor to ensure full service recovery. We will provide another update in 1 hour or as soon as more information becomes available.
provider
- monitoring
We are no longer observing the issue with 53000 errors on the Singapore edge client causing unregistered events. Our engineering teams are continuing to monitor to ensure full service recovery. We will provide another update in 2 hours or as soon as more information becomes available.
provider
- resolved
We are no longer observing the issue with 53000 errors on the Singapore edge client causing unregistered events. This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-85b61a71e1
Is Twilio still down?
No, this incident was resolved 2026-10-17 22:11 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
5h 3m, from 2026-10-17 17:07 UTC to 2026-10-17 22:11 UTC, by the times Twilio posted.
What was affected?
Twilio named Client Web US1, Client Web AU1, Client Web IE1 in apac.
What caused it?
Twilio hasn't published a root cause. If it does, it shows here.
Where does this come from?
Twilio's official status page, https://status.twilio.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.