Skip to content
Back to TwilioIncident Postmortem
Twilio logo

Twilio

Tracked by PulseWatch

Auto-drafted postmortem

Twilio outage on May 2-3 — 1d 4h disruption

May 2, 04:14 PM → May 3, 08:33 PM · 1d 4h · medium

On May 2, 2026, Twilio experienced a service disruption. This incident was detected via user reports and lasted approximately 1 day and 4 hours before being resolved on May 3, 2026.

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

Impact

Users reported issues with Twilio's service, primarily experiencing the website being down or slow/unresponsive. A total of 570 reports were received during the incident, with a peak of 26 reports in a 15-minute period. The most common issue reported was 'Website down' (480 reports), followed by 'Slow / unresponsive' (90 reports). No specific regional impact was recorded.

Top reported issues

  • Website down480
  • Slow / unresponsive90

Incident timeline

  1. May 2, 04:14 PM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 04:43 PM

    Status updated: major issue

  3. May 2, 04:53 PM

    Status updated: major issue

  4. May 2, 04:58 PM

    Status updated: major issue

  5. May 2, 05:07 PM

    Status updated: major issue

  6. May 2, 05:13 PM

    Status updated: major issue

  7. May 2, 05:23 PM

    Status updated: major issue

  8. May 2, 05:28 PM

    Status updated: major issue

  9. May 2, 05:37 PM

    Status updated: major issue

  10. May 2, 05:43 PM

    Status updated: major issue

  11. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.3)

  12. May 3, 08:23 PM

    Status updated: possible issue

  13. May 3, 08:27 PM

    Status updated: possible issue

  14. May 3, 08:33 PM

    Report volume returned to baseline — incident resolved

Official updates

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