Live

Service Degradation Affecting Zoom Phone Inbound Calls for Subset of Jio subscribers in India

0

Zoom Phone inbound calls do not work for some Jio subscribers in India. The affected components are Calling and Zoom Phone APAC Calling. Zoom identified the cause and works with a vendor on a fix.

State

Identified

Started

Ongoing for

3 h 16 min

Worst impact

Degraded

Timeline

3 updates
07:3308:2209:1110:0010:49
DegradedUpdate postedTimes in UTC

Investigating

18 min 9%

Identified

2 h 58 min 91%

Updates

Times in UTC

As posted by Zoom

Identified

Our team continue to work with our vendor on a resolution for the issue affecting Zoom Phone Inbound calls for subset of Reliance Jio subscribers in India. We will keep you informed with timely updates as progress is made. Thank you for your patience.

Identified

We have successfully identified the root cause affecting Zoom Phone Inbound calls for subset of Reliance Jio subscribers in India. Our team is actively working with our vendor on a resolution, and we will keep you informed with timely updates as progress is made. Thank you for your patience.

Investigating

We are currently investigating a service degradation affecting Zoom Phone Inbound calls for subset of Jio subscribers in India. Our team is actively working to identify the impact and root cause. We will provide an update as soon as more information becomes available. We appreciate your patience as we work to resolve this issue.

Affected components

2
Calling (Inbound/Outbound)Zoom Phone - APAC - Calling (Inbound/Outbound)

Zoom in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

63

Days with an incident

52

Median duration

1 h 21 min

This incident

2.4× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

14 days
median 1 h 21 min
90 days agoToday

Other Zoom incidents

All incidents

Follow Zoom

Your coding agent knows when Zoom is down, and tells you when a failure is theirs, not yours. You can also get Zoom incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "zoom" and tell me if Zoom has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=zoom
Slack
/feed subscribe https://outages.live/feed.xml?providers=zoom

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane