Skip to content
Back to TwilioIncident Postmortem
Twilio logo

Twilio

Tracked by PulseWatch

Auto-drafted postmortem

Twilio outage on May 2 — 1d 8h disruption

May 2, 12:44 PM → May 3, 09:18 PM · 1d 8h · medium

Twilio experienced a service disruption that was initially detected through user reports. The incident began on May 2, 2026, and was resolved on May 3, 2026.

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

Impact

The disruption was widely reported by users, with a total of 810 reports received during the incident, peaking at 26 reports within a 15-minute period. The most frequently reported issues included 'Website down,' accounting for 552 reports, and 'Slow / unresponsive' service, with 258 reports. No specific regional impact was recorded during this time. This incident was detected by PulseWatch, a third-party outage monitoring platform, and correlated with official vendor signals.

Top reported issues

  • Website down552
  • Slow / unresponsive258

Incident timeline

  1. May 2, 12:44 PM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 01:12 PM

    Status updated: major issue

  3. May 2, 01:22 PM

    Status updated: major issue

  4. May 2, 01:27 PM

    Status updated: major issue

  5. May 2, 01:37 PM

    Status updated: major issue

  6. May 2, 01:43 PM

    Status updated: major issue

  7. May 2, 01:52 PM

    Status updated: major issue

  8. May 2, 01:58 PM

    Status updated: major issue

  9. May 2, 02:07 PM

    Status updated: major issue

  10. May 2, 02:13 PM

    Status updated: major issue

  11. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.3)

  12. May 3, 09:08 PM

    Status updated: possible issue

  13. May 3, 09:12 PM

    Status updated: possible issue

  14. May 3, 09:18 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 12:44 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