Twilio: Incorrect Data on Deactivations API for 2025-03-05
Timeline of updates
- resolved
Twilio has identified a large number of incorrect entries in the Deactivation API for March 5th, 2025. We are working with the carrier to identify the corrected list. To avoid further customer impact, we have removed the incorrect file until we can replace it with a corrected one. When querying 2025-03-05 on the Deactivations API, you will receive a 20404 error response.
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-14 01:23 UTC, resolved after 23 min, 1 update(s).
- Title
- Incorrect Data on Deactivations API for 2025-03-05
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/5mjvwv4pjx6j
Twilio profileRecent Twilio incidentsAll outages on March 14, 2025Twilio in March 2025MarkdownJSON