Twilio Outage History

Twilio degraded · 8 active incidents · 1 long-running issue View live status →

Pingoru has recorded 1,183 incidents for Twilio: 1,178 in the last 12 months and 560 in the last 90 days.

Source: status.twilio.com · Aggregated across Twilio products

1,183incidents recorded
1,178last 12 months
560last 90 days
17 hourstypical duration
Incidents per month
0100200AprMayJunJulAugSepOct153
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct95%
Pingoru began tracking Twilio in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026105531 of 720 (74%)
May 2026164744 of 744 (100%)
June 2026150619 of 720 (86%)
July 2026198718 of 744 (96%)
August 2026195716 of 744 (96%)
September 2026179720 of 720 (100%)
October 2026153570 of 602 (95%)

Incidents, newest first

Minor May 14, 2026 SMS Delivery Delays from Twilio to Multiple Networks in Brunei Darussalam 17h 30m SMS, APAC

Started May 14, 2026, 03:10 PM UTC· resolved May 15, 2026, 08:40 AM UTC

  1. investigating May 14, 2026, 03:10 PM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to network subscribers on multiple networks in Brunei Darussalam. 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 May 14, 2026, 04:10 PM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to network subscribers on multiple networks in Brunei Darussalam. Our team is actively investigating this issue. We will provide another update in 2 hours or as soon as more information becomes available.

  3. investigating May 14, 2026, 06:11 PM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to network subscribers on multiple networks in Brunei Darussalam. Our team is actively investigating this issue. We will provide another update in 4 hours or as soon as more information becomes available.

  4. identified May 14, 2026, 08:47 PM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to network subscribers on multiple networks in Brunei Darussalam. 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 May 14, 2026, 09:49 PM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to network subscribers on multiple networks in Brunei Darussalam. 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. identified May 14, 2026, 11:55 PM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to network subscribers on multiple networks in Brunei Darussalam. 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.

  7. identified May 15, 2026, 03:57 AM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from Twilio to network subscribers on multiple networks in Brunei Darussalam. 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.

  8. monitoring May 15, 2026, 07:15 AM UTC

    We have observed a recovery in SMS delivery from Twilio to network subscribers on multiple networks in Brunei Darussalam and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  9. resolved May 15, 2026, 08:40 AM UTC

    The incident has been resolved and SMS delivery from Twilio to affected networks in Brunei Darussalam is operating normally.

Read the full incident report →

Minor May 14, 2026 Conversation Intelligence (Classic) is Unavailable in the new Console 3h 27m Conversation Intelligence (classic)

Started May 14, 2026, 08:25 AM UTC· resolved May 14, 2026, 11:52 AM UTC

  1. investigating May 14, 2026, 08:25 AM UTC

    Currently Conversation Intelligence (classic) is unavailable in the new console to manage Intelligence Services and Language Operators. Our engineers are working to make it available for customers again. We will provide another update in 1 hour or as soon as more information becomes available.

  2. investigating May 14, 2026, 09:18 AM UTC

    We are still investigating the issue where the Conversation Intelligence (classic) is unavailable in the new console to manage Intelligence Services and Language Operators. Our engineers are working to make it available for customers again. We will provide another update in 2 hours or as soon as more information becomes available.

  3. monitoring May 14, 2026, 11:17 AM UTC

    We have observed a recovery where the Conversation Intelligence (classic) is unavailable in the new console to manage Intelligence Services and Language Operators. We will provide another update in 30 minutes or as soon as more information becomes available.

  4. monitoring May 14, 2026, 11:48 AM UTC

    We are still observing recovery where the Conversation Intelligence (classic) is unavailable in the new console to manage Intelligence Services and Language Operators. We will provide another update in 30 minutes or as soon as more information becomes available.

  5. resolved May 14, 2026, 11:52 AM UTC

    The issue affecting the Conversation Intelligence (classic) has been resolved and is operating normally at this time.

Read the full incident report →

Minor May 14, 2026 SMS Delivery Delays from a Subset of Twilio to SCO Mobile Pakistan 3h 22m SMS, APAC

