rewindex

CompaniesTwilioIncidents

Twilio: Our Engineers are Investigating an Issue with 5XXs from Twilio Public API to Customer via Rest Proxy

No impact listedStatus: resolvedStarted Resolved (4 min)1 updatestatus.twilio.com (opens in new tab)

Timeline of updates

  1. resolved

    The Twilio Programmable Messaging API was partially degraded for 1 minute on Nov 18th, 2025 between 12:35:00 PST and 12:36:00 PST. During this period of time, customers sending a message may have received elevated volumes of 5xx's in API responses. This issue has now been resolved.

From Twilio’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Twilio, started 2025-11-18 21:00 UTC, resolved after 4 min, 1 update(s).

Title
Our Engineers are Investigating an Issue with 5XXs from Twilio Public API to Customer via Rest Proxy
Vendor
Twilio
Date
URL
https://rewindex.com/company/twilio/incidents/18ny11yr1xv8

Twilio profileRecent Twilio incidentsAll outages on November 18, 2025Twilio in November 2025MarkdownJSON