Twilio: Lookup V2 reassigned number service affected
Timeline of updates
- resolved
Twilio Lookup product was degraded for 1 minute between 14:04 and 14:05 Pacific Time on 08/27/2025. During this period of time, Lookup returned 38 HTTP 503 errors in a minute for all reassigned_number 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 2025-08-27 17:12 UTC, resolved after 0 min, 1 update(s).
- Title
- Lookup V2 reassigned number service affected
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/k64hws8ts07n
Twilio profileRecent Twilio incidentsAll outages on August 27, 2025Twilio in August 2025MarkdownJSON