Started May 14, 2026, 04:40 AM UTC· resolved May 14, 2026, 08:03 AM UTC

  1. investigating May 14, 2026, 04:40 AM UTC

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Phone Numbers to SCO Mobile network subscribers in Pakistan. 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 May 14, 2026, 04:41 AM UTC

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Phone Numbers to SCO Mobile network subscribers in Pakistan. 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 May 14, 2026, 05:42 AM UTC

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio to SCO Mobile network subscribers in Pakistan. 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. monitoring May 14, 2026, 06:15 AM UTC

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

  5. resolved May 14, 2026, 08:03 AM UTC

    The incident has been resolved and SMS delivery from a subset of Twilio to SCO Mobile network subscribers in Pakistan is operating normally.

Read the full incident report →

Minor May 13, 2026 Twilio Accounts May Not Be Able to Capture Speech Using <gather> 44m TwiML US1, TwiML AU1, TwiML IE1

Started May 13, 2026, 09:25 PM UTC· resolved May 13, 2026, 10:10 PM UTC

  1. investigating May 13, 2026, 09:25 PM UTC

    We are currently investigating an issue where Twilio accounts may not be able to capture speech using "gather" verb. We expect to provide another update in 1 hour or as soon as more information becomes available.

  2. resolved May 13, 2026, 10:10 PM UTC

    We have fully investigated the issue where Twilio accounts may not be able to capture speech using "gather" verb, and it was determined that there is no noticeable customer impact. All systems are operational.

Read the full incident report →

Minor May 13, 2026 Issues Retrieving Transcripts 48m Conversation Intelligence (classic)

Started May 13, 2026, 03:54 PM UTC· resolved May 13, 2026, 04:43 PM UTC

  1. investigating May 13, 2026, 03:54 PM UTC

    Our monitoring systems have detected a potential issue with Conversation intelligence v2 Dynamo db failures. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

  2. monitoring May 13, 2026, 04:10 PM UTC

    Some customers experienced issues retrieving transcripts between 15:04 and 15:46 UTC due to an issue with one of our Transcript Store services, this is 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.

  3. resolved May 13, 2026, 04:43 PM UTC

    Issue Retrieving Transcripts has been resolved and is operating normally at this time.

Read the full incident report →

Notice May 13, 2026 Intermittent long latency on mail send API – API v3, SMTP, Event Webhooks, API v2 and 9 more

Started May 13, 2026, 03:30 PM UTC· resolved May 13, 2026, 03:30 PM UTC

  1. resolved May 28, 2026, 01:38 AM UTC

    Customers in US-East may have experienced intermittent high mail send latency from 5/13/2026 to 5/27/2026. Our engineers have investigated and resolved the issue. All impacted services are operating normally.

Read the full incident report →

Minor May 13, 2026 Messages delayed on RCS and WhatsApp 1h 39m RCS Messaging

Started May 13, 2026, 01:57 AM UTC· resolved May 13, 2026, 03:36 AM UTC

  1. investigating May 13, 2026, 01:57 AM UTC

    We are experiencing delays on RCA Whatsapp messages. Customer may encounter error 21611 during this time. Our engineers are working to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available

  2. investigating May 13, 2026, 02:02 AM UTC

    We are experiencing delays on RCS and WhatsApp messages. Customers may encounter messages queueing longer than expected during this time. Our engineers are working to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.

  3. investigating May 13, 2026, 02:55 AM UTC

    We are experiencing delays on RCS and WhatsApp messages. Customers may encounter messages queueing longer than expected during this time. Our engineers are working to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.

  4. resolved May 13, 2026, 03:36 AM UTC

    The issue has been resolved and we are no longer experiencing delays on RCS and WhatsApp messages.

Read the full incident report →

Notice May 12, 2026 SendGrid - Subset to email services experiencing 5xx errors 34m SendGrid Website, SendGrid Statistics

Started May 12, 2026, 11:48 PM UTC· resolved May 13, 2026, 12:22 AM UTC

  1. monitoring May 12, 2026, 11:48 PM UTC

    Starting around 16:20 PST on 04/12/2026, our engineers began investigating an issue with a subset of services experiencing 5xx errors. Users may have experienced issues when accessing subusers, authenticating domains and link branding records, accessing the account, and checking account stats. This does not impact mail send. Our engineers have implemented a fix and are monitoring system performance. We will provide another update in an hour or as soon as more information becomes available.

  2. resolved May 13, 2026, 12:22 AM UTC

    Our engineers have monitored the fix and confirmed all services are now operating normally.

