Twilio: Double Encoded Numbers Issue for Lookup V1 API
Timeline of updates
- resolved
Twilio Lookup V1 API was degraded from 2024-01-11 19:41:59 UTC and 2024-01-15 16:42:08. About 0.13% of the traffic experienced anomalous responses. After investigating it was determined that the API was not performing an extra url-decoding step on top of the url-decoding performed in the downstream. This resulted in Lookups V1 not accepting 4.97% of the requests that were url-encoded multiple times. This incident affected 4.97% of the requests that included phone numbers that were url-encoded more than once and 0.13% of the total traffic. 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-02-05 20:58 UTC, resolved after 0 min, 1 update(s).
- Title
- Double Encoded Numbers Issue for Lookup V1 API
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/mllqnfnbgblf
Twilio profileRecent Twilio incidentsAll outages on February 5, 2024Twilio in February 2024MarkdownJSON