Twilio Outage History

Twilio degraded · 2 active incidents View live status →

Twilio had 301 outages in the last 2 years totaling 498h 49m of downtime — averaging 12 incidents per month.

There were 301 Twilio outages since April 7, 2026 totaling 498h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.twilio.com

Minor April 15, 2026

User Authentication Identity Gateway API Failure Increase for T-Mobile in United States

Detected by Pingoru
Apr 15, 2026, 06:59 AM UTC
Resolved
Apr 15, 2026, 11:14 AM UTC
Duration
4h 14m
Affected: Lookup SIM Swap
Timeline · 4 updates
  1. investigating Apr 15, 2026, 06:59 AM UTC

    Twilio customers may be experiencing User Authentication Identity Gateway API failure increase for T-Mobile in the United States. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. investigating Apr 15, 2026, 08:05 AM UTC

    Twilio customers may be experiencing User Authentication Identity Gateway API failure increase for T-Mobile in the United States. Our team is actively investigating this issue. We will provide another update in 2 hours or as soon as more information becomes available.

  3. monitoring Apr 15, 2026, 10:09 AM UTC

    We have observed a recovery in User Authentication Identity Gateway API failure increase for T-Mobile in the United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  4. resolved Apr 15, 2026, 11:14 AM UTC

    The incident has been resolved and User Authentication Identity Gateway API failure increase for T-Mobile in the United States is operating normally.

Read the full incident report →

Minor April 15, 2026

User Authentication Identity SNA Failure Increase for Telkomsel in Indonesia

Detected by Pingoru
Apr 15, 2026, 05:43 AM UTC
Resolved
Apr 15, 2026, 11:20 AM UTC
Duration
5h 37m
Affected: Verify Silent Network Auth
Timeline · 5 updates
  1. investigating Apr 15, 2026, 05:43 AM UTC

    Twilio customers may be experiencing User Authentication Identity SNA failure increase for Telkomsel. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. identified Apr 15, 2026, 05:46 AM UTC

    Twilio customers may be experiencing User Authentication Identity SNA failure increase for Telkomsel in Indonesia. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  3. monitoring Apr 15, 2026, 06:54 AM UTC

    We have observed a recovery in User Authentication Identity SNA failure increase for Telkomsel in Indonesia and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  4. monitoring Apr 15, 2026, 09:00 AM UTC

    We have observed a recovery in User Authentication Identity SNA failure increase for Telkomsel in Indonesia and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.

  5. resolved Apr 15, 2026, 11:20 AM UTC

    The incident has been resolved and User Authentication Identity SNA failure increase for Telkomsel in Indonesia is operating normally.

Read the full incident report →

Minor April 14, 2026

Reassigned Number Package Degradation for Lookup V2 API

Detected by Pingoru
Apr 14, 2026, 08:51 PM UTC
Resolved
Apr 14, 2026, 09:19 PM UTC
Duration
28m
Affected: Lookup
Timeline · 4 updates
  1. investigating Apr 14, 2026, 08:51 PM UTC

    The reassigned number package is experiencing errors in the responses returned through the API. We expect to provide another update in 1 hour or as soon as more information becomes available

  2. investigating Apr 14, 2026, 08:51 PM UTC

    The reassigned number package is experiencing errors in the responses returned through the API. We expect to provide another update in 1 hour or as soon as more information becomes available

  3. monitoring Apr 14, 2026, 09:11 PM UTC

    We have started seeing recovery for the reassigned number package experiencing errors in the responses returned through the API. We will continue to monitor to ensure a full recovery. We expect to provide another update in 2 hours or as soon as more information becomes available.

  4. resolved Apr 14, 2026, 09:19 PM UTC

    The issue affecting intermittent errors for the reassigned number package in the responses returned through the API has been resolved and the service is functioning normally at this time.

Read the full incident report →

Minor April 14, 2026

On Call Engineers Are Investigating an Issue with WhatsApp Sender Registration in Meta Embedded Signup

Detected by Pingoru
Apr 14, 2026, 06:14 PM UTC
Resolved
Apr 14, 2026, 10:13 PM UTC
Duration
3h 59m
Affected: Messaging Channels
Timeline · 6 updates
  1. investigating Apr 14, 2026, 06:14 PM UTC

    Our monitoring systems have detected a potential issue with customers being unable to complete sender registration process for WhatsApp. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

  2. investigating Apr 14, 2026, 06:42 PM UTC

    We are investigating issues for some customers who may be unable to complete sender registration prrocess for Whatsapp. We expect to provide another update in 1 hour or as soon as more information becomes available

  3. investigating Apr 14, 2026, 06:57 PM UTC

    We are investigating an issue with WhatsApp sender registration in Meta embedded signup. We expect to provide another update in 1 hour or as soon as more information becomes available

  4. investigating Apr 14, 2026, 08:05 PM UTC

    We are investigating an issue with WhatsApp sender registration in Meta embedded signup. We expect to provide another update in 2 hours or as soon as more information becomes available

  5. monitoring Apr 14, 2026, 10:06 PM UTC

    We are observing successful recovery of the WhatsApp sender registration in Meta embedded signup. We will continue to monitor to ensure full service recovery. We expect to provide another update in 2 hours or as soon as more information becomes available.

  6. resolved Apr 14, 2026, 10:13 PM UTC

    We are observing successful recovery of the WhatsApp sender registration in Meta embedded signup issue. This incident has been resolved.

