[Voice] Service Issue in Platform

Incident Report for Vonage API Status

Postmortem

[Voice] Service Issue in Platform

On August 9th an unusual burst of high traffic was being sent to the Voice API Service which caused some calls to be rejected and others to experience long times to connect.

‌

Date/Time Impacted

On August 9th, 2022 From 14:15 UTC until 16:35 UTC

‌

Services Impacted

Voice API Calls

‌

Summary

An unusual burst of high traffic was being sent to the Voice API Service.

‌

Root Cause

An unusual burst of high traffic was being sent to the Voice API Service.

‌

Restoration Actions

After investigation the offending traffic was identified and blocked, which stabilized the service.

‌

Next Steps

Preventative measures have already been put into place to ensure the traffic that was causing the problem is better managed through our systems in future.

Measures to reduce detection time and reduce the likelihood of future such events have already been identified and are prioritized as per our incident-handling process.

We value your feedback and want to do the best we can for you. Please let us know how we did or your ideas for how we can improve our incident communication processes through the following short survey:

https://forms.gle/1Ct3vRveAhFCBcQc9

Posted Aug 12, 2022 - 16:10 UTC

Resolved

The issue has been mitigated, and it is resolved.
Posted Aug 10, 2022 - 03:57 UTC

Monitoring

At 2022-08-09T16:09:39.000+0000 UTC until 2022-08-09T16:09:55.000+0000 UTC our monitoring alerted us to a potential service issue with our platform. During this time, calls may have taken longer to connect or be rejected.

SIP Trunking and Voice API were the affected services.

At this time, the issue appears to be mitigated and we are monitoring it.

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/360015693092-Nexmo-Incident-Handling - for an explanation of our approach to publishing incidents.
Posted Aug 09, 2022 - 16:22 UTC
This incident affected: Voice (Voice API, SIP Trunking).