Vonage incident

IR27192 - India inbound numbers not connecting

Minor Resolved View vendor source →

Vonage experienced a minor incident on September 8, 2025 affecting Inbound Voice Interactions and Inbound Voice Interactions and 1 more component, lasting 4d 3h. The incident has been resolved; the full update timeline is below.

Started
Sep 08, 2025, 07:49 AM UTC
Resolved
Sep 12, 2025, 11:08 AM UTC
Duration
4d 3h
Detected by Pingoru
Sep 08, 2025, 07:49 AM UTC

Affected components

Inbound Voice InteractionsInbound Voice InteractionsInbound Voice InteractionsInbound Voice Interactions

Update timeline

  1. investigating Sep 08, 2025, 07:49 AM UTC

    We are currently aware of an ongoing issue affecting inbound calls to certain India number ranges. Our Incident Management team is investigating the issue with priority.

  2. investigating Sep 08, 2025, 10:03 AM UTC

    The incident management team continues to work with the Carrier service provider to identify the problem.

  3. identified Sep 08, 2025, 01:58 PM UTC

    The provider of the impacted number range informed us that the outage is caused by a hardware malfunction in India, which has caused problems for a number of networks. We are working with them to get the issue resolved. As soon as we have any update we will let you know.

  4. identified Sep 09, 2025, 08:30 AM UTC

    The provider of the impacted number range is working to develop an alternative path. As soon as we have any update we will let you know.

  5. identified Sep 09, 2025, 03:03 PM UTC

    The provider of the impacted number range is working on resolving the issue related to the hardware malfunction, and have provided an ETA of 3 to 5 business days. We continue to monitor the progress and we will provide the next update in 3 business days, on Friday September 12th.

  6. monitoring Sep 11, 2025, 08:27 AM UTC

    Service is now recovered and we are monitoring. If you are still experiencing issues please contact Support.

  7. resolved Sep 12, 2025, 11:08 AM UTC

    This issue has been resolved. We are now working to generate a full root cause analysis which will be shared in the form of an Incident Report with affected customers.