Is Zoom Down?

CommunicationLive status, outages, and incident history

No. Zoom is up right now.

Every monitored Zoom system is operational as of October 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving1 active incident

Know the moment Zoom breaks

Zoom is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official Zoom status page

How we know: the official Zoom status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Zoom Component Status

The main Zoom systems on this page. All 305 are operational right now.

305operational

Apps by Zoom » Ellkay

Operational

Apps by Zoom » Epic FHIR

Operational

Apps by Zoom » Google Workspace

Operational

302 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Apps by Zoom » Lti Pro, Apps by Zoom » Microsoft OneDrive for Organizations, Apps by Zoom » Microsoft Teams, Apps by Zoom » Slack, Clinical Notes, My Notes, Zoom AI Services, Zoom Blog, Zoom Build Platform » CoBrowse SDK, Zoom Build Platform » Video SDK, Zoom Build Platform » Zoom AI Services API, Zoom Canvas, and 290 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Zoom Outages & Incidents

Incident history from the official Zoom status page, including resolution updates.

Zoom Conference Room Connector DNS Changes: November 14, 2026Scheduled for Nov 14, 2026 · 16h 0mScheduled

As part of ongoing service enhancements for the Cloud Room Connector (CRC) service, Zoom will be updating DNS records for SIP/H.323 endpoints in the Japan (Osaka and Tokyo), EU (France and Amsterdam), Australia (Melbourne and Sydney), Hong Kong, China, Canada (Toronto and Vancouver), and India (Mumbai and Hyderabad) regions. In addition to the DNS record update, we will be decommissioning legacy DNS records in other regions that are no longer in use. Effective Date: November 14, 2026 Action Required To avoid service disruption, we recommend reviewing your CRC endpoint configurations as soon as possible, updating your DNS records with the new entries, and removing the older legacy records before November 14, 2026. If you have any questions or issues, please contact Zoom Support. DNS Record Updates Japan Region We will update the country-level domain and data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows: zmjp.us >> jp.zoomcrc.com os.zmjp.us >> kix.zoomcrc.com ty.zmjp.us >> nrt.zoomcrc.com Records to be replaced (A-Record and SRV-Record): zmjp.us: _h323cs._tcp.zmjp.us _sip._tcp.zmjp.us _sips._tcp.zmjp.us _sip._udp.zmjp.us os.zmjp.us: _h323cs._tcp.os.zmjp.us _sip._tcp.os.zmjp.us _sips._tcp.os.zmjp.us _sip._udp.os.zmjp.us ty.zmjp.us: _h323cs._tcp.ty.zmjp.us _sip._tcp.ty.zmjp.us _sips._tcp.ty.zmjp.us _sip._udp.ty.zmjp.us New records (A-Record and SRV-Record): jp.zoomcrc.com: _h323cs._tcp.jp.zoomcrc.com _sip._tcp.jp.zoomcrc.com _sips._tcp.jp.zoomcrc.com _sip._udp.jp.zoomcrc.com kix.zoomcrc.com: _h323cs._tcp.kix.zoomcrc.com _sip._tcp.kix.zoomcrc.com _sips._tcp.kix.zoomcrc.com _sip._udp.kix.zoomcrc.com nrt.zoomcrc.com: _h323cs._tcp.nrt.zoomcrc.com _sip._tcp.nrt.zoomcrc.com _sips._tcp.nrt.zoomcrc.com _sip._udp.nrt.zoomcrc.com Canada Region We will update the country-level domain and data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows: zmca.us >> ca.zoomcrc.com tr.zmca.us >> yyz.zoomcrc.com vn.zmca.us >> yvr.zoomcrc.com Records to be replaced (A-Record and SRV-Record): zmca.us: _h323cs._tcp.zmca.us _sip._tcp.zmca.us _sips._tcp.zmca.us _sip._udp.zmca.us tr.zmca.us: _h323cs._tcp.tr.zmca.us _sip._tcp.tr.zmca.us _sips._tcp.tr.zmca.us _sip._udp.tr.zmca.us vn.zmca.us: _h323cs._tcp.vn.zmca.us _sip._tcp.vn.zmca.us _sips._tcp.vn.zmca.us _sip._udp.vn.zmca.us New records (A-Record and SRV-Record): ca.zoomcrc.com: _h323cs._tcp.ca.zoomcrc.com _sip._tcp.ca.zoomcrc.com _sips._tcp.ca.zoomcrc.com _sip._udp.ca.zoomcrc.com yyz.zoomcrc.com: _h323cs._tcp.yyz.zoomcrc.com _sip._tcp.yyz.zoomcrc.com _sips._tcp.yyz.zoomcrc.com _sip._udp.yyz.zoomcrc.com yvr.zoomcrc.com: _h323cs._tcp.yvr.zoomcrc.com _sip._tcp.yvr.zoomcrc.com _sips._tcp.yvr.zoomcrc.com _sip._udp.yvr.zoomcrc.com EU Region We will update the data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows: am.zmeu.us >> ams.zoomcrc.com fr.zmeu.us >> fra.zoomcrc.com Records to be replaced (A-Record and SRV-Record): am.zmeu.us: _h323cs._tcp.am.zmeu.us _sip._tcp.am.zmeu.us _sips._tcp.am.zmeu.us _sip._udp.am.zmeu.us fr.zmeu.us: _h323cs._tcp.fr.zmeu.us _sip._tcp.fr.zmeu.us _sips._tcp.fr.zmeu.us _sip._udp.fr.zmeu.us New records (A-Record and SRV-Record): ams.zoomcrc.com: _h323cs._tcp.ams.zoomcrc.com _sip._tcp.ams.zoomcrc.com _sips._tcp.ams.zoomcrc.com _sip._udp.ams.zoomcrc.com fra.zoomcrc.com: _h323cs._tcp.fra.zoomcrc.com _sip._tcp.fra.zoomcrc.com _sips._tcp.fra.zoomcrc.com _sip._udp.fra.zoomcrc.com Decommisioned Legacy Records Hosted Zone: zmeu.us A-Records: sip.zmeu.us vip2.zmeu.us sip2.zmeu.us udp2.zmeu.us udp.zmeu.us SRV-Records: _h323cs._tcp.vip2.zmeu.us _sip._tcp.vip2.zmeu.us _sips._tcp.vip2.zmeu.us _sip._udp.vip2.zmeu.us Australia Region We will update the country-level domain and data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows: zmau.us >> au.zoomcrc.com me.zmau.us >> mel.zoomcrc.com sy.zmau.us >> syd.zoomcrc.com Records to be replaced (A-Record and SRV-Record): zmau.us: _h323cs._tcp.zmau.us _sip._tcp.zmau.us _sips._tcp.zmau.us _sip._udp.zmau.us me.zmau.us: _h323cs._tcp.me.zmau.us _sip._tcp.me.zmau.us _sips._tcp.me.zmau.us _sip._udp.me.zmau.us sy.zmau.us: _h323cs._tcp.sy.zmau.us _sip._tcp.sy.zmau.us _sips._tcp.sy.zmau.us _sip._udp.sy.zmau.us New records (A-Record and SRV-Record): au.zoomcrc.com: _h323cs._tcp.au.zoomcrc.com _sip._tcp.au.zoomcrc.com _sips._tcp.au.zoomcrc.com _sip._udp.au.zoomcrc.com mel.zoomcrc.com: _h323cs._tcp.mel.zoomcrc.com _sip._tcp.mel.zoomcrc.com _sips._tcp.mel.zoomcrc.com _sip._udp.mel.zoomcrc.com syd.zoomcrc.com: _h323cs._tcp.syd.zoomcrc.com _sip._tcp.syd.zoomcrc.com _sips._tcp.syd.zoomcrc.com _sip._udp.syd.zoomcrc.com Decommisioned Legacy Records Hosted Zone: zmau.us SRV-Records: _h323cs._tcp.vip2.zmau.us _sip._tcp.vip2.zmau.us _sip._tcp.vip2.zmau.us _sip._udp.vip2.zmau.us _sips._udp.vip2.zmau.us China Region We will update the country-level domain and data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows: zmcn.us >> cn.zoomcrc.com Records to be replaced (A-Record and SRV-Record): zmcn.us: _h323cs._tcp.zmcn.us _sip._tcp.zmcn.us _sips._tcp.zmcn.us _sip._udp.zmcn.us New records (A-Record and SRV-Record): cn.zoomcrc.com: _h323cs._tcp.cn.zoomcrc.com _sip._tcp.cn.zoomcrc.com _sips._tcp.cn.zoomcrc.com _sip._udp.cn.zoomcrc.com Decommisioned Legacy Records Hosted Zone: zmcn.us A-Records: udp.zmcn.us udp2.zmcn.us vip2.zmcn.us sip2.zmcn.us sip.zmcn.us SRV-Records: _h323cs._tcp.vip2.zmcn.us _sip._tcp.vip2.zmcn.us _sips._tcp.vip2.zmcn.us _sip._udp.vip2.zmcn.us Hong Kong Region We will update the country-level domain and data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows: zmhk.us >> hkg.zoomcrc.com Records to be replaced (A-Record and SRV-Record): zmhk.us: _h323cs._tcp.zmhk.us _sip._tcp.zmhk.us _sips._tcp.zmhk.us _sip._udp.zmhk.us New records (A-Record and SRV-Record): hkg.zoomcrc.com: _h323cs._tcp.hkg.zoomcrc.com _sip._tcp.hkg.zoomcrc.com _sips._tcp.hkg.zoomcrc.com _sip._udp.hkg.zoomcrc.com Decommisioned Legacy Records Hosted Zone: zmhk.us A-Records: vip2.zmhk.us udp2.zmhk.us sip2.zmhk.us udp.zmhk.us sip.zmhk.us SRV-Records: _sip._tcp.vip2.zmhk.us _sip._udp.vip2.zmhk.us _sips._tcp.vip2.zmhk.us _h323cs._tcp.vip2.zmhk.us India Region We will update the country-level domain and data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows: zmin.us >> in.zoomcrc.com hy.zmin.us >> hy2.zoomcrc.com mb.zmin.us >> mb2.zoomcrc.com Records to be replaced (A-Record and SRV-Record): zmin.us: _h323cs._tcp.zmin.us _sip._tcp.zmin.us _sips._tcp.zmin.us _sip._udp.zmin.us hy.zmin.us: _h323cs._tcp.hy.zmin.us _sip._tcp.hy.zmin.us _sips._tcp.hy.zmin.us _sip._udp.hy.zmin.us mb.zmin.us: _h323cs._tcp.mb.zmin.us _sip._tcp.mb.zmin.us _sips._tcp.mb.zmin.us _sip._udp.mb.zmin.us New records (A-Record and SRV-Record): in.zoomcrc.com: _h323cs._tcp.in.zoomcrc.com _sip._tcp.in.zoomcrc.com _sips._tcp.in.zoomcrc.com _sip._udp.in.zoomcrc.com hy2.zoomcrc.com: _h323cs._tcp.hy2.zoomcrc.com _sip._tcp.hy2.zoomcrc.com _sips._tcp.hy2.zoomcrc.com _sip._udp.hy2.zoomcrc.com mb2.zoomcrc.com: _h323cs._tcp.mb2.zoomcrc.com _sip._tcp.mb2.zoomcrc.com _sips._tcp.mb2.zoomcrc.com _sip._udp.mb2.zoomcrc.com Decommisioned Legacy Records Hosted Zone: zmin.us A-Records: vip2.zmin.us udp2.zmin.us udp.zmin.us sip2.zmin.us sip.zmin.us SRV-Records: _sips._tcp.vip2.zmin.us _sip._udp.vip2.zmin.us _sip._tcp.vip2.zmin.us _h323cs._tcp.vip2.zmin.us

