Twilio incident: 5300 Errors on Singapore Client Edge

Affected components

• Client Web AU1
• Client Web IE1
• Client Web US1

1. resolvedOct 17, 2026, 22:11 UTC

   We are no longer observing the issue with 53000 errors on the Singapore edge client causing unregistered events. This incident has been resolved.

2. monitoringOct 17, 2026, 21:39 UTC

   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.

3. monitoringOct 17, 2026, 20:36 UTC

   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.

4. monitoringOct 17, 2026, 20:21 UTC

   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.

5. investigatingOct 17, 2026, 19:23 UTC

   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.

6. investigatingOct 17, 2026, 18:21 UTC

   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

7. investigatingOct 17, 2026, 17:51 UTC

   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

8. investigatingOct 17, 2026, 17:07 UTC

   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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Twilio's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• 1Password: High error rate on 1Password.comMajor · Oct 16, 2026, 23:45 UTC
• Grafana Cloud: IRM Unable to Send SMS to Thailand NumbersMinor · Oct 5, 2026, 16:17 UTC
• LiveKit: Investigating reports of elevated RoomService API errorsMinor · Oct 6, 2026, 00:10 UTC
• Shopify: Some merchants encountering error messages when trying to login to their adminsMinor · Oct 8, 2026, 14:49 UTC
• SendGrid: SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs to Mobile ChinaMinor · Oct 9, 2026, 06:42 UTC
• SendGrid: Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to ThailandMinor · Oct 12, 2026, 11:53 UTC
• Grafana Cloud: Phone call notifications to numbers in Russia and Kazakhstan are blockedMinor · Oct 13, 2026, 09:23 UTC
• OVHcloud: [GRA11][Public Cloud] - Network API incident notificationMinor · Oct 16, 2026, 16:13 UTC
• Snyk: Snyk Code Performance Degraded in SNYK-US-02Minor · Oct 17, 2026, 01:43 UTC
• OVHcloud: [GLOBAL][Cloud Databases] - MYSQL Database incident notificationMinor · Oct 17, 2026, 08:48 UTC

How often does Twilio have incidents?

Twilio reported 495 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 5h 55m. See Twilio's uptime and incident history