Announcing IP Address Changes: November 6, 2026 (No Operational Impact)
The published IP ranges for Zoom Meetings and Webinars, Contact Center, and Phone services have been updated, including the removal of decommissioned entries and mask changes. We recommend that network administrators with Zoom-specific firewall or network rules update their systems as soon as possible. Removed IPv4 addresses for Zoom Meetings and Webinars: 3.235.96.0/23 69.174.108.0/22 New IPv4 addresses for Zoom Meetings and Webinars: 3.235.96.26/31 3.235.96.158/31 69.174.110.0/23 Removed IPv4 addresses for Zoom Phone: 8.5.128.0/24 69.174.108.0/22 New IPv4 addresses for Zoom Phone: 69.174.110.0/23 Removed IPv4 addresses for Zoom Contact Center: 3.235.96.0/23 New IPv4 addresses for Zoom Contact Center: 3.235.96.26/31 3.235.96.158/31 For a complete list, please see: https://assets.zoom.us/docs/ipranges/Zoom.txt https://assets.zoom.us/docs/ipranges/ZoomMeetings.txt https://assets.zoom.us/docs/ipranges/ZoomPhone.txt https://assets.zoom.us/docs/ipranges/ZoomPhone-TCP443.txt https://assets.
The latest update from Zoom.
State
Scheduled
Starts
in 6 d
2026-11-07 07:59 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Zoom
The published IP ranges for Zoom Meetings and Webinars, Contact Center, and Phone services have been updated, including the removal of decommissioned entries and mask changes. We recommend that network administrators with Zoom-specific firewall or network rules update their systems as soon as possible. Removed IPv4 addresses for Zoom Meetings and Webinars: 3.235.96.0/23 69.174.108.0/22 New IPv4 addresses for Zoom Meetings and Webinars: 3.235.96.26/31 3.235.96.158/31 69.174.110.0/23 Removed IPv4 addresses for Zoom Phone: 8.5.128.0/24 69.174.108.0/22 New IPv4 addresses for Zoom Phone: 69.174.110.0/23 Removed IPv4 addresses for Zoom Contact Center: 3.235.96.0/23 New IPv4 addresses for Zoom Contact Center: 3.235.96.26/31 3.235.96.158/31 For a complete list, please see: https://assets.zoom.us/docs/ipranges/Zoom.txt https://assets.zoom.us/docs/ipranges/ZoomMeetings.txt https://assets.zoom.us/docs/ipranges/ZoomPhone.txt https://assets.zoom.us/docs/ipranges/ZoomPhone-TCP443.txt https://assets.
Affected components
8Zoom in the last 90 days
Full historyIncidents in 90 days
49
Days with an incident
41
Median duration
47 min
This incident
Not comparable
Other Zoom incidents
All incidentsZoom·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.
Zoom·Service Degradation Affecting Multiple Zoom Services
This incident has been resolved and the affected service has been restored.
Zoom·Service Degradation Affecting Zoom Meetings Services in the US.
This incident has been resolved.
Zoom·Service Degradation Affecting Zoom Learning Webpage
This incident has been resolved and the affected service has been restored.
Zoom·Service Degradation Affecting Meeting Summaries Via Email.
This incident has been 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.
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.cc/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.
https://outages.cc/feed.xml?providers=zoom/feed subscribe https://outages.cc/feed.xml?providers=zoomFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane