Update - Our providers have fixed the DNS resolution. Vonage will proceed with testing and will schedule the restoration of the usual network topology and proxies use for China Relay as soon as possible. At the moment customers should expect to see the same quality of service in their communications in line with the last couple of days. We will continue to monitor the situation and provide updates when necessary. Please reach out to support@api.vonage.com if you have any specific problems to report with supporting data.
Jul 4, 07:53 UTC
Update - Our engineering team is continually working to restore the usual network topology and proxies use. There are no disruptions ongoing, and the customer traffic is still diverted out from China Relay feature proxies, which could potentially imply some QoS reduction for customers that had used the China Relay feature. We will continue to monitor the situation and provide updates. Please reach out to support@api.vonage.com if you have any specific problems to report with supporting data.
Jul 1, 02:17 UTC
Update - Connectivity degradation with China was restored as indicated in the last update and is expected to be operative without disruption, as the needed measures were put in place by engineering to avert the DNS resolution problem.

Customers should not see impediments in their communications, and those customers not directly leveraging China Relay feature should see no difference in their communications at this point. Traffic has been temporarily diverted out from China Relay feature proxies, which could potentially imply some QoS reduction for customers that are used to the China Relay feature. Capacity to connect and communicate should be preserved at this point in any case.

Engineering is working to restore the usual network topology and proxies use. Currently there is no disruption ongoing, but we maintain the monitoring status. Please reach out to support@api.vonage.com if you have any specific problem to report with supporting data.

Jun 27, 08:50 UTC
Monitoring - We have detected an issue with the Vonage China proxy on 2022-06-25 at 0:00 UTC. The root cause would appear related to a DNS resolution outage. We have applied mitigation measures so that connectivity is restored to affected customers in the region. We are moving to the monitoring status at this point while engineering continues with the necessary work to fully resolve the issue. Please reach out to support@api.vonage.com if you have any further questions.
Jun 26, 15:14 UTC
Investigating - We have detected an issue with the Vonage China proxy and are working to resolve the issue on 2022-06-25 at 0:00 UTC. Please reach out to support@api.vonage.com if you have any further questions.
Jun 26, 12:36 UTC
Enterprise Operational
Enterprise Video Operational
Enterprise API Operational
Enterprise Broadcast Operational
Enterprise SIP Operational
Enterprise Session Monitoring Operational
Enterprise Archiving Operational
Standard Operational
Standard Video Operational
Standard API Operational
Standard Broadcast Operational
Standard SIP Operational
Standard Session Monitoring Operational
Standard Archiving Operational
Tools ? Operational
Account Portal Operational
China Relay Degraded Performance
Advanced Insights Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Jul 5, 2022
Resolved - We were observing delays in uploading some archives to destination storage buckets starting July 2nd. Engineering did the due corrections and those were fully caught up around July 4th at 22h00 UTC.

Please contact support@api.vonage.com for any questions. For any specific issue, please report it with supporting data.

Jul 5, 07:00 UTC
Monitoring - We have implemented a fix for the uploading archives issue.

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

Jul 4, 17:19 UTC
Investigating - We were observing delays in uploading some archives to destination storage buckets starting July 2nd. Engineering is working to restore the timely upload of all archives and correct the degradation. Please contact support@api.vonage.com for any questions. For any specific issue, please report it with supporting data.
Jul 4, 15:56 UTC
Jul 4, 2022
Resolved - One archiving server in US EAST region had a failure around July 3rd 23:41 UTC. The few recordings ongoing at that point in that specific server would have been impacted. The issue was immediately resolved for any new recordings created after.

Please contact support@api.vonage.com for any questions.
For any specific issue, please report it with supporting data.

Jul 4, 17:20 UTC
Jul 3, 2022

No incidents reported.

Jul 2, 2022

No incidents reported.

Jul 1, 2022
Resolved - All services have been restored so we are moving this incident to resolved.
Please let support@api.vonage.com know if you continue to experience problems with this.
A post-mortem will be published in the next few days.

Jul 1, 21:08 UTC
Monitoring - The problem has been resolved and will continue to monitor the service during the next few hours. We will update you when this is fully resolved or if there are any new updates.

If you have any questions in the meanwhile, please contact support@api.vonage.com.

Jul 1, 12:09 UTC
Investigating - We have detected a degradation in our DB access responsiveness that could lead in some cases to issues operating with the Video API such as new video sessions, archiving APIs, new connections, broadcast, and potentially some delay on archive uploads. The issue is now under investigation. Currently observed incident timeframe impact window is 05:10 UTC to 10:50 UTC. During this time customers would have received intermittent failures from our system.

