Vonage API Status

Resolved: Some servers were in an unstable state in the US-West region from Thursday, 8th May 04:54 UTC to Thursday, 8th May 04:59 UTC. Some customers may have experienced API failures for the following services during this period if they run across those servers,

Session Archiving, Session Connection, Video Broadcast, and Video Experience Composer (Standard and Enterprise)

The faulty instances were detected and removed from rotation. All services have been restored. Please let [email protected] know if you continue to experience problems with this.

Resolved: Some servers were in an unstable state in the US-West region from Thursday, 8th May 04:54 UTC to Thursday, 8th May 04:59 UTC. Some customers may have experienced API failures for the following services during this period if they run across those servers,

Session Archiving, Session Connection, Video Broadcast, and Video Experience Composer (Standard and Enterprise)

The faulty instances were detected and removed from rotation. All services have been restored. Please let [email protected] know if you continue to experience problems with this.

Resolved: Google has fixed the Chrome bug in version 137 and backported it to 136, which is currently rolling out. Users on older versions may still experience issues until the update reaches them.

Our documentation has been updated with guidance. If you need further assistance, please contact [email protected].

Monitoring: Google has confirmed that a fix for the issue affecting Chrome M136 on Windows, where the browser API intermittently responds slowly when returning audio device information, has been implemented.

The fix is included in Chrome version 137.0.7150.0 and has also been merged into version 136. This means it will be available in an upcoming stable respin of Chrome 136, expected to be released within the next few days.

In the meantime, if you continue to experience this issue, please roll-back to M135, or use an alternate browsers.

We will continue to monitor the rollout and provide further updates as needed. If you require assistance, please contact our support team.

Monitoring: Voice Client sdks are affected too, @vonage/client-sdk and nexmo-client are affected on the same versions of Chrome

Monitoring: We are aware of an issue affecting Google Chrome version M136 on Windows, as referenced below:

https://issues.chromium.org/issues/414842421 https://vcc.statuspage.io/incidents/5yyl528vk1jz

This issue causes the browser API to intermittently respond very slowly when returning audio device information through getUserMedia. We are monitoring the situation closely. If you are experiencing this issue, please use one of the following options:

1. Roll back to Chrome version 135 and pin it to prevent automatic updates.
2. Use an alternate browser, such as Firefox.

If you continue to experience problems or need assistance with a workaround, please contact our support team.

Thank you for your understanding and cooperation.

Resolved: Google has fixed the Chrome bug in version 137 and backported it to 136, which is currently rolling out. Users on older versions may still experience issues until the update reaches them.

Our documentation has been updated with guidance. If you need further assistance, please contact [email protected].

Monitoring: Google has confirmed that a fix for the issue affecting Chrome M136 on Windows, where the browser API intermittently responds slowly when returning audio device information, has been implemented.

The fix is included in Chrome version 137.0.7150.0 and has also been merged into version 136. This means it will be available in an upcoming stable respin of Chrome 136, expected to be released within the next few days.

In the meantime, if you continue to experience this issue, please roll-back to M135, or use an alternate browsers.

We will continue to monitor the rollout and provide further updates as needed. If you require assistance, please contact our support team.

Monitoring: Voice Client sdks are affected too, @vonage/client-sdk and nexmo-client are affected on the same versions of Chrome

Monitoring: We are aware of an issue affecting Google Chrome version M136 on Windows, as referenced below:

https://issues.chromium.org/issues/414842421 https://vcc.statuspage.io/incidents/5yyl528vk1jz

This issue causes the browser API to intermittently respond very slowly when returning audio device information through getUserMedia. We are monitoring the situation closely. If you are experiencing this issue, please use one of the following options:

1. Roll back to Chrome version 135 and pin it to prevent automatic updates.
2. Use an alternate browser, such as Firefox.

If you continue to experience problems or need assistance with a workaround, please contact our support team.

Thank you for your understanding and cooperation.

Resolved: We noticed issues with Live Captions in Video API sessions starting at 21:13 UTC in US-EAST-1 servers. The issue was resolved at 21:15 UTC. We will continue to monitor the service during the next few hours and post updates should anything change.

Resolved: Google has fixed the Chrome bug in version 137 and backported it to 136, which is currently rolling out. Users on older versions may still experience issues until the update reaches them.

Our documentation has been updated with guidance. If you need further assistance, please contact [email protected].