Read the full incident report →

Minor April 14, 2026

SMS Delivery Delays and Failures from Twilio to Viva Cell MTS Armenia

Detected by Pingoru
Apr 14, 2026, 02:49 PM UTC
Resolved
Apr 14, 2026, 09:41 PM UTC
Duration
6h 52m
Affected: SMS, Europe
Timeline · 7 updates
  1. investigating Apr 14, 2026, 02:49 PM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from Twilio to Viva Cell MTS network subscribers in Armenia. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. identified Apr 14, 2026, 03:19 PM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from Twilio to Viva Cell MTS network subscribers in Armenia. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  3. identified Apr 14, 2026, 04:19 PM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from Twilio to Viva Cell MTS network subscribers in Armenia. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.

  4. identified Apr 14, 2026, 06:20 PM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from Twilio to Viva Cell MTS network subscribers in Armenia. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available.

  5. monitoring Apr 14, 2026, 07:00 PM UTC

    We have observed a recovery in SMS delivery from Twilio to Viva Cell MTS network subscribers in Armenia and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  6. monitoring Apr 14, 2026, 09:01 PM UTC

    We have observed a recovery in SMS delivery from Twilio to Viva Cell MTS network subscribers in Armenia and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.

  7. resolved Apr 14, 2026, 09:41 PM UTC

    The incident has been resolved and SMS delivery from Twilio to Viva Cell MTS network subscribers in Armenia is operating normally.

Read the full incident report →

Minor April 14, 2026

SMS Delivery Delays from Twilio to AT&T Mexico

Detected by Pingoru
Apr 14, 2026, 08:19 AM UTC
Resolved
Apr 14, 2026, 02:22 PM UTC
Duration
6h 3m
Affected: SMS, Latin America
Timeline · 7 updates
  1. investigating Apr 14, 2026, 08:19 AM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to AT&T network subscribers in Mexico. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. identified Apr 14, 2026, 08:33 AM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to AT&T network subscribers in Mexico. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  3. monitoring Apr 14, 2026, 08:46 AM UTC

    We have observed a recovery in SMS delivery from Twilio to AT&T network subscribers in Mexico and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  4. identified Apr 14, 2026, 10:42 AM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to AT&T network subscribers in Mexico. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  5. identified Apr 14, 2026, 12:14 PM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to AT&T network subscribers in Mexico. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.

  6. monitoring Apr 14, 2026, 01:38 PM UTC

    We have observed a recovery in SMS delivery from Twilio to AT&T network subscribers in Mexico and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  7. resolved Apr 14, 2026, 02:22 PM UTC

    The incident has been resolved and SMS delivery from Twilio to AT&T network subscribers in Mexico is operating normally.

Read the full incident report →

Minor April 13, 2026

Unexpected 503 Errors When Connecting to Twilio APIs

Detected by Pingoru
Apr 13, 2026, 08:13 PM UTC
Resolved
Apr 13, 2026, 11:14 PM UTC
Duration
3h
Affected: REST API
Timeline · 5 updates
  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.

Read the full incident report →

Minor April 13, 2026

SMS Delivery Failures from a Subset of Twilio Long Codes to Orange Côte d'Ivoire

Detected by Pingoru
Apr 13, 2026, 06:42 PM UTC
Resolved
Apr 14, 2026, 12:49 PM UTC
Duration
18h 6m
Affected: SMS, Middle East & Africa
Timeline · 7 updates
  1. identified Apr 13, 2026, 06:42 PM UTC

    Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Long Codes to Orange network subscribers in Côte d'Ivoire. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. identified Apr 13, 2026, 07:43 PM UTC

    Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Long Codes to Orange network subscribers in Côte d'Ivoire. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.

  3. identified Apr 13, 2026, 09:43 PM UTC

    Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Long Codes to Orange network subscribers in Côte d'Ivoire. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available.

  4. identified Apr 14, 2026, 01:46 AM UTC

    Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Long Codes to Orange network subscribers in Côte d'Ivoire. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 8 hours or as soon as more information becomes available.

  5. monitoring Apr 14, 2026, 06:39 AM UTC

    We have observed a recovery in SMS delivery from a subset of Twilio Long Codes to Orange network subscribers in Côte d'Ivoire and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  6. monitoring Apr 14, 2026, 08:54 AM UTC

    We have observed a recovery in SMS delivery from a subset of Twilio Long Codes to Orange network subscribers in Côte d'Ivoire and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.

  7. resolved Apr 14, 2026, 12:49 PM UTC

    The incident has been resolved and SMS delivery from a subset of Twilio Long Codes to Orange network subscribers in Côte d'Ivoire is operating normally.

