Twilio: Verify experienced an increase in HTTP 500 and 503 codes and latencies on the Verifications API.
Timeline of updates
- resolved
Twilio Verify was degraded for 28 minutes between 21:50:49 and 22:18:16 UTC Pacific Time on 09/05/2025. During this period of time customers may have experienced an increase in HTTP 500 and 503 codes and latencies on the Verifications API. The 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-09-06 04:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Verify experienced an increase in HTTP 500 and 503 codes and latencies on the Verifications API.
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/frsh01x1ycxr
Twilio profileRecent Twilio incidentsAll outages on September 6, 2025Twilio in September 2025MarkdownJSON