Skip to content
Back to TwilioIncident Postmortem
Twilio logo

Twilio

Tracked by PulseWatch

Auto-drafted postmortem

Twilio outage on May 2 — 1d 12h disruption

May 2, 09:14 AM → May 3, 10:03 PM · 1d 12h · medium

Twilio experienced a service disruption starting on May 2, 2026. This incident was detected through a significant increase in user reports. The service disruption was resolved on May 3, 2026.

Peak reports
26
in 15 min
Total reports
1,000
during the incident
Duration
1d 12h
tracked by PulseWatch

Impact

During the incident, PulseWatch recorded approximately 1000 user reports, with a peak of 26 reports within a 15-minute period. Users primarily reported issues categorized as 'Website down,' accounting for 612 reports, and 'Slow / unresponsive,' with 388 reports. No specific regional impact was recorded during this period. These reports indicate a broad impact on user access and service responsiveness.

Top reported issues

  • Website down612
  • Slow / unresponsive388

Incident timeline

  1. May 2, 09:14 AM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 09:42 AM

    Status updated: major issue

  3. May 2, 09:52 AM

    Status updated: major issue

  4. May 2, 09:57 AM

    Status updated: major issue

  5. May 2, 10:08 AM

    Status updated: major issue

  6. May 2, 10:13 AM

    Status updated: major issue

  7. May 2, 10:22 AM

    Status updated: major issue

  8. May 2, 10:27 AM

    Status updated: major issue

  9. May 2, 10:38 AM

    Status updated: major issue

  10. May 2, 10:43 AM

    Status updated: major issue

  11. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.3)

  12. May 3, 09:53 PM

    Status updated: possible issue

  13. May 3, 09:57 PM

    Status updated: possible issue

  14. May 3, 10:03 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 09:14 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