Twilio: Lookup V2 Reassigned Number Latency Spike
Timeline of updates
- resolved
Twilio Lookup V2 Reassigned Number Latency Spike was degraded for 20 minutes between 22:55 and 23:40Pacific Time on 12/02/2024. During this period of time customers may have experienced a large increase in traffic where our provider started failing. 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 16:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Lookup V2 Reassigned Number Latency Spike
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/tslg7b4sv48j
Twilio profileRecent Twilio incidentsAll outages on December 10, 2024Twilio in December 2024MarkdownJSON