Zoom Phone Maintenance - EU01 - FRA2 Data Center: November 09, 2026Scheduled for Nov 9, 2026 · 62h 30mScheduled

Zoom will perform service maintenance at our EU01-FRA2 Data Center starting at 9:00 AM Pacific on November 09, 2026. Zoom Phone users registered to the those sip zones will be automatically registered in the AMS2 sip zone sequentially. During the maintenance window, a brief disconnection may be experienced and notifications may be missed. If you get disconnected, the system will attempt to reconnect you automatically.

Scheduled Zoom Software Quarterly Lifecycle Update (11/7/2026)Scheduled for Nov 8, 2026 · 1h 0mScheduled

As a reminder approximately 30 days ahead of the upcoming enforcement, Zoom will be enforcing a new global minimum version this November 7. This affects the following products: ◦ VDI plugin ◦ Zoom Phone Local Survivability (ZPLS) module ◦ Meeting SDK (Web) For more information, such as specific versions we are enforcing, refer to the Zoom Software Quarterly Lifecycle Policy support article: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0061130 To assist with checking the client versions on your account, refer to the Dashboard support article: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0062208#h_13ce9a73-91e5-4df6-9cb5-c815b1605cf5 --- [2026-08-07T10:41:03.507-07:00] (scheduled) Zoom will be enforcing a new minimum version for the following areas, approximately 90 days from now, on November 7, 2026: VDI plugin Zoom Phone Local Survivability (ZPLS) module Meeting SDK (Web) All other clients and plugins not listed here will maintain the same version requirements as the August 2026 enforcement. For more information, such as specific versions we are enforcing, refer to the Zoom Software Quarterly Lifecycle Policy support article: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0061130 To assist with checking the client versions on your account, refer to the Dashboard support article: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0062208#h_13ce9a73-91e5-4df6-9cb5-c815b1605cf5

