Service Issue in Platform

Incident Report for Vonage API Status

Resolved

We have implemented a fix for this issue and all capabilities on accounts have been added back.

We will continue to monitor services during the next few hours and post updates should anything change.
Posted Mar 05, 2025 - 17:54 UTC

Update

We continue to work on a fix for this issue and will provide an update as soon as more information becomes available.
Incident start time(UTC): 5th March 10:20 UTC

Please see this article - https://api.support.vonage.com/hc/en-us/articles/6749696044828-Vonage-API-Support-Incident-Handling - for an explanation of our approach to publishing incidents.
Posted Mar 05, 2025 - 16:09 UTC

Update

We continue to work on a fix for this issue and will provide an update as soon as more information becomes available.

Please see this article - https://api.support.vonage.com/hc/en-us/articles/6749696044828-Vonage-API-Support-Incident-Handling - for an explanation of our approach to publishing incidents.
Posted Mar 05, 2025 - 14:46 UTC

Identified

We have identified the root cause of this issue, and we're working on getting the issue fixed.

At this time, We have identified an issue around a few capabilities being missing temporarily and have added them back. More details will be shared within 1 hour.

Please see this article - https://api.support.vonage.com/hc/en-us/articles/6749696044828-Vonage-API-Support-Incident-Handling - for an explanation of our approach to publishing incidents.
Posted Mar 05, 2025 - 13:47 UTC

Investigating

Our monitoring system has alerted us to a potential service issue with our platform.

Although it is not yet certain whether there is any customer impact, we are alerting customers immediately while our engineering teams investigate. We aim to provide an update on our investigation within 1 hour.

Please see this article - https://api.support.vonage.com/hc/en-us/articles/6749696044828-Vonage-API-Support-Incident-Handling - for an explanation of our approach to publishing incidents.
Posted Mar 05, 2025 - 12:44 UTC
This incident affected: Multiple Services Affected (Multiple Services Affected).