Skip to content
Back to TwilioIncident Postmortem
Twilio logo

Twilio

Tracked by PulseWatch

Auto-drafted postmortem

Twilio outage on May 2 — 1d 10h disruption

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

On May 2, 2026, an outage affecting Twilio services was detected through user reports. The incident began at approximately 11:29 UTC and was resolved on May 3, 2026, at approximately 21:34 UTC.

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

Impact

During the incident, users reported a medium severity impact, with a total of 898 reports received. The most frequently reported issues included 'Website down,' accounting for 580 reports, and 'Slow / unresponsive' services, with 318 reports. No specific regional concentrations of impact were recorded during this period.

Top reported issues

  • Website down580
  • Slow / unresponsive318

Incident timeline

  1. May 2, 11:29 AM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 12:07 PM

    Status updated: major issue

  3. May 2, 12:12 PM

    Status updated: major issue

  4. May 2, 12:22 PM

    Status updated: major issue

  5. May 2, 12:27 PM

    Status updated: major issue

  6. May 2, 12:38 PM

    Status updated: major issue

  7. May 2, 12:42 PM

    Status updated: major issue

  8. May 2, 12:52 PM

    Status updated: major issue

  9. May 2, 12:57 PM

    Status updated: major issue

  10. May 2, 01:07 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:23 PM

    Status updated: possible issue

  13. May 3, 09:27 PM

    Status updated: possible issue

  14. May 3, 09:33 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 11:29 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