Twilio: Degraded CNAM Lookup in Lookup API, Elastic SIP Trunking, and IncomingPhoneNumber Resource
Timeline of updates
- resolved
CNAM lookups were degraded for 18 minutes between 20:32 and 20:50 Pacific Time on 10/12/2021. During this period, customers may have experienced null responses if using the Lookup API to query Caller Name, or if CNAM Lookup was enabled on their Elastic SIP Trunk, or if voice_caller_id_lookup was enabled on their IncomingPhoneNumber resource. 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-13 18:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Degraded CNAM Lookup in Lookup API, Elastic SIP Trunking, and IncomingPhoneNumber Resource
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/m0q65y206q9m
Twilio profileRecent Twilio incidentsAll outages on October 13, 2021Twilio in October 2021MarkdownJSON