Twilio: Subset of Inbound Calls With Invalid ST/SH Passports Being Rejected
Timeline of updates
- resolved
From 2025-11-25 19:25 UTC until 2025-12-11 00:23 UTC, a small subset of inbound calls from carriers sending invalid STIR/SHAKEN PASSporTs were erroneously rejected. These calls should have been accepted and completed with a 32021 (warning), but due to a software bug they were instead classified as 32020 (error) and blocked. The issue has been mitigated and inbound calls with invalid PASSporTs are now processed normally.
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-12-11 20:49 UTC, resolved after 0 min, 1 update(s).
- Title
- Subset of Inbound Calls With Invalid ST/SH Passports Being Rejected
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/3r3m07jjdmn0
Twilio profileRecent Twilio incidentsAll outages on December 11, 2025Twilio in December 2025MarkdownJSON