Skip to content
Back to TwilioIncident Postmortem
Twilio logo

Twilio

Tracked by PulseWatch

Auto-drafted postmortem

Twilio outage on May 2 — 1d 7h disruption

May 2, 01:51 PM → May 3, 09:03 PM · 1d 7h · medium

Twilio experienced a service disruption starting on May 2, 2026, which was initially detected through user reports. The incident led to various service issues for users. The disruption was resolved on May 3, 2026.

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

Impact

The outage was detected through a significant increase in user reports, with a peak of 26 reports within a 15-minute period and a total of 732 reports during the incident. Users primarily reported issues categorized as 'Website down' (528 reports) and 'Slow / unresponsive' (204 reports). No specific top impacted regions were recorded during this time. The disruption affected users attempting to access or utilize Twilio services.

Top reported issues

  • Website down528
  • Slow / unresponsive204

Incident timeline

  1. May 2, 01:51 PM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 02:22 PM

    Status updated: major issue

  3. May 2, 02:28 PM

    Status updated: major issue

  4. May 2, 02:37 PM

    Status updated: major issue

  5. May 2, 02:42 PM

    Status updated: major issue

  6. May 2, 02:53 PM

    Status updated: major issue

  7. May 2, 02:58 PM

    Status updated: major issue

  8. May 2, 03:07 PM

    Status updated: major issue

  9. May 2, 03:12 PM

    Status updated: major issue

  10. May 2, 03:22 PM

    Status updated: major issue

  11. May 2, 03:27 PM

    Status updated: major issue

  12. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.3)

  13. May 3, 08:53 PM

    Status updated: possible issue

  14. May 3, 08:58 PM

    Status updated: possible issue

  15. May 3, 09:03 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 01:51 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