Twilio: Inaccurate Portability API Responses
Timeline of updates
- resolved
Twilio Portability API Responses was degraded between between 10:00 and 6:30 Pacific Time on 12/04/2024. During this period of time customers may have experienced incorrect portability responses indicating that a number was not portable to Twilio. 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-12-10 19:55 UTC, resolved after 3.2 h, 1 update(s).
- Title
- Inaccurate Portability API Responses
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/wvt42c8khwzy
Twilio profileRecent Twilio incidentsAll outages on December 10, 2024Twilio in December 2024MarkdownJSON