Read the full incident report →

Minor April 13, 2026

User Authentication Identity SNA Failures for T-Mobile in United States

Detected by Pingoru
Apr 13, 2026, 06:38 PM UTC
Resolved
Apr 14, 2026, 12:20 AM UTC
Duration
5h 41m
Affected: Verify Silent Network AuthLookup SIM Swap
Timeline · 6 updates
  1. investigating Apr 13, 2026, 06:38 PM UTC

    Twilio customers may be experiencing User Authentication Identity API errors for T-Mobile in the United States. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. identified Apr 13, 2026, 06:58 PM UTC

    Twilio customers may be experiencing User Authentication Identity API errors for T-Mobile in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  3. identified Apr 13, 2026, 08:08 PM UTC

    Twilio customers may be experiencing User Authentication Identity SNA failures for T-Mobile in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  4. identified Apr 13, 2026, 09:14 PM UTC

    Twilio customers may be experiencing User Authentication Identity SNA failures for T-Mobile in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.

  5. monitoring Apr 13, 2026, 10:14 PM UTC

    We have observed a recovery in User Authentication Identity for T-Mobile in the United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  6. resolved Apr 14, 2026, 12:20 AM UTC

    The incident has been resolved and User Authentication Identity for T-Mobile in the United States is operating normally.

Read the full incident report →

Minor April 13, 2026

SMS Delivery Failures from Twilio to Beeline Kazakhstan

Detected by Pingoru
Apr 13, 2026, 05:45 PM UTC
Resolved
Apr 14, 2026, 01:04 AM UTC
Duration
7h 19m
Affected: SMS, APAC
Timeline · 3 updates
  1. investigating Apr 13, 2026, 05:45 PM UTC

    Twilio customers may be experiencing SMS delivery failures from Twilio to Beeline network subscribers in Kazakhstan. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. identified Apr 13, 2026, 05:47 PM UTC

    Twilio customers may be experiencing SMS delivery failures from Twilio to Beeline network subscribers in Kazakhstan. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  3. resolved Apr 14, 2026, 01:04 AM UTC

    We are no longer experiencing SMS delivery failures from Twilio to Beeline network subscribers in Kazakhstan. This incident has been resolved.

Read the full incident report →

Minor April 13, 2026

SMS Delivery Delays from Twilio to Shelcomm United States

Detected by Pingoru
Apr 13, 2026, 04:47 AM UTC
Resolved
Apr 13, 2026, 08:54 AM UTC
Duration
4h 6m
Affected: Other
Timeline · 6 updates
  1. investigating Apr 13, 2026, 04:47 AM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to Shelcomm network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. identified Apr 13, 2026, 04:54 AM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to Shelcomm network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  3. identified Apr 13, 2026, 05:20 AM UTC

    We are continuing to work on a fix for this issue.

  4. identified Apr 13, 2026, 05:54 AM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to Shelcomm network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.

  5. monitoring Apr 13, 2026, 06:48 AM UTC

    We have observed a recovery in SMS delivery from Twilio to Shelcomm network subscribers in the United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  6. resolved Apr 13, 2026, 08:54 AM UTC

    The incident has been resolved and SMS delivery from Twilio to Shelcomm network subscribers in the United States is operating normally.

Read the full incident report →

Notice April 13, 2026

OhSip E2E test failures

Detected by Pingoru
Apr 13, 2026, 04:18 AM UTC
Resolved
Apr 13, 2026, 04:37 AM UTC
Duration
18m
Timeline · 2 updates
  1. investigating Apr 13, 2026, 04:18 AM UTC

    Our monitoring systems have detected a potential issue with OhSip E2E test failures. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

  2. resolved Apr 13, 2026, 04:37 AM UTC

    We have fully investigated the issue triggered by our automated alert, and it was determined that there is no noticeable customer impact. All systems are operational.

Read the full incident report →

Minor April 12, 2026

SMS Delivery Failures from Network Subscribers to a Subset of Twilio Brazil Phone Numbers

Detected by Pingoru
Apr 12, 2026, 04:33 PM UTC
Resolved
Apr 12, 2026, 07:13 PM UTC
Duration
2h 40m
Affected: SMS, Latin America
Timeline · 3 updates
  1. investigating Apr 12, 2026, 04:33 PM UTC

    Twilio customers may be experiencing SMS delivery failures from network subscribers in Brazil to a subset of Twilio Phone Numbers. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. monitoring Apr 12, 2026, 05:34 PM UTC

    We have observed a recovery in SMS delivery from network subscribers in Brazil to a subset of Twilio Phone Numbers and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  3. resolved Apr 12, 2026, 07:13 PM UTC

    The incident has been resolved and SMS delivery from network subscribers to a subset of Twilio Brazil Phone Numbers is operating normally.

Read the full incident report →