Read the full incident report →

Minor May 12, 2026 Customer Low Balance Notification and Automatic Recharge of Balance Is Not Working 12h 20m Billing

Started May 12, 2026, 11:02 PM UTC· resolved May 13, 2026, 11:23 AM UTC

  1. investigating May 12, 2026, 05:09 PM UTC

    Our monitoring systems have detected a potential issue with Credit cards will not be charged for PAYG. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

  2. investigating May 12, 2026, 05:29 PM UTC

    Our engineering team has identified an issue affecting customer low balance notifications and the automatic balance recharge feature. We are actively working to deploy a fix. We will provide an update in 1 hour, or sooner if additional information becomes available.

  3. investigating May 12, 2026, 06:05 PM UTC

    We are still investigating an issue affecting customer low balance notifications and the automatic balance recharge feature. We are actively working to deploy a fix. We will provide an update in 2 hours, or sooner if additional information becomes available.

  4. identified May 12, 2026, 06:24 PM UTC

    Our engineering team has identified an issue affecting customer low balance notifications and the automatic balance recharge feature. We are actively working to deploy a fix. We will provide an update in 1 hour, or sooner if additional information becomes available.

  5. monitoring May 12, 2026, 07:05 PM UTC

    Our engineers have implemented a fix and we are now seeing billing processing as expected. We are monitoring system performance and will provide another update in 2 hours or as soon as more information becomes available.

  6. monitoring May 12, 2026, 09:01 PM UTC

    Our engineers have implemented a fix and we are now seeing billing processing as expected. We continue monitoring system performance and will provide another update in 2 hours or as soon as more information becomes available.

  7. monitoring May 12, 2026, 11:02 PM UTC

    Our engineers have implemented a fix and we are now seeing billing processing as expected. We continue monitoring system performance and will provide another update in 30 minutes or as soon as more information becomes available.

  8. monitoring May 13, 2026, 01:03 AM UTC

    Our engineers have implemented a fix and we are now seeing billing processing as expected. We continue monitoring system performance and will provide another update in 4 hours or as soon as more information becomes available.

  9. monitoring May 13, 2026, 04:54 AM UTC

    Our engineers have implemented a fix and we are now seeing billing processing as expected. We continue monitoring system performance and will provide another update in 4 hours or as soon as more information becomes available.

  10. monitoring May 13, 2026, 08:54 AM UTC

    Our engineers have implemented a fix and we are now seeing billing processing as expected. We continue monitoring system performance and will provide another update in 8 hours or as soon as more information becomes available.

  11. resolved May 13, 2026, 11:23 AM UTC

    The issue affecting low balance notifications and the automatic balance recharge feature has been resolved and is operating normally at this time.

Read the full incident report →

Minor May 12, 2026 Teammates invited to SendGrid are prompted to create standalone Unified accounts instead of joining the inviting one 1h 48m API v3, SMTP, Event Webhooks, API v2 and 9 more

Started May 12, 2026, 04:31 PM UTC· resolved May 12, 2026, 06:20 PM UTC

  1. investigating May 12, 2026, 04:31 PM UTC

    Starting around 9 AM PDT on Tuesday, 5/12/2026, our engineers started investigating an issue with teammates, where invitees could not join their organizations and instead they were led to creating standalone Twilio Unified accounts. New teammates, therefore, are unable to join their organizations at the time. This issue does not impact mail send. We will provide another update in an hour or as soon as more information becomes available.

  2. identified May 12, 2026, 04:59 PM UTC

    Our engineers have identified the issue and are working toward a fix. We will provide another update in one hour or as soon as more information becomes available.

  3. monitoring May 12, 2026, 05:13 PM UTC

    Our engineers have implemented a fix and are monitoring system performance. Teammates that were impacted by the issue need to request a new invite link and delete cache and cookies on their browsers before attempting to join again. We will provide another update in one hour or as soon as more information becomes available.

  4. resolved May 12, 2026, 06:20 PM UTC

    Our engineers have monitored the fix and confirmed the issue with teammate account creation has been resolved. All services are now operating normally at this time.