Zoom Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Zoom incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed

Jul 13100.00% average · 34 days with incidentsOct 11

Going further back: Zoom uptime by month and every recorded Zoom outage.

Live Zoom Outage Reports

Problems reported by engineers using Zoom. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total

24h agoNothing reportednow

No Zoom problems reported yet.

Something wrong with Zoom on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Zoom

Zoom is a video conferencing and unified communications platform with 300M+ daily meeting participants across enterprise, education, and consumer markets. Zoom outages prevent video meetings, webinars, and phone calls for millions worldwide. Track Zoom status and outages here.

Over the past 30 days, PulsAPI has measured Zoom uptime at 100.00%. Response times, incident history, and SLA tracking for Zoom are available on the PulsAPI dashboard.

Zoom Status FAQ

Is Zoom down right now?

The verdict at the top of this page comes from the latest poll of the official Zoom status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Zoom is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Zoom recovers.

How do I check Zoom uptime history?

PulsAPI tracks Zoom uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Zoom changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Zoom outages?

PulsAPI reads the official Zoom status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Zoom components?

Yes. PulsAPI monitors 305 individual Zoom components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Zoom goes down?

Yes. Create a free account and subscribe to Zoom: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Zoom to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Zoom problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Zoom?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Zoom plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Zoom with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services