Twilio incident

Unexpected 503 Errors When Connecting to Twilio APIs

Minor Resolved View vendor source →

Twilio experienced a minor incident on April 13, 2026 affecting REST API, lasting 3h. The incident has been resolved; the full update timeline is below.

Started
Apr 13, 2026, 08:13 PM UTC
Resolved
Apr 13, 2026, 11:14 PM UTC
Duration
3h
Detected by Pingoru
Apr 13, 2026, 08:13 PM UTC

Affected components

REST API

Update timeline

  1. investigating Apr 13, 2026, 08:13 PM UTC

    Our monitoring systems have detected a potential issue leading to 503 Errors. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

  2. investigating Apr 13, 2026, 08:53 PM UTC

    We are currently investigating an issue causing unexpected 503 errors (less than 0.01% error rate) at 19:30 UTC and again from 20:00 - 20:02 UTC for customers using Twilio APIs. Our engineers are investigating root cause and will provide another update in one hour or as soon as more information becomes available.

  3. investigating Apr 13, 2026, 10:10 PM UTC

    We are still investigating an issue causing unexpected 503 errors (less than 0.01% error rate) at 19:30 UTC and again from 20:00 - 20:02 UTC for customers using Twilio APIs. Our engineers are investigating root cause and will provide another update in 2 hours or as soon as more information becomes available.

  4. monitoring Apr 13, 2026, 10:43 PM UTC

    The unexpected 503 errors (less than 0.01% error rate) for customers using Twilio APIs are now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  5. resolved Apr 13, 2026, 11:14 PM UTC

    The issue causing unexpected 503 errors (less than 0.01% error rate) has been resolved and Twilio APIs are operating normally at this time.