Vonage: Disruption - Number Deactivation Feed Unavailability
Timeline of updates
- resolved
We have confirmed that the third-party disruption affecting the Number Deactivation Feed has been resolved. Services have been restored and are operating normally. We have identified a limited number of customers who may have been impacted during this disruption. Our team will be reaching out directly to those specific customers to provide further details and any necessary remediation. If you believe you were affected and have not heard from us, please contact us at api.support.vonage.com. Thank you for your patience and understanding.
From Vonage’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 vonageapi.statuspage.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Vonage, started 2026-07-14 15:11 UTC, resolved after 1.7 h, 1 update(s).
- Title
- Disruption - Number Deactivation Feed Unavailability
- Vendor
- Vonage
- Date
- URL
- https://rewindex.com/company/vonage/incidents/zr7d9y8k3n98
Vonage profileRecent Vonage incidentsAll outages on July 14, 2026Vonage in July 2026MarkdownJSON