If you have any questions in the meanwhile, please contact support@api.vonage.com.

Jul 1, 11:39 UTC
Jun 30, 2022
Resolved - There is no ongoing customer impact. This issue is resolved, but please reach out to support@api.vonage.com if you have any further questions.
Jun 30, 22:59 UTC
Monitoring - At 19:14 UTC, one of our Enterprise Video servers in our Frankfurt datacenter restarted. Customer connections would have been dropped. The instance immediately recovered afterwards and we are monitoring.
Jun 30, 22:18 UTC
Resolved - After additional investigation, we’ve detected that during the incident timeframe there were also issues initiating new video sessions, new archiving sessions and archive uploads. The issue is now fully resolved. We’re updating the incident timeframe to reflect a larger impact window of 11:02 UTC to 18:50 UTC. During this time clients would have received intermittent failures from our system.
Jun 30, 21:27 UTC
Monitoring - We have implemented a fix for the uploading archives issue.

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

Jun 30, 20:06 UTC
Investigating - We are observing delays in uploading some archives to customers' storage buckets starting June 30 at 12:48 UTC.
We are investigating to understand the full impact of the issue. We aim to provide an update on our investigation soon.
If you have any questions in the meanwhile, please contact support@api.vonage.com.

Jun 30, 19:03 UTC
Jun 29, 2022
Resolved - This issue has been resolved. Please reach out to support@api.vonage.com if you have any further questions.
Jun 29, 16:43 UTC
Monitoring - We have implemented the fix and the callbacks are currently being processed normally. There is no ongoing impact and customers will no longer experience any delay for the new sessions. We will continue monitoring the callback service for the next few hours and will post an update once this is fully resolved.

Please let support@api.vonage.com know if you continue to experience problems with this.

Jun 29, 16:01 UTC
Identified - An issue has been identified with our Session Monitoring callback infrastructure. As a result of this, some customers might experience a slight delay in receiving the session monitoring callbacks. We will update you once this is fixed or if there is any progress.

Please reach out to support@api.vonage.com if you have any further questions.

Jun 29, 15:28 UTC
Jun 28, 2022
Resolved - One of our servers in the EU-WEST-1 (Dublin) restarted on the Enterprise environment on 2022-06-28 at 01:17 Local (UTC). There is no ongoing customer impact. The server is taken out of rotation. This issue is resolved, but customer connections would have been affected. Please reach out to support@api.vonage.com if you have any further questions.
Jun 28, 01:26 UTC
Jun 27, 2022
Jun 26, 2022
Jun 25, 2022

No incidents reported.

Jun 24, 2022

No incidents reported.

Jun 23, 2022
Resolved - From 09:24am UTC to 09:57am UTC, SIP interconnect callbacks would have been delayed in our Singapore region. The service has recovered and is fully functioning at this time.
Jun 23, 10:37 UTC
Jun 22, 2022
Resolved - The Standard SIP, Enterprise SIP problem has been resolved.

The following services were impacted from 7:00pm UTC to 7:05pm UTC June 22, 2022.

All services have been restored.

Please let support@api.vonage.com know if you continue to experience problems with this.

Jun 22, 20:17 UTC
Update - We are continuing to monitor for any further issues.
Jun 22, 19:27 UTC
Monitoring - At 3:00pm EDT one of the components for the SIP interconnect crashed and immediately restarted. This could have impacted the ability to control SIP sessions, but the media would have not been impacted. The instance is now recovered and we are monitoring.

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

Standard SIP, Enterprise SIP

We aim to provide an update on our investigation within 30 minutes.

Please see this article - https://support.tokbox.com/hc/en-us/articles/360046878071 -for an explanation of the Vonage API group's approach to publishing information about incidents.

Jun 22, 19:26 UTC
Jun 21, 2022
Resolved - This incident has been resolved.
Jun 21, 14:24 UTC
Update - We are continuing to monitor for any further issues.
Jun 21, 10:45 UTC
Monitoring - The issue was resolved at 9:02am UTC and we are continuing to monitor the service while we investigate the cause.
Jun 21, 09:38 UTC
Investigating - At 8:55am UTC we were notified that one of our api servers in the US East 1 region failed. The server was automatically taken out of rotation but any API requests that could have hit that server during the failure would have failed, implying some degraded the experience of the affected sessions. Any affected sessions should have recovered the normal activity once the server was removed automatically. Our team are investigating the cause of the failure.
Jun 21, 09:36 UTC