Vonage: In-App Voice/Messaging Issue in Platform
Timeline of updates
- resolved
We can confirm this problem has been resolved, and all services have been restored. You may have experienced In-App Voice and In-App Messaging failures when trying to authenticate if your JWT did not include the RTC endpoint in the ACL. In-App Voice services were impacted from 2025-03-11 15:29 UTC until 16:07 UTC. Voice API, SIP Trunking, and In-App Voice/Messaging requests with a JWT that included the RTC endpoint in the ACL have not been impacted. Please let support@api.vonage.com know if you continue to experience problems with this.
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 2025-03-11 16:27 UTC, resolved after 51 min, 1 update(s).
- Title
- In-App Voice/Messaging Issue in Platform
- Vendor
- Vonage
- Date
- URL
- https://rewindex.com/company/vonage/incidents/3qdx6p2rwvt6
Vonage profileRecent Vonage incidentsAll outages on March 11, 2025Vonage in March 2025MarkdownJSON