Read the full incident report →

Minor May 12, 2026 SMS Delivery Delays from a Subset of Twilio Short Codes to C-Spire United States 6h 51m SMS Short Code, North America

Started May 12, 2026, 04:24 PM UTC· resolved May 12, 2026, 11:16 PM UTC

  1. investigating May 12, 2026, 04:24 PM UTC

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to C-Spire 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 May 12, 2026, 04:30 PM UTC

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to C-Spire 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 May 12, 2026, 05:31 PM UTC

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to C-Spire 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.

  4. identified May 12, 2026, 07:33 PM UTC

    Twilio customers may be experiencing SMS delivery delays from a subset of Twilio Short Codes to C-Spire 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 4 hours or as soon as more information becomes available.

  5. monitoring May 12, 2026, 09:20 PM UTC

    We have observed a recovery in SMS delivery from a subset of Twilio Short Codes to C-Spire 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 May 12, 2026, 11:16 PM UTC

    The incident has been resolved and SMS delivery from a subset of Twilio Short Codes to C-Spire network subscribers in the United States is operating normally.

Read the full incident report →

Notice May 12, 2026 Notify SMS Requests Failed With 500s Errors if the Request Landed on OTK Pods – Notify

Started May 12, 2026, 01:41 PM UTC· resolved May 12, 2026, 01:41 PM UTC

  1. resolved May 12, 2026, 01:41 PM UTC

    Notify SMS was degraded between 05/06/2026, 23:00 and 05/11/2026, 7:00 Pacific Time. During this period of time customers may have experienced Notify: SMS requests not getting delivered to users. The issue has now been resolved.

Read the full incident report →

Minor May 12, 2026 Voice Call Failures from Peru to a Subset of Twilio Peru Phone Numbers 1h 43m Voice, Latin America

Started May 12, 2026, 12:49 PM UTC· resolved May 12, 2026, 02:33 PM UTC

  1. investigating May 12, 2026, 12:49 PM UTC

    Twilio customers may be experiencing voice call failures from network subscribers in Peru to a subset of Twilio Peru 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 May 12, 2026, 01:16 PM UTC

    We have observed a recovery in voice calls from network subscribers in Peru to a subset of Twilio Peru 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 May 12, 2026, 02:33 PM UTC

    The incident has been resolved and voice calls from network subscribers in Peru to a subset of Twilio Peru Phone Numbers are operating normally.

Read the full incident report →

Notice May 12, 2026 DLR Degradation for a Subset of SMPP API Customers. – SMPP

Started May 12, 2026, 09:32 AM UTC· resolved May 12, 2026, 09:32 AM UTC

  1. resolved May 12, 2026, 09:32 AM UTC

    A small set of SMPP API Customers were affected by issues with DLR deliveries between 2026-05-07 23:53 UTC and 2026-05-11 13:46 UTC. During this time some DLRs may not have been delivered to the end customer. All systems are fully operational

Read the full incident report →

Minor May 12, 2026 SMS Delivery Failures from a Subset of Twilio Toll-Free Numbers to Multiple Networks in United States 7h 54m SMS Toll-Free, North America, SMS Toll-Free, North America

Started May 12, 2026, 07:03 AM UTC· resolved May 12, 2026, 02:58 PM UTC

  1. investigating May 12, 2026, 07:03 AM UTC

    Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Toll-Free Numbers to 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 May 12, 2026, 07:41 AM UTC

    Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Toll-Free Numbers to 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 May 12, 2026, 08:43 AM UTC

    Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Toll-Free Numbers to 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.

  4. identified May 12, 2026, 10:49 AM UTC

    Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Toll-Free Numbers to the United States. 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 May 12, 2026, 02:50 PM UTC

    Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Toll-Free Numbers to the United States. 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.

  6. resolved May 12, 2026, 02:58 PM UTC

    We have completed our investigation and determined that this event did not result in any customer impact. All systems are operating normally.

Read the full incident report →

Notice May 12, 2026 Outage on messaging insights –

