Vonage: Issues Impacting WhatsApp API
Affected components: Messages APISMS & Messages - Messages API
Timeline of updates
- investigatingEdited
We are working to resolve the issue that is impacting Vonage Messages API – WhatsApp channel. Messages API customers may not receive delivery callbacks for the WhatApp channel. Outbound messaging is unaffected. Inbound WhatsApp messages are affected. We'll continue to provide further updates here within 60 minutes. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- investigating
We continue to work to resolve the issue that may be impacting your access to WhatsApp messaging. We'll continue to provide further updates here within 60 minutes. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- investigating
We continue to work to resolve the issue that may be impacting Vonage Messages API – WhatsApp channel. We'll continue to provide further updates here within 30 minutes. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- identified
We have identified the issue that may be impacting your ability to access WhatsApp, and we are working with our partner on a resolution. We will continue to provide further updates within 30 minutes and once full service is restored. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- identified
We have identified the issue that is affecting inbound WhatsApp messages and webhooks, and we are working with our partner on a resolution. We will continue to provide further updates within 30 minutes and once full service is restored. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- identified
We have identified the issue that is affecting inbound WhatsApp messages and webhooks, and we are working with our partner on a resolution. We will continue to provide further updates within 30 minutes and once full service is restored. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- identified
We have identified the issue that is affecting inbound WhatsApp messages and webhooks, and we are working with our partner on a resolution. We will continue to provide further updates within 30 minutes and once full service is restored. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
- monitoring
Vonage services show signs of recovery following today's interruption in inbound WhatsApp messages and webhooks. We'll continue to provide further updates here within 30 minutes and once full service is restored. Thank you for your patience and understanding as we work to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com.
- resolved
Vonage services have been fully restored following today's service interruption affecting inbound WhatsApp messages and webhooks, which began at 2026-11-13 18:31:00 UTC. Full resolution has been confirmed effective 2026-11-13 22:00:00 UTC. Please note inbound messages sent and callbacks not received during the incident are lost. Impacted customers will receive a formal RFO. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com.
Changes Rewindex caught on this incident
- Incident silently edited: Issues Impacting WhatsApp API
- Incident silently edited: Issues Impacting WhatsApp API
- Incident updated: Issues Impacting WhatsApp API
- Incident updated: Issues Impacting WhatsApp API
- Incident updated: Issues Impacting WhatsApp API
- Incident updated: Issues Impacting WhatsApp API
- Incident updated: Issues Impacting WhatsApp API
- Incident updated: Issues Impacting WhatsApp API
- Incident updated: Issues Impacting WhatsApp API
- Incident updated: Issues Impacting WhatsApp 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-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
7e0a76767600dab4…Version 2 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
86e87cd22cb22add…Version 3 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
dc210655e8d89d97…Version 4 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
b4562a2094aad8f9…Version 5 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
eb00dc3c53931a72…Version 6 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
15a4b4bb8b41dc33…Version 7 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
573f263afce2eb21…Version 8 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
54d347ef56b08003…Version 9 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
1d33a79769c50a05…Version 10 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
10ac513e9d25f704…Version 11 captured
In the 2026-11-13 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
06326685dbc1884d…
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-11-13 18:30 UTC, resolved after 4.0 h, 9 update(s); edited after publishing.
- Title
- Issues Impacting WhatsApp API
- Vendor
- Vonage
- Date
- URL
- https://rewindex.com/company/vonage/incidents/8bxgqbfy0fb0
Vonage profileRecent Vonage incidentsAll outages on November 13, 2026Vonage in November 2026MarkdownJSON