Skip to content
Back to TwilioIncident Postmortem
Twilio logo

Twilio

Tracked by PulseWatch

Auto-drafted postmortem

Twilio outage on May 2 — 1d 17h disruption

May 2, 05:44 AM → May 3, 11:03 PM · 1d 17h · medium

A service disruption affecting Twilio was detected by user reports starting on May 2, 2026. The incident, which was correlated across official vendor signals, was resolved on May 3, 2026.

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

Impact

Users reported a medium-severity service disruption affecting Twilio, with a total of 1000 reports received during the incident. The most frequently reported issues included "Website down" (628 reports) and "Slow / unresponsive" service (372 reports). At its peak, 26 reports were received within a 15-minute period. No specific top impacted regions were recorded during this event.

Top reported issues

  • Website down628
  • Slow / unresponsive372

Incident timeline

  1. May 2, 05:44 AM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 06:12 AM

    Status updated: major issue

  3. May 2, 06:23 AM

    Status updated: major issue

  4. May 2, 06:28 AM

    Status updated: major issue

  5. May 2, 06:38 AM

    Status updated: major issue

  6. May 2, 06:43 AM

    Status updated: major issue

  7. May 2, 06:53 AM

    Status updated: major issue

  8. May 2, 06:58 AM

    Status updated: major issue

  9. May 2, 07:07 AM

    Status updated: major issue

  10. May 2, 07:12 AM

    Status updated: major issue

  11. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.3)

  12. May 3, 10:53 PM

    Status updated: possible issue

  13. May 3, 10:57 PM

    Status updated: possible issue

  14. May 3, 11:03 PM

    Report volume returned to baseline — incident resolved

Official updates

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