Monitoring: Google has confirmed that a fix for the issue affecting Chrome M136 on Windows, where the browser API intermittently responds slowly when returning audio device information, has been implemented.

The fix is included in Chrome version 137.0.7150.0 and has also been merged into version 136. This means it will be available in an upcoming stable respin of Chrome 136, expected to be released within the next few days.

In the meantime, if you continue to experience this issue, please roll-back to M135, or use an alternate browsers.

We will continue to monitor the rollout and provide further updates as needed. If you require assistance, please contact our support team.

Monitoring: Voice Client sdks are affected too, @vonage/client-sdk and nexmo-client are affected on the same versions of Chrome

Monitoring: We are aware of an issue affecting Google Chrome version M136 on Windows, as referenced below:

https://issues.chromium.org/issues/414842421 https://vcc.statuspage.io/incidents/5yyl528vk1jz

This issue causes the browser API to intermittently respond very slowly when returning audio device information through getUserMedia. We are monitoring the situation closely. If you are experiencing this issue, please use one of the following options:

1. Roll back to Chrome version 135 and pin it to prevent automatic updates.
2. Use an alternate browser, such as Firefox.

If you continue to experience problems or need assistance with a workaround, please contact our support team.

Thank you for your understanding and cooperation.

Resolved: We can confirm this problem has been resolved, and all services have been restored.

The following services were impacted from [06-05-2025 20:42] UTC until [07-05-2025 09:31] UTC.

Voice API In-App Voice Programmable SIP

Customers may have experienced call drops for both Outbound and Inbound calls using the Voice API during the incident.

Please let [email protected] know if you continue to experience problems with this.

Monitoring: We have implemented a fix for this issue.

Customers may have experienced call drops for both Outbound and Inbound calls using the Voice API during the incident.

The following services were impacted from [06-05-2025 20:42] UTC until [07-05-2025 09:31] UTC. Voice API In-App Voice Programmable SIP

We will continue to monitor services during the next few hours and post updates should anything change.

Identified: We have identified the problem. Issues have been mitigated to prevent further instances of call problems. We are doing testing to confirm what further corrections need to take place. We will update soon once we have a final solution in place. Please reach out to support if there are ongoing voice issues you need to report.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

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

Although it is not yet certain whether there is any customer impact, we are alerting customers immediately while our engineering teams investigate.

If there is a customer impact, it is likely to be affecting the following products: Vocie API

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.

Resolved: Google has fixed the Chrome bug in version 137 and backported it to 136, which is currently rolling out. Users on older versions may still experience issues until the update reaches them.

Our documentation has been updated with guidance. If you need further assistance, please contact [email protected].

Monitoring: Google has confirmed that a fix for the issue affecting Chrome M136 on Windows, where the browser API intermittently responds slowly when returning audio device information, has been implemented.

The fix is included in Chrome version 137.0.7150.0 and has also been merged into version 136. This means it will be available in an upcoming stable respin of Chrome 136, expected to be released within the next few days.

In the meantime, if you continue to experience this issue, please roll-back to M135, or use an alternate browsers.

We will continue to monitor the rollout and provide further updates as needed. If you require assistance, please contact our support team.

Monitoring: Voice Client sdks are affected too, @vonage/client-sdk and nexmo-client are affected on the same versions of Chrome

Monitoring: We are aware of an issue affecting Google Chrome version M136 on Windows, as referenced below:

https://issues.chromium.org/issues/414842421 https://vcc.statuspage.io/incidents/5yyl528vk1jz

This issue causes the browser API to intermittently respond very slowly when returning audio device information through getUserMedia. We are monitoring the situation closely. If you are experiencing this issue, please use one of the following options:

1. Roll back to Chrome version 135 and pin it to prevent automatic updates.
2. Use an alternate browser, such as Firefox.

If you continue to experience problems or need assistance with a workaround, please contact our support team.

Thank you for your understanding and cooperation.

Investigating: Our monitoring system has alerted us to a potential service issue with our platform for customers using our Verify V2 API.

Although it is not yet certain whether there is any customer impact, we are alerting customers immediately while our engineering teams investigate.

If there is a customer impact, it is likely to be affecting the following products:

Verify V2 - Email channel

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.

Investigating: We have been notified by our US suppliers about an issue impacting SMS messages for the following carrier: US Cellular. You might experience temporary delays in inbound SMS, outbound SMS and delivery receipts to US Cellular.

The carrier is aware of this issue and investigating the root cause. We will issue an update as soon as more information becomes available.