Started May 12, 2026, 07:00 AM UTC· resolved May 12, 2026, 07:00 AM UTC

  1. resolved May 12, 2026, 07:00 AM UTC

    Few customers may have experienced failures in Messaging Insights between May 7, 2026 23:45 UTC and May 8, 2026 00:20 UTC, caused by a AWS outage. The impact has been mitigated.

Read the full incident report →

Minor May 12, 2026 SMS Delivery Delays from Twilio to Vodafone Germany 4h 34m SMS, Europe

Started May 12, 2026, 02:25 AM UTC· resolved May 12, 2026, 07:00 AM UTC

  1. investigating May 12, 2026, 02:25 AM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to Vodafone Germany. 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 May 12, 2026, 02:29 AM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to Vodafone Germany. 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 May 12, 2026, 03:30 AM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to Vodafone Germany. 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. monitoring May 12, 2026, 04:57 AM UTC

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

  5. resolved May 12, 2026, 07:00 AM UTC

    The incident has been resolved and SMS delivery from Twilio to Vodafone network subscribers in Germany is operating normally.

Read the full incident report →

Minor May 11, 2026 SMS Delivery Delays and Failures from Twilio to Djibouti Telecom (Evatis), Djibouti 19h 49m SMS, Middle East & Africa

Started May 11, 2026, 06:58 PM UTC· resolved May 12, 2026, 02:47 PM UTC

  1. investigating May 11, 2026, 06:58 PM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from Twilio Phone Numbers to Djibouti Telecom (Evatis) network subscribers in Djibouti. 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 May 11, 2026, 07:58 PM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from Twilio Phone Numbers to Djibouti Telecom (Evatis) network subscribers in Djibouti. Our team is actively investigating this issue. We will provide another update in 2 hours or as soon as more information becomes available.

  3. investigating May 11, 2026, 09:59 PM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from Twilio to Djibouti Telecom (Evatis) network subscribers in Djibouti. Our team is actively investigating this issue. We will provide another update in 4 hours or as soon as more information becomes available.

  4. investigating May 12, 2026, 02:07 AM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from Twilio Phone Numbers to Djibouti Telecom (Evatis) network subscribers in Djibouti. Our team is actively investigating this issue. We will provide another update in 8 hours or as soon as more information becomes available.

  5. identified May 12, 2026, 06:38 AM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from Twilio Phone Numbers to Djibouti Telecom (Evatis) network subscribers in Djibouti. 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.

  6. identified May 12, 2026, 07:39 AM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from Twilio Phone Numbers to Djibouti Telecom (Evatis) network subscribers in Djibouti. 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.

  7. identified May 12, 2026, 09:44 AM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from Twilio Phone Numbers to Djibouti Telecom (Evatis) network subscribers in Djibouti. 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.

  8. monitoring May 12, 2026, 01:20 PM UTC

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

  9. resolved May 12, 2026, 02:47 PM UTC

    The incident has been resolved and SMS delivery from Twilio to Djibouti Telecom (Evatis) network subscribers in Djibouti is operating normally.

Read the full incident report →

Minor May 11, 2026 SMS Delivery Delays from Twilio to Tigo Bolivia 10h 1m SMS, Latin America

Started May 11, 2026, 06:11 PM UTC· resolved May 12, 2026, 04:13 AM UTC

  1. investigating May 11, 2026, 06:11 PM UTC

    Twilio customers may be experiencing SMS delivery receipt delays from Twilio to Tigo network subscribers in Bolivia. Our team is actively investigating this issue. Message delivery may succeed, but delivery receipts may be delayed. We will provide another update in 1 hour or as soon as more information becomes available.

  2. identified May 11, 2026, 06:38 PM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio Phone Numbers to Tigo network subscribers in Bolivia. 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 May 11, 2026, 07:38 PM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio Phone Numbers to Tigo network subscribers in Bolivia. 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 May 11, 2026, 09:39 PM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio Phone Numbers to Tigo network subscribers in Bolivia. 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 May 11, 2026, 10:38 PM UTC

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

  6. monitoring May 12, 2026, 12:39 AM UTC

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

  7. resolved May 12, 2026, 04:13 AM UTC

    The incident has been resolved and SMS delivery from Twilio to Tigo network subscribers in Bolivia is operating normally.

Read the full incident report →

