Twilio: Incorrect Number Type Returned From LookUp Product
Timeline of updates
- resolved
Carrier Lookup was degraded for 5 days between Oct 15 12:58:28 UTC and Oct 20 07:12:21 UTC. During this period, customers may have experienced incorrect values for the number type in carrier lookup responses for approximately 5% of the requests. 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 2021-10-20 06:56 UTC, resolved after 29 min, 1 update(s).
- Title
- Incorrect Number Type Returned From LookUp Product
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/py97r16kmmqg
Twilio profileRecent Twilio incidentsAll outages on October 20, 2021Twilio in October 2021MarkdownJSON