Live

Service Degradation for a subset of users affecting outbound Zoom Phone calls in Australia.

0

Outbound Zoom Phone calls in Australia did not work for a subset of users. Zoom Phone Calling (Inbound/Outbound) was affected. Zoom reports that the incident is resolved and that the service is restored. The outage lasted 12 minutes.

State

Resolved

Started

Lasted

12 min

Worst impact

Notice

Timeline

2 updates
20:3020:3320:3620:3920:42
NoticeUpdate postedTimes in UTC

Monitoring

12 min 100%

Updates

Times in UTC

As posted by Zoom

Resolved

This incident has been resolved.

Monitoring

On 11/20/2026, Between 18:26 UTC to 19:22 UTC, a subset of users may have experienced issues with outbound Zoom Phone calls in Australia. This incident has been resolved and the affected services have been restored.

Affected components

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

Zoom in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

68

Days with an incident

55

Median duration

1 h 18 min

This incident

84% shorter than the median

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

14 days
median 1 h 18 min
90 days agoToday

Other Zoom incidents

All incidents

Zoom·Service degradation affecting multiple services in the US region

Zoom services had intermittent problems in the US region. Affected components include Web Portal, Web Client, Zoom AI, and Zoom Whiteboard. Zoom reports that the incident is resolved and the services are restored. The incident lasted 38 minutes.

Resolved

Zoom·Service Degradation Affecting Zoom MyNotes in the US region.

Zoom MyNotes had a service degradation in the US region. Zoom reports that the incident is resolved and that the affected services are restored. The incident lasted 86 minutes.

Resolved

Zoom·Service Degradation Affecting Subset of Users using Zoom Phone Calls in Europe Region.

Zoom Phone inbound and outbound calls did not work for some users in the EMEA region. Zoom reports that the incident is resolved and the services are restored. The incident lasted 13 minutes.

Resolved

Zoom·Service degradation affected a subset of users attempting to approve attendees for Webinar Registrations in the North America region.

Zoom Webinar Registration attendee approval did not work for some users in the North America region. The Zoom Web Portal was affected. Zoom reports that the incident is resolved and that it lasted 15 minutes.

Resolved

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

Zoom Phone inbound calls did not work for some Jio subscribers in India. The affected components were Calling (Inbound/Outbound) and Zoom Phone - APAC - Calling (Inbound/Outbound). Zoom reports that the incident is resolved and lasted 5 hours and 30 minutes.

Resolved

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