Skip to content
Back to TwilioIncident Postmortem
Twilio logo

Twilio

Tracked by PulseWatch

Auto-drafted postmortem

Twilio outage on May 2 — 1 day, 11 hour disruption

May 2, 10:21 AM → May 3, 09:48 PM · 1d 11h · medium

On May 2, 2026, a service disruption affecting Twilio was detected through user reports. The incident began at 10:21 UTC and was fully resolved on May 3, 2026, at 21:48 UTC.

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

Impact

The service disruption led to a total of 972 user reports over its duration, with a peak of 26 reports within a 15-minute window. Users primarily reported issues such as the Twilio website being down, which accounted for 600 reports, and slow or unresponsive service, noted in 372 reports. No specific regional impact was identified or recorded during this incident.

Top reported issues

  • Website down600
  • Slow / unresponsive372

Incident timeline

  1. May 2, 10:21 AM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 10:53 AM

    Status updated: major issue

  3. May 2, 10:57 AM

    Status updated: major issue

  4. May 2, 11:07 AM

    Status updated: major issue

  5. May 2, 11:13 AM

    Status updated: major issue

  6. May 2, 11:23 AM

    Status updated: major issue

  7. May 2, 11:28 AM

    Status updated: major issue

  8. May 2, 11:37 AM

    Status updated: major issue

  9. May 2, 11:43 AM

    Status updated: major issue

  10. May 2, 11:52 AM

    Status updated: major issue

  11. May 2, 11:57 AM

    Status updated: major issue

  12. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.3)

  13. May 3, 09:38 PM

    Status updated: possible issue

  14. May 3, 09:43 PM

    Status updated: possible issue

  15. May 3, 09:48 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 10:21 AM

    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