Twilio: Elevated HTTP 500 and 503 Status Codes on the Create, Check, Update, and Fetch Verifications Endpoints of the Verify API
Timeline of updates
- resolved
Twilio Verify was degraded for 29 minutes between 16:05 and 16:34 Pacific Time on 02/28/2025. During this period of time customers may have experienced elevated HTTP 500 and 503 status codes on the create, check, update, and fetch Verifications endpoints of the Twilio Verify 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: minor) posted by Twilio, started 2025-03-01 00:55 UTC, resolved after 18 min, 1 update(s).
- Title
- Elevated HTTP 500 and 503 Status Codes on the Create, Check, Update, and Fetch Verifications Endpoints of the Verify API
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/dxn9ppybhz7x
Twilio profileRecent Twilio incidentsAll outages on March 1, 2025Twilio in March 2025MarkdownJSON