Twilio outage on May 2 — 1d 2h disruption
May 2, 05:21 PM → May 3, 08:18 PM · 1d 2h · medium
Twilio experienced a service disruption that was detected through user reports. The incident began on May 2, 2026, and was resolved on May 3, 2026.
Impact
Users reported issues with Twilio services over a period of 1 day and 2 hours. A total of 488 reports were received, with a peak of 26 reports in a 15-minute window. The most frequently reported issues included 'Website down' (452 reports) and 'Slow / unresponsive' (36 reports). No specific regional impact was recorded during this incident.
Top reported issues
- Website down452
- Slow / unresponsive36
Incident timeline
- May 2, 05:21 PM
PulseWatch detected elevated report volume (medium severity)
- May 3, 11:30 AM
Peak of 8 reports in 15 minutes (baseline 1.3)
- May 3, 01:58 PM
Status updated: possible issue
- May 3, 02:08 PM
Status updated: possible issue
- May 3, 02:12 PM
Status updated: possible issue
- May 3, 02:22 PM
Status updated: possible issue
- May 3, 02:27 PM
Status updated: possible issue
- May 3, 02:37 PM
Status updated: possible issue
- May 3, 02:43 PM
Status updated: possible issue
- May 3, 02:52 PM
Status updated: possible issue
- May 3, 02:57 PM
Status updated: possible issue
- May 3, 03:07 PM
Status updated: possible issue
- May 3, 03:13 PM
Status updated: possible issue
- May 3, 03:23 PM
Status updated: possible issue
- May 3, 03:28 PM
Status updated: possible issue
- May 3, 03:38 PM
Status updated: possible issue
- May 3, 03:42 PM
Status updated: possible issue
- May 3, 03:52 PM
Status updated: possible issue
- May 3, 03:57 PM
Status updated: possible issue
- May 3, 04:08 PM
Status updated: possible issue
- May 3, 04:13 PM
Status updated: possible issue
- May 3, 04:27 PM
Status updated: possible issue
- May 3, 04:37 PM
Status updated: possible issue
- May 3, 04:42 PM
Status updated: possible issue
- May 3, 04:52 PM
Status updated: possible issue
- May 3, 04:58 PM
Status updated: possible issue
- May 3, 05:07 PM
Status updated: possible issue
- May 3, 05:12 PM
Status updated: possible issue
- May 3, 05:23 PM
Status updated: possible issue
- May 3, 05:28 PM
Status updated: possible issue
- May 3, 05:38 PM
Status updated: possible issue
- May 3, 05:43 PM
Status updated: possible issue
- May 3, 05:53 PM
Status updated: possible issue
- May 3, 05:58 PM
Status updated: possible issue
- May 3, 06:08 PM
Status updated: possible issue
- May 3, 06:13 PM
Status updated: possible issue
- May 3, 06:23 PM
Status updated: possible issue
- May 3, 06:27 PM
Status updated: possible issue
- May 3, 06:37 PM
Status updated: possible issue
- May 3, 06:43 PM
Status updated: possible issue
- May 3, 06:52 PM
Status updated: possible issue
- May 3, 06:57 PM
Status updated: possible issue
- May 3, 07:07 PM
Status updated: possible issue
- May 3, 07:12 PM
Status updated: possible issue
- May 3, 07:22 PM
Status updated: possible issue
- May 3, 07:27 PM
Status updated: possible issue
- May 3, 07:37 PM
Status updated: possible issue
- May 3, 07:43 PM
Status updated: possible issue
- May 3, 07:53 PM
Status updated: possible issue
- May 3, 07:57 PM
Status updated: possible issue
- May 3, 08:07 PM
Status updated: possible issue
- May 3, 08:13 PM
Status updated: possible issue
- May 3, 08:18 PM
Report volume returned to baseline — incident resolved
Official updates
- May 2, 05:21 PM
Twilio status page acknowledged the incident.
View official source