Skip to content
Back to TwilioIncident Postmortem
Twilio logo

Twilio

Tracked by PulseWatch

Auto-drafted postmortem

Twilio outage on May 4 — 1h 27m disruption

May 4, 03:36 AM → May 4, 05:03 AM · 1h 27m · medium

On May 4, 2026, Twilio experienced a service disruption, which was detected through user reports. The incident began at 03:36 UTC and was resolved by 05:04 UTC.

Peak reports
8
in 15 min
Total reports
40
during the incident
Duration
1h 27m
tracked by PulseWatch

Impact

Users reported issues with Twilio's services, leading to a medium-severity incident. A total of 40 reports were received during the disruption, with a peak of 8 reports within a 15-minute period. The most frequently reported issue types included 'Website down' and 'API issues'. No specific regional impact was recorded during this time.

Top reported issues

  • Website down24
  • API issues16

Incident timeline

  1. May 4, 03:36 AM

    PulseWatch detected elevated report volume (medium severity)

  2. May 4, 03:45 AM

    Peak of 8 reports in 15 minutes (baseline 4.0)

  3. May 4, 03:53 AM

    Status updated: major issue

  4. May 4, 03:57 AM

    Status updated: major issue

  5. May 4, 04:02 AM

    Status updated: possible issue

  6. May 4, 04:08 AM

    Status updated: major issue

  7. May 4, 04:12 AM

    Status updated: major issue

  8. May 4, 04:17 AM

    Status updated: possible issue

  9. May 4, 04:23 AM

    Status updated: major issue

  10. May 4, 04:27 AM

    Status updated: major issue

  11. May 4, 04:32 AM

    Status updated: possible issue

  12. May 4, 04:38 AM

    Status updated: major issue

  13. May 4, 04:42 AM

    Status updated: major issue

  14. May 4, 04:53 AM

    Status updated: possible issue

  15. May 4, 04:57 AM

    Status updated: possible issue

  16. May 4, 05:03 AM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 4, 03:36 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