- Detected by Pingoru
- Mar 23, 2026, 11:51 AM UTC
- Resolved
- Mar 23, 2026, 12:57 PM UTC
- Duration
- 1h 5m
Affected: Twilio Flex Application Platform
Timeline · 3 updates
-
investigating Mar 23, 2026, 11:51 AM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Mar 23, 2026, 11:57 AM UTC
Twilio customers may be experiencing intermittent authentication failures when attempting to access Twilio Flex. Twilio engineers have been alerted and are actively working to identify the root cause. We will provide another update in 1 hour or as soon as more information becomes available.
-
resolved Mar 23, 2026, 12:57 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 01:35 PM UTC
- Resolved
- Mar 19, 2026, 04:53 PM UTC
- Duration
- 3h 17m
Affected: Twilio PSTNTwilio Voice, APACTwilio Voice, Europe
Timeline · 4 updates
-
investigating Mar 19, 2026, 01:35 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Mar 19, 2026, 01:38 PM UTC
Twilio customers may be experiencing voice call failures from network subscribers to Twilio Phone Numbers in France, Norway, Italy, Indonesia, and Denmark. The Twilio team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.
-
monitoring Mar 19, 2026, 04:04 PM UTC
Twilio have observed a recovery in voice calls from network subscribers in multiple countries to Twilio Phone Numbers and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
-
resolved Mar 19, 2026, 04:53 PM UTC
The incident has been resolved and voice calls from network subscribers to Twilio Phone Numbers are operating normally.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 09:33 PM UTC
- Resolved
- Mar 19, 2026, 01:02 AM UTC
- Duration
- 3h 28m
Affected: Twilio Programmable Messaging
Timeline · 4 updates
-
investigating Mar 18, 2026, 09:33 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Mar 18, 2026, 09:36 PM UTC
Twilio monitoring systems have detected a potential issue with High latency impacting outgoing messages for msg-send. Their engineers have been alerted and are investigating. We will provide an update when we have more details.
-
investigating Mar 18, 2026, 10:45 PM UTC
We are continuing to investigate this issue.
-
resolved Mar 19, 2026, 01:02 AM UTC
The High latency issue on outgoing messages for Programmable Messaging API has been resolved and service is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 06:02 PM UTC
- Resolved
- Mar 16, 2026, 07:22 PM UTC
- Duration
- 1h 19m
Affected: Twilio Messaging Channels
Timeline · 3 updates
-
investigating Mar 16, 2026, 06:02 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Mar 16, 2026, 06:05 PM UTC
Some customers may not be receiving the status of outbound messages on their Status Callback webhook for WhatsApp. Twilio engineers have been alerted and are investigation. We will post another update in 30 minutes.
-
resolved Mar 16, 2026, 07:22 PM UTC
The issue with customers not receiving the status of outbound messages on their Status Callback webhook for WhatsApp has been resolved and Status Callback webhook for WhatsApp is operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 04:55 PM UTC
- Resolved
- Mar 16, 2026, 07:30 PM UTC
- Duration
- 2h 35m
Timeline · 2 updates
-
investigating Mar 16, 2026, 04:55 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
resolved Mar 16, 2026, 07:30 PM UTC
Twilio are no longer experiencing reported errors for Conversations. This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 04:43 PM UTC
- Resolved
- Mar 16, 2026, 06:46 PM UTC
- Duration
- 2h 3m
Timeline · 2 updates
-
investigating Mar 16, 2026, 04:43 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
resolved Mar 16, 2026, 06:46 PM UTC
The issue affecting intermittent various pages in the Twilio Console has been resolved, and the service is functioning normally at this time.
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 07:35 AM UTC
- Resolved
- Mar 13, 2026, 09:09 AM UTC
- Duration
- 1h 34m
Affected: Cloudflare DashboardCloudflare API
Timeline · 6 updates
-
investigating Mar 13, 2026, 07:35 AM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Mar 13, 2026, 07:37 AM UTC
Cloudflare is investigating intermittent issues with Cloudflare Dashboard and related APIs. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using the Dashboard / Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.
-
identified Mar 13, 2026, 08:27 AM UTC
The issue has been identified and a fix is being implemented.
-
identified Mar 13, 2026, 08:36 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring Mar 13, 2026, 08:37 AM UTC
A fix has been implemented, and the Cloudflare Engineering team are monitoring the results.
-
resolved Mar 13, 2026, 09:09 AM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2026, 07:11 PM UTC
- Resolved
- Mar 09, 2026, 08:21 PM UTC
- Duration
- 1h 10m
Affected: Twilio Flex Programmable Chat
Timeline · 3 updates
-
investigating Mar 09, 2026, 07:11 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Mar 09, 2026, 07:14 PM UTC
Twilio monitoring systems have detected a potential issue with Flex agent page. Their engineers have been alerted and are investigating. We will provide an update when we have more details.
-
resolved Mar 09, 2026, 08:21 PM UTC
Twilio have fully investigated the Flex Agents delays or errors when fetching Interaction Participants, and it was determined that the impact was limited to a small set of customers, who have been contacted individually to address any concerns. All systems are operational.
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2026, 02:41 PM UTC
- Resolved
- Mar 10, 2026, 03:03 AM UTC
- Duration
- 12h 22m
Affected: Twilio Segment
Timeline · 4 updates
-
investigating Mar 09, 2026, 02:41 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
identified Mar 09, 2026, 08:23 PM UTC
Segment users may experience slow loading and intermittent UI errors on Audiences and Journeys pages. The team has identified the root cause of the issue and is working now to mitigate the issue.
-
identified Mar 09, 2026, 08:24 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Mar 10, 2026, 03:03 AM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 06:43 PM UTC
- Resolved
- Mar 05, 2026, 10:45 PM UTC
- Duration
- 4h 2m
Affected: Twilio Messaging Channels
Timeline · 4 updates
-
investigating Mar 05, 2026, 06:43 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Mar 05, 2026, 06:52 PM UTC
Twilio monitoring systems have detected a potential issue with WhatsApp phone numbers not being displayed correctly. Twilio engineers have been alerted and are investigating. We will provide an update when we have more details.
-
monitoring Mar 05, 2026, 10:35 PM UTC
Twilio is observing a recovery in the display of WhatsApp phone number details. We are monitoring the service to ensure a full recovery and provide another update as soon as more information becomes available.
-
resolved Mar 05, 2026, 10:45 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 07:13 PM UTC
- Resolved
- Feb 27, 2026, 07:20 PM UTC
- Duration
- 7m
Timeline · 3 updates
-
investigating Feb 27, 2026, 07:13 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Feb 27, 2026, 07:18 PM UTC
We are continuing to investigate this issue.
-
resolved Feb 27, 2026, 07:20 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 11:55 AM UTC
- Resolved
- Feb 25, 2026, 02:51 PM UTC
- Duration
- 2h 55m
Affected: Twilio SMS, Europe
Timeline · 4 updates
-
investigating Feb 25, 2026, 11:55 AM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Feb 25, 2026, 12:00 PM UTC
We are continuing to investigate this issue.
-
monitoring Feb 25, 2026, 01:59 PM UTC
Twilio have observed a recovery in SMS delivery from the United Kingdom to a subset of Twilio Long Codes and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
-
resolved Feb 25, 2026, 02:51 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Feb 23, 2026, 09:17 PM UTC
- Resolved
- Feb 24, 2026, 12:36 AM UTC
- Duration
- 3h 19m
Affected: Twilio Voice, North America
Timeline · 3 updates
-
investigating Feb 23, 2026, 09:17 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Feb 23, 2026, 09:21 PM UTC
Twilio customers may be experiencing voice calls post dial delay from twilio phone numbers to United States. Twilio engineering team is investigating the issue. We will provide another update as soon as more information becomes available.
-
resolved Feb 24, 2026, 12:36 AM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 09:52 PM UTC
- Resolved
- Feb 20, 2026, 10:24 PM UTC
- Duration
- 31m
Affected: Twilio TwiML
Timeline · 3 updates
-
investigating Feb 20, 2026, 09:52 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Feb 20, 2026, 09:55 PM UTC
Twilio monitoring systems have detected a potential issue with Programmable Voice - TwiML. Their engineering team has been alerted and are actively investigating. We will update as soon as we have more information.
-
resolved Feb 20, 2026, 10:24 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Feb 17, 2026, 07:30 PM UTC
- Resolved
- Feb 17, 2026, 07:54 PM UTC
- Duration
- 23m
Timeline · 4 updates
-
investigating Feb 17, 2026, 07:30 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Feb 17, 2026, 07:34 PM UTC
We are continuing to investigate this issue.
-
investigating Feb 17, 2026, 07:35 PM UTC
We are continuing to investigate this issue.
-
resolved Feb 17, 2026, 07:54 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Feb 13, 2026, 05:17 PM UTC
- Resolved
- Feb 13, 2026, 05:24 PM UTC
- Duration
- 7m
Affected: Twilio Voice, North America
Timeline · 3 updates
-
investigating Feb 13, 2026, 05:17 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Feb 13, 2026, 05:20 PM UTC
Twilio are observing call failures from Twilio phone numbers to Emergency Numbers in US. Twilio are currently working with their carrier partner to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
-
resolved Feb 13, 2026, 05:24 PM UTC
We have fully investigated the intermittent call failure from Twilio phone numbers to Emergency Numbers in US 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 →
- Detected by Pingoru
- Feb 12, 2026, 12:45 PM UTC
- Resolved
- Feb 13, 2026, 05:12 AM UTC
- Duration
- 16h 26m
Affected: Twilio Flex Application PlatformTwilio Flex Agent Desktop
Timeline · 6 updates
-
investigating Feb 12, 2026, 12:45 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Feb 12, 2026, 12:50 PM UTC
Twilio monitoring systems have detected a potential issue Flex. Twilio engineering teams have been alerted and are actively investigating. We will update as soon as we have more information.
-
investigating Feb 12, 2026, 02:25 PM UTC
Twilio are still investigating an issue where some Flex Agents may intermittently be unable to accept inbound voice calls. The Twilio engineering team has been engaged and is working to resolve this issue. We expect to provide another update in 2 hours or as soon as more information becomes available.
-
investigating Feb 12, 2026, 02:25 PM UTC
We are continuing to investigate this issue.
-
investigating Feb 12, 2026, 03:54 PM UTC
Twilio are still investigating an issue where some Flex Agents may intermittently be unable to accept inbound voice calls. The Twilio engineering team has been engaged and is working to resolve this issue. We expect to provide another update in 4 hours or as soon as more information becomes available.
-
resolved Feb 13, 2026, 05:12 AM UTC
Flex agents are able to operate normally, and there are no indications of service disruption or degradation.
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 06:39 PM UTC
- Resolved
- Feb 04, 2026, 08:42 PM UTC
- Duration
- 2h 2m
Affected: Twilio Console
Timeline · 3 updates
-
investigating Feb 04, 2026, 06:39 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Feb 04, 2026, 06:40 PM UTC
Twilio are investigating an error with users unable to edit WhatsApp senders within the Console. We expect to provide another update in 1 hour or as soon as more information becomes available
-
resolved Feb 04, 2026, 08:42 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 06:23 PM UTC
- Resolved
- Feb 04, 2026, 09:30 PM UTC
- Duration
- 3h 7m
Affected: Twilio Conversations
Timeline · 4 updates
-
investigating Feb 04, 2026, 06:23 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Feb 04, 2026, 06:25 PM UTC
We are continuing to investigate this issue.
-
monitoring Feb 04, 2026, 09:28 PM UTC
We are observing recovery in elevated 500s error for Conversations API. We will continue monitoring the service to ensure a full recovery. We will provide another update in 2 hours or as soon as more information becomes available.
-
resolved Feb 04, 2026, 09:30 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 12:03 PM UTC
- Resolved
- Feb 04, 2026, 02:18 PM UTC
- Duration
- 2h 14m
Affected: Twilio Conference
Timeline · 5 updates
-
investigating Feb 04, 2026, 12:03 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Feb 04, 2026, 12:05 PM UTC
Twilio are investigating an issue with increased 500 errors for Voice Conference Participants API. We expect to provide another update in 1 hour or as soon as more information becomes available.
-
investigating Feb 04, 2026, 01:53 PM UTC
Twilio are aware of increased 500 errors affecting the Twilio Calls and Conference APIs. Customers may experience failures when using the Calls or Conference APIs. Twilio team is actively investigating the root cause and has escalated this to their platform engineering team. We will provide another update in 2 hours or as soon as more information becomes available.
-
monitoring Feb 04, 2026, 01:58 PM UTC
Twilio Calls and Conference 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.
-
resolved Feb 04, 2026, 02:18 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 10:49 PM UTC
- Resolved
- Jan 28, 2026, 10:31 AM UTC
- Duration
- 11h 42m
Affected: Twilio PSTNTwilio Voice, Europe
Timeline · 6 updates
-
investigating Jan 27, 2026, 10:49 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Jan 27, 2026, 10:51 PM UTC
Twilio are observing Voice Calls Failures From Multiple Networks to a subset of Twilio Numbers in United Kingdom. Twilio are currently working with their carrier partner to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
-
monitoring Jan 27, 2026, 11:44 PM UTC
Twilio have started seeing recovery for Voice Calls Failures From Multiple Networks to a subset of Twilio Numbers in United Kingdom. They 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.
-
investigating Jan 28, 2026, 04:27 AM UTC
Twilio are continuing to observe voice call failures from multiple networks to a subset of Twilio numbers in the United Kingdom. They are currently working with their carrier partner to resolve the issue. We expect to provide another update in 4 hours or as soon as more information becomes available.
-
monitoring Jan 28, 2026, 08:12 AM UTC
Twilio has started seeing recovery for voice calls from multiple networks to a subset of Twilio numbers in the United Kingdom. Twilio will continue to monitor to ensure a full recovery. We expect to provide another update in 4 hours or as soon as more information becomes available.
-
resolved Jan 28, 2026, 10:31 AM UTC
Voice Calls Failures From Multiple Networks to a subset of Twilio Numbers in the United Kingdom have been resolved and are operating normally at this time.
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 12:29 AM UTC
- Resolved
- Jan 27, 2026, 06:09 AM UTC
- Duration
- 5h 40m
Affected: Twilio Phone Numbers
Timeline · 5 updates
-
investigating Jan 27, 2026, 12:25 AM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Jan 27, 2026, 12:29 AM UTC
Twilio are observing Inbound Call Failure To Norway Phone numbers. They are currently working with their carrier partner to resolve the issue. We expect to provide another update in 1 hour. or as soon as more information becomes available.
-
investigating Jan 27, 2026, 12:30 AM UTC
We are continuing to investigate this issue.
-
investigating Jan 27, 2026, 01:41 AM UTC
Twilio continue observing an Inbound Call Failure To Norway Phone numbers. They are currently working with their carrier partner to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.
-
resolved Jan 27, 2026, 06:09 AM UTC
The issue affecting inbound calls to Twilio Norway Phone numbers has been resolved, and the service is functioning normally at this time.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 12:13 PM UTC
- Resolved
- Jan 22, 2026, 01:07 PM UTC
- Duration
- 54m
Affected: Twilio Voice, Europe
Timeline · 3 updates
-
investigating Jan 22, 2026, 12:13 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
identified Jan 22, 2026, 12:15 PM UTC
The issue causing inbound call failures to Twilio +34 phone numbers has been identified. Twilio are actively working with their carrier partner to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
-
resolved Jan 22, 2026, 01:07 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 09:55 AM UTC
- Resolved
- Jan 22, 2026, 11:23 AM UTC
- Duration
- 1h 28m
Timeline · 4 updates
-
investigating Jan 22, 2026, 09:55 AM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Jan 22, 2026, 09:57 AM UTC
We are continuing to investigate this issue.
-
monitoring Jan 22, 2026, 10:59 AM UTC
Creating rooms in Video 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.
-
resolved Jan 22, 2026, 11:23 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 19, 2026, 07:09 AM UTC
- Resolved
- Jan 19, 2026, 08:00 AM UTC
- Duration
- 51m
Affected: Twilio Console
Timeline · 4 updates
-
investigating Jan 19, 2026, 07:01 AM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
-
investigating Jan 19, 2026, 07:06 AM UTC
We are continuing to investigate this issue.
-
monitoring Jan 19, 2026, 07:09 AM UTC
Twilio login and signup page is now operating normally. Twilio will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.
-
resolved Jan 19, 2026, 08:00 AM UTC
Twilio login and signup page issue has been resolved and is operating normally at this time.
Read the full incident report →