Please contact [email protected] if you have any questions.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The carrier has identified the issue and is working on a solution. We will update you as soon as we get relevant information from our partners.

Identified: The carrier has identified the issue and is working on a solution. We will update you as soon as we get relevant information from our partners.

Identified: The carrier has identified the issue and is working on a solution. We will update you as soon as we get relevant information from our partners.

Identified: The carrier has identified the issue and is working on a solution. We will update you as soon as we get relevant information from our partners.

Identified: The carrier has identified the issue and is working on a solution. We will update you as soon as we get relevant information from our partners.

Identified: The carrier has identified the issue and is working on a solution. We will update you as soon as we get relevant information from our partners.

Identified: The carrier has identified the issue and is working on a solution. We will update you as soon as we get relevant information from our partners.

Identified: The carrier has identified the issue and is working on a solution. We will update you as soon as we get relevant information from our partners.

Identified: The carrier has identified the issue and is working on a solution. We will update you as soon as we get relevant information from our partners.

Identified: The carrier has identified the issue and is working on a solution. We will update you as soon as we get relevant information from our partners.

Identified: The carrier has identified the issue and is working on a solution. We will update you as soon as we get relevant information from our partners.

Identified: The carrier has identified the issue and is working on a solution. We will update you as soon as we get relevant information from our partners.

Investigating: The carrier is continuing to investigate this issue. We will update you as soon as we get relevant information from our partners.

Investigating: We are continuing to investigate this issue. We will update you as soon as we get relevant information from our partners.

Investigating: We are continuing to investigate this issue. We will update you as soon as we get relevant information from our partners.

Investigating: We have observed SMS delivery degradation impacting 10DLC traffic towards AT&T USA. You may expect missing or delayed outbound messages, missing or late delivery receipts.

The carrier is aware of this issue and investigating the root cause. We will issue an update as soon as more information becomes available.

Please contact [email protected] if you have any questions.

Investigating: Please be advised that we are now observing message delivery degradation towards all major Networks in Portugal. This is related to nationwide power outage.

We are working with our carrier partners to resolve the issue and will issue an update as soon as more information becomes available.

Please contact [email protected] if you have any questions.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We have been notified by our supplier about delivery degradation for messages sent towards Tele2 Sweden.

We are working with our carrier partners to resolve the issue and will issue an update as soon as more information becomes available.

Please contact [email protected] if you have any questions.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: Please be advised that we are observing message delivery for degradation for domestic brands towards Telkomsel, Indonesia.

We are working with our carrier partners to resolve the issue and will issue an update as soon as more information becomes available.

Please contact [email protected] if you have any questions.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently observing degradation of Outbound calls towards some set of Japan Toll Free number ranges. We are working with our carrier partners to resolve the issue and will issue an update as soon as more information becomes available.

Please contact [email protected] if you have any questions.

Investigating: We have been notified by our supplier of SMS delivery degradation towards Peru Movistar.

We are working with our carrier partners to resolve the issue and will issue an update as soon as more information becomes available.

Please contact [email protected] if you have any questions.

Investigating: Please be informed that we are currently observing SMS delivery degradation towards Tigo, Paraguay.

We are working with our carrier partners to resolve the issue and will issue an update as soon as more information becomes available.

Please contact [email protected] if you have any questions.

Investigating: Our carrier partner is still working on this issue.

Investigating: We have been notified by our supplier about an Inbound and outbound SMS delivery degradation for messages sent towards a subset of our Israel Long Virtual Numbers. You may experience failures or delays for Inbound and outbound SMS sending towards your subscribed Israel Long Virtual Numbers.

We are working along with our partners to resolve the issue and will post an update as soon as more information becomes available.

Please contact [email protected] if you have any questions.

Resolved: This incident has been resolved.

Investigating: Please be informed we are observing SMS delivery degradation towards Nigeria-MTN network.

We are working with our carrier partners to resolve the issue and will issue an update as soon as more information becomes available.

Please contact [email protected] if you have any questions.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently observing SMS delivery degradation towards Mali Orange network.

We are working with our carrier partners to resolve the issue and will issue an update as soon as more information becomes available.

Please contact [email protected] if you have any questions.

Investigating: Please be advised that we have been notified about SMS delivery degradation towards Egypt Etisalat network .

We are working with our carrier partners to resolve the issue and will issue an update as soon as more information becomes available.

Please contact [email protected] if you have any questions