Live

Service degradation affecting Zoom Calendar service in US and Europe region

0

Zoom Calendar and Zoom Mail Calendar had a service degradation. The problem affected some users in the US and Europe regions. Zoom reports that the incident is resolved, and it lasted 22 minutes.

State

Resolved

Started

Lasted

22 min

Worst impact

Degraded

Timeline

3 updates
17:1717:2317:2817:3317:39
DegradedUpdate postedTimes in UTC

Investigating

13 min 59%

Monitoring

9 min 41%

Updates

Times in UTC

As posted by Zoom

Resolved

This incident has been resolved and the affected services have been restored.

Monitoring

The issue preventing subset of users to use Calendar services has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.

Investigating

We are currently investigating a service degradation affecting subset of users using Zoom Calendar service in US and EU region. 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
CalendarZoom Mail - Calendar

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

73% 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 21 min
90 days agoToday

Other Zoom incidents

All incidents

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

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.

Degraded

Zoom·Service Degradation Affecting My Files Functionality in Zoom Hub in US Region

Zoom Hub My Files did not work in the US region. Users got permission errors. Zoom reports that the incident is resolved. It lasted 1 hour and 33 minutes.

Resolved

Zoom·Service Degradation Affecting Outbound SMS due to an underlying carrier issue in the Australia region.

Zoom outbound SMS did not work in the Australia region. The incident affected SMS/MMS (Inbound/Outbound), SMS (Inbound/Outbound), Zoom Phone - Australia - SMS/MMS (Inbound/Outbound), and Zoom CX - Australia - SMS (Inbound/Outbound). Zoom reports that the incident is resolved. It lasted 82 minutes.

Resolved

Zoom·Service Degradation Affecting Zoom Events custom domain

Zoom Events custom domain had degraded service. The incident is resolved. The outage lasted about 24 minutes.

Resolved

Zoom·Service Degradation Affecting Zoom Workflow Service

Zoom Workflows and Zoom AIC had degraded service on 2026-11-15. Users could not view the Zoom Workflow tab in the Zoom Client. Zoom reports that the incident is resolved. The outage lasted about 2 hours and 50 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