Skip to content
Back to TwilioIncident Postmortem
Twilio logo

Twilio

Tracked by PulseWatch

Auto-drafted postmortem

Twilio outage on May 2-3 — 1d 5h disruption

May 2, 02:59 PM → May 3, 08:48 PM · 1d 5h · medium

On May 2, 2026, Twilio experienced a service disruption that affected users for over a day. The incident was detected through user reports and subsequently correlated with official vendor signals. Service was fully restored on May 3, 2026.

Peak reports
26
in 15 min
Total reports
654
during the incident
Duration
1d 5h
tracked by PulseWatch

Impact

Users reported issues primarily categorized as 'Website down (504)' and 'Slow / unresponsive' during the incident. PulseWatch detected a peak of 26 reports within a 15-minute period, with a total of 654 user reports received over the duration of the disruption. No specific top impacted regions were recorded for this event. This outage was initially detected via user reports.

Top reported issues

  • Website down504
  • Slow / unresponsive150

Incident timeline

  1. May 2, 02:59 PM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 03:38 PM

    Status updated: major issue

  3. May 2, 03:42 PM

    Status updated: major issue

  4. May 2, 03:52 PM

    Status updated: major issue

  5. May 2, 03:57 PM

    Status updated: major issue

  6. May 2, 04:08 PM

    Status updated: major issue

  7. May 2, 04:12 PM

    Status updated: major issue

  8. May 2, 04:22 PM

    Status updated: major issue

  9. May 2, 04:27 PM

    Status updated: major issue

  10. May 2, 04:38 PM

    Status updated: major issue

  11. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.3)

  12. May 3, 08:38 PM

    Status updated: possible issue

  13. May 3, 08:43 PM

    Status updated: possible issue

  14. May 3, 08:48 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 02:59 PM

    Twilio status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash