Bandwidth: Inbound Calling - Caller ID Lookup (CNAM) API
Affected components: Inbound Calling - Caller ID Lookup - CNAM
Timeline of updates
- investigating
Bandwidth teams are investigating slowness with the Inbound Calling - Caller ID Lookup (CNAM) API.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
- Major incident: Inbound Calling - Caller ID Lookup (CNAM) API
- Incident updated: Inbound Calling - Caller ID Lookup (CNAM) API
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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
cc0ae16f875f9727…Version 2 captured
In the 2026-11-18 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
569a6a24a8a8cf7b…
Impact, status and times are the vendor’s own, as last archived. View on status.bandwidth.com (opens in new tab).
Cite this
Status incident (vendor impact label: major) posted by Bandwidth, started 2026-11-18 21:11 UTC, resolved after 39 min, 2 update(s); edited after publishing.
- Title
- Inbound Calling - Caller ID Lookup (CNAM) API
- Vendor
- Bandwidth
- Date
- URL
- https://rewindex.com/company/bandwidth/incidents/m85g6h7k1xm1
Bandwidth profileRecent Bandwidth incidentsAll outages on November 18, 2026Bandwidth in November 2026MarkdownJSON