Minor May 11, 2026 SMS Delivery Delays and Failures from a Subset of Twilio Long Codes to U Mobile Malaysia 13h 13m SMS, APAC

Started May 11, 2026, 05:22 PM UTC· resolved May 12, 2026, 06:36 AM UTC

  1. investigating May 11, 2026, 05:22 PM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from a subset of Twilio Long Codes to U Mobile network subscribers in Malaysia. 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 May 11, 2026, 05:30 PM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from a subset of Twilio Long Codes to U Mobile network subscribers in Malaysia. 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 May 11, 2026, 06:30 PM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from a subset of Twilio Long Codes to U Mobile network subscribers in Malaysia. 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 May 11, 2026, 08:30 PM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from a subset of Twilio Long Codes to U Mobile network subscribers in Malaysia. 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. identified May 12, 2026, 12:31 AM UTC

    Twilio customers may be experiencing SMS delivery delays and failures from a subset of Twilio Long Codes to U Mobile network subscribers in Malaysia. 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.

  6. monitoring May 12, 2026, 03:18 AM UTC

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

  7. monitoring May 12, 2026, 05:19 AM UTC

    We have observed a recovery in SMS delivery from a subset of Twilio Long Codes to U Mobile network subscribers in Malaysia and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.

  8. resolved May 12, 2026, 06:36 AM UTC

    The incident has been resolved and SMS delivery from a subset of Twilio Long Codes to U Mobile network subscribers in Malaysia is operating normally.

Read the full incident report →

Minor May 11, 2026 RCS Message Delivery Delays via AT&T 6h 37m RCS Messaging

Started May 11, 2026, 04:17 PM UTC· resolved May 11, 2026, 10:54 PM UTC

  1. identified May 11, 2026, 04:17 PM UTC

    Customers might be experiencing delays in RCS message delivery to ATT devices. Customers who have fallback to sms enabled could be experiencing higher rate of messages falling back to sms for ATT recipients. We expect to provide another update in 1 hour or as soon as more information becomes available.

  2. identified May 11, 2026, 05:18 PM UTC

    We are still experiencing delays in RCS message delivery to ATT devices. Customers who have fallback to sms enabled could be experiencing higher rate of messages falling back to sms for ATT recipients. We expect to provide another update in 2 hours or as soon as more information becomes available.

  3. identified May 11, 2026, 07:17 PM UTC

    We are still experiencing delays in RCS message delivery to ATT devices. Customers who have fallback to sms enabled could be experiencing higher rate of messages falling back to sms for ATT recipients. We expect to provide another update in 4 hours or as soon as more information becomes available.

  4. monitoring May 11, 2026, 10:23 PM UTC

    RCS message delivery to ATT devices is 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 May 11, 2026, 10:54 PM UTC

    The issue with delays in RCS message delivery to ATT devices has been resolved and RCS message delivery is operating normally at this time.

Read the full incident report →

Minor May 11, 2026 Voice Call Audio Quality Degradation between a Subset of Twilio United States Phone Numbers and T-Mobile in United States 2d 5h Voice, North America

Started May 11, 2026, 04:04 PM UTC· resolved May 13, 2026, 09:11 PM UTC

  1. investigating May 11, 2026, 04:04 PM UTC

    Twilio customers may be experiencing voice call audio quality degradation between a subset of Twilio Phone Numbers and T-Mobile 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 May 11, 2026, 04:27 PM UTC

    Twilio customers may be experiencing voice call audio quality degradation between a subset of Twilio Phone Numbers and T-Mobile 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 May 11, 2026, 05:30 PM UTC

    Twilio customers may be experiencing voice call audio quality degradation between a subset of Twilio Phone Numbers and T-Mobile 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.

  4. identified May 11, 2026, 07:31 PM UTC

    Twilio customers may be experiencing voice call audio quality degradation between a subset of Twilio Phone Numbers and T-Mobile 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 4 hours or as soon as more information becomes available.

  5. identified May 11, 2026, 11:31 PM UTC

    Twilio customers may be experiencing voice call audio quality degradation between a subset of Twilio Phone Numbers and T-Mobile 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 8 hours or as soon as more information becomes available.

  6. monitoring May 11, 2026, 11:43 PM UTC

    We have observed a recovery in voice calls between a subset of Twilio Phone Numbers and T-Mobile 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.

  7. monitoring May 12, 2026, 01:49 AM UTC

    We have observed a recovery in voice calls between a subset of Twilio Phone Numbers and T-Mobile network subscribers in the United States and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.

  8. monitoring May 12, 2026, 05:55 AM UTC

    We have observed a recovery in voice calls between a subset of Twilio Phone Numbers and T-Mobile network subscribers in the United States and are monitoring service stability. We will provide another update in 8 hours or as soon as more information becomes available.

  9. monitoring May 12, 2026, 01:55 PM UTC

    We have observed a recovery in voice calls between a subset of Twilio United States Phone Numbers and T-Mobile network subscribers in the United States and are monitoring service stability. We will provide another update in 16 hours or as soon as more information becomes available.

  10. identified May 12, 2026, 03:58 PM UTC

    Twilio customers may be experiencing voice call audio quality degradation between a subset of Twilio Phone Numbers and T-Mobile 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.

  11. monitoring May 12, 2026, 04:58 PM UTC

    We have observed a recovery in voice calls between a subset of Twilio Phone Numbers and T-Mobile 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.

  12. monitoring May 12, 2026, 06:59 PM UTC

    We have observed a recovery in voice calls between a subset of Twilio United States Phone Numbers and T-Mobile network subscribers in the United States and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.

  13. monitoring May 12, 2026, 11:00 PM UTC

    We have observed a recovery in voice calls between a subset of Twilio United States Phone Numbers and T-Mobile network subscribers in the United States and are monitoring service stability. We will provide another update in 8 hours or as soon as more information becomes available.

  14. monitoring May 13, 2026, 07:00 AM UTC

    We have observed a recovery in voice calls between a subset of Twilio United States Phone Numbers and T-Mobile network subscribers in the United States and are monitoring service stability. We will provide another update in 16 hours or as soon as more information becomes available.

  15. resolved May 13, 2026, 09:11 PM UTC

    The incident has been resolved and voice calls between a subset of Twilio United States Phone Numbers and T-Mobile network subscribers in the United States are operating normally.

Read the full incident report →

Minor May 11, 2026 Conversations Classic Customers Can Experience Issues With Delivery Receipts Functionality 1h 9m Conversations

Started May 11, 2026, 03:17 PM UTC· resolved May 11, 2026, 04:26 PM UTC

  1. identified May 11, 2026, 03:17 PM UTC

    Our engineers have identified the issue with Conversations Classic and are working to deploy a fix. We expect to provide another update in 1 hour or as soon as more information becomes available.

  2. identified May 11, 2026, 03:42 PM UTC

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

  3. monitoring May 11, 2026, 03:54 PM UTC

    Conversations Classic is 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.

  4. resolved May 11, 2026, 04:26 PM UTC

    Issue with Conversations Classic has been resolved and delivery receipts functionality is operating normally at this time.

Read the full incident report →

Minor May 11, 2026 SMS Delivery Delays from Twilio to Panhandle Telecommunication Systems Inc. United States 3h 16m SMS Long Code, North America, SMS Short Code, North America, SMS Toll-Free, North America, SMS Toll-Free, North America

Started May 11, 2026, 01:12 PM UTC· resolved May 11, 2026, 04:28 PM UTC

  1. investigating May 11, 2026, 01:12 PM UTC

    Twilio customers may be experiencing SMS delivery delays from Twilio to Panhandle Telecommunication Systems Inc. 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. monitoring May 11, 2026, 02:08 PM UTC

    We have observed a recovery in SMS delivery from Twilio to Panhandle Telecommunication Systems Inc. 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.

  3. monitoring May 11, 2026, 04:10 PM UTC

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

  4. resolved May 11, 2026, 04:28 PM UTC

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

Read the full incident report →

Notice May 11, 2026 One Console Billing Insights Usage Summary Page Is Broken – Billing

Started May 11, 2026, 01:09 PM UTC· resolved May 11, 2026, 01:09 PM UTC

  1. resolved May 11, 2026, 01:09 PM UTC

    We have mitigated an issue on One Console Usage pages that impacted some of our customers. The service is now operating normally, and we will continue to monitor for system stability.

Read the full incident report →