Twilio: Verify experienced a degradation on the Verification creation endpoint given an increased latency.
Timeline of updates
- resolved
On March 13th, between 18:19:11 UTC and 18:19:39 UTC (28 seconds), Verify experienced a degradation on the Verification creation endpoint given an increased latency. Customer Impact: 343 errors (i.e., 503) were returned to customers. 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 2024-03-13 19:13 UTC, resolved after 0 min, 1 update(s).
- Title
- Verify experienced a degradation on the Verification creation endpoint given an increased latency.
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/lq5r18d6vrr5
Twilio profileRecent Twilio incidentsAll outages on March 13, 2024Twilio in March 2024MarkdownJSON