Incorrect Data on Deactivations API for 2025-03-05


Incident resolved in 23m20s

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.

1741916808

Update

Our engineers are currently investigating the customer impact of a retroactive issue with Intermittent SMS/MMS Deliverability Issues. We will follow up and provide customer impact details within 2 hours.

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.

1741915463

Update

Our engineers are currently investigating the customer impact of a retroactive issue with Intermittent SMS/MMS Deliverability Issues to AT&T. We will follow up and provide customer impact details within 2 hours.

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.

1741915408