Skip to content
Back to TwilioIncident Postmortem
Twilio logo

Twilio

Tracked by PulseWatch

Auto-drafted postmortem

Twilio outage on May 1 — 1h 5m disruption

May 1, 12:42 PM → May 1, 01:47 PM · 1h 5m · high

On May 1, 2026, Twilio experienced a service disruption. This incident was detected through user reports indicating issues with the platform. The service disruption was resolved by 13:47 UTC on the same day.

Peak reports
10
in 15 min
Total reports
28
during the incident
Duration
1h 5m
tracked by PulseWatch

Impact

Users reported a high severity service disruption affecting Twilio. The incident was identified through 28 user reports, with a peak of 10 reports within a 15-minute period. The primary issues reported by users included website accessibility problems and API functionality issues. No specific regional impact was recorded during this event.

Top reported issues

  • Website down16
  • API issues12

Incident timeline

  1. May 1, 12:42 PM

    PulseWatch detected elevated report volume (high severity)

  2. May 1, 12:45 PM

    Peak of 8 reports in 15 minutes (baseline 4.0)

  3. May 1, 01:47 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. May 1, 12:42 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