Skip to content
Back to TwilioIncident Postmortem
Twilio logo

Twilio

Tracked by PulseWatch

Auto-drafted postmortem

Twilio outage on May 2 — 1d 15h disruption

May 2, 06:51 AM → May 3, 10:48 PM · 1d 15h · medium

On May 2, 2026, Twilio experienced a service disruption, which was detected through user reports. The incident lasted for 1 day and 15 hours. Service was fully restored on May 3, 2026.

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

Impact

During the incident, PulseWatch recorded approximately 1000 user reports. The most frequently reported issue types were 'Website down,' accounting for 624 reports, and 'Slow / unresponsive,' with 376 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 down624
  • Slow / unresponsive376

Incident timeline

  1. May 2, 06:51 AM

    PulseWatch detected elevated report volume (medium severity)

  2. May 2, 07:23 AM

    Status updated: major issue

  3. May 2, 07:27 AM

    Status updated: major issue

  4. May 2, 07:37 AM

    Status updated: major issue

  5. May 2, 07:42 AM

    Status updated: major issue

  6. May 2, 07:52 AM

    Status updated: major issue

  7. May 2, 07:57 AM

    Status updated: major issue

  8. May 2, 08:07 AM

    Status updated: major issue

  9. May 2, 08:12 AM

    Status updated: major issue

  10. May 2, 08:22 AM

    Status updated: major issue

  11. May 2, 08:27 AM

    Status updated: major issue

  12. May 3, 11:30 AM

    Peak of 8 reports in 15 minutes (baseline 1.3)

  13. May 3, 10:23 PM

    Status updated: possible issue

  14. May 3, 10:28 PM

    Status updated: major issue

  15. May 3, 10:38 PM

    Status updated: possible issue

  16. May 3, 10:43 PM

    Status updated: possible issue

  17. May 3, 10:48 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 2, 06:51 AM

    Twilio status page acknowledged the incident.

    View official source
  2. May 3, 10:48 PM

    Root cause: Transient performance degradation with flapping behavior.

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