outages.live
Live
ZoomMaintenance ·

Scheduled Maintenance – Contact Center Services: November 06, 2026

MaintenanceOfficial update

We are currently performing scheduled maintenance on our Contact Center infrastructure. During this window, support calls will continue to be accepted and handled as normal; however, response times may be slower than usual as our team works through the maintenance activities. We appreciate your patience and apologize for any inconvenience. We will provide an update once maintenance is complete.

The latest update from Zoom.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Zoom

Scheduled

We are currently performing scheduled maintenance on our Contact Center infrastructure. During this window, support calls will continue to be accepted and handled as normal; however, response times may be slower than usual as our team works through the maintenance activities. We appreciate your patience and apologize for any inconvenience. We will provide an update once maintenance is complete.

Affected components

2
Zoom Contact CenterZoom CX - Global - Zoom Contact Center

Zoom in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

51

Days with an incident

44

Median duration

1 h 17 min

This incident

Not comparable

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

14 days
median 1 h 17 min
90 days agoToday

Other Zoom incidents

All incidents

Zoom·Service Degradation Affecting Zoom Mail, Calendar and Scheduler.

Zoom Mail, Calendar, and Zoom Scheduler had degraded service. Zoom reported that the incident is resolved. The outage lasted about 97 minutes.

Resolved

Zoom·Service Degradation Affecting Outbound MMS Services in the US region

Zoom reports that outbound MMS services did not work for some users in the US region. The affected components are SMS/MMS (Inbound/Outbound) and Zoom Phone - NORTH AMERICA - SMS/MMS (Inbound/Outbound). Zoom reports that the incident is resolved, and it lasted about 7 hours and 51 minutes.

Resolved

Zoom·Service Degradation Affecting the Evaluations Acknowledge Button in Zoom Quality Management in the US Region

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

Resolved

Zoom·Service Degradation Affecting Multiple Zoom Services

This incident has been resolved and the affected service has been restored.

Resolved

Zoom·Service Degradation Affecting Zoom Meetings Services in the US.

This incident has been resolved.

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