Is Zoom Down?

Zoom is the backbone of remote work for hundreds of millions of people — team standups, client demos, all-hands calls, virtual classrooms. When it goes down, meetings collapse, deals stall, and everyone starts frantically typing "is Zoom down?" into their search bar.

This guide helps you answer that question in under two minutes, figure out whether the problem is Zoom or your own setup, and make sure you are never caught off guard again.

Is Zoom Down Right Now?

The fastest way to know for certain: check live Zoom status on Statusfield →

Statusfield monitors Zoom continuously and surfaces outages the moment they are detected — often before an official incident is acknowledged. You will see per-component status (meetings, webinars, phone, chat, API) so you can tell exactly what is broken and what is still working.

What a Zoom Outage Looks and Feels Like

Zoom outages rarely announce themselves with a clear error message. More often, they show up as:

Symptom	What it usually signals
"Unable to connect" at the join screen	Meeting server or authentication issue
Stuck at "Connecting…" or "Waiting for host"	Session negotiation failing server-side
Video freezes but audio continues	Media server degradation (video path only)
Audio drops but video stays	Different media server path degraded
Login loop — password accepted but session never starts	Identity/auth service issue
Screen share fails to start or black-screens for participants	Screen-share transcoding infrastructure
Meeting recording fails or gets stuck at "processing"	Cloud recording pipeline failure
Webinar registration emails not arriving	Email delivery or Zoom Webinar backend
"Meeting not found" for a valid link	Zoom scheduling API or meeting lookup failure

Not all of these are always a platform-wide outage. Some are component-specific. That is why checking per-component status matters more than a single "Zoom is up/down" indicator.

Zoom's Components — What Breaks Independently

Zoom is not a monolith. Its platform has multiple components that can degrade or fail without the others going down:

Component	What it powers	Who notices
Meeting	Standard Zoom meetings	Every user running a meeting
Webinar	Zoom Webinar product	Event hosts and attendees
Zoom Phone	Cloud VoIP and SMS	Teams using Zoom Phone
Zoom Chat	Team messaging (formerly Team Chat)	Internal chat users
Zoom Rooms	Conference room hardware systems	IT and in-office setups
Zoom Mail / Calendar	Integrated email and scheduling	Users on Zoom's email product
Dashboard	Admin portal and analytics	IT admins and operations
API / Webhooks	Programmatic access for integrations	Developers, LMS, CRM integrations
Web Portal	Browser-based Zoom management	Account settings, scheduling

A meeting component outage is the broadest — it hits every user joining or hosting. An API outage is invisible to casual users but breaks every scheduler, CRM sync, and recording workflow that talks to Zoom programmatically.

Is It Zoom — or Is It You?

This is the most important question to answer before you do anything else. Here is a quick split-test:

Signs it is a Zoom platform issue:

• Multiple people on different networks and devices cannot join
• The problem started at roughly the same time for your whole team
• Statusfield or community reports show active Zoom incidents
• Your mobile data and your home Wi-Fi both fail the same way

Signs it is local to you or your network:

• You are the only person having trouble while colleagues are on calls fine
• Zoom works on your phone (mobile data) but not your laptop (corporate Wi-Fi)
• Your corporate firewall or VPN recently changed
• You just updated the Zoom desktop app
• Other internet services are also slow or broken

Quick local-side checks:

1. Try the Zoom web client in your browser instead of the desktop app — if it works, the app install is the issue, not Zoom's servers.
2. Disconnect your VPN if you use one. VPNs frequently block the UDP ports Zoom needs for media.
3. Try from a different network — mobile hotspot, a coffee shop, home vs. office. If a different network works, the problem is upstream of your device.
4. Try a different device entirely. If a colleague's laptop joins the same meeting fine, the issue is device-specific.

What to Do When Zoom Is Down

Once you have confirmed it is a real Zoom outage, here is the playbook:

For meeting hosts and participants

Immediately:

1. Switch to the Zoom web client at zoom.us/wc — it bypasses the desktop app entirely and sometimes stays functional when the native client cannot connect, particularly during partial outages.
2. If audio is more important than video, have participants call in via the phone dial-in number embedded in the meeting invite. Zoom's PSTN infrastructure (phone dial-in) is on a separate path and frequently stays up when IP media is degraded.
3. Fall back to a backup call option — a Google Meet, Microsoft Teams, or plain phone call. The five minutes you spend setting this up before a meeting is always worth it.

Clear the app cache if you suspect a client-side issue:

• Mac: Quit Zoom, then delete ~/Library/Application Support/zoom.us/ and relaunch.
• Windows: Quit Zoom, delete %APPDATA%\Zoom\data\ and relaunch.
• iOS / Android: Go to app settings, clear cache, force-stop, reopen.

Do not clear the cache while an active outage is happening — it will not help and will slow down your recovery once the outage resolves.

For IT teams and admins

1. Alert your users before they start messaging support. A quick Slack or email message saying "Zoom is experiencing a service disruption, here is the backup meeting link" prevents a flood of tickets.
2. Check whether your backup call tool (Teams, Meet, WebEx) is still operational before you route everyone there — it would be unfortunate to fall back to a platform that is also having issues.
3. Document the outage start time. You will need it when filling out an incident postmortem or claiming an SLA credit from Zoom.

Zoom Error Codes and What They Mean

When Zoom fails, it often shows a numeric error code. Here is a quick reference for the ones users encounter most:

Error code	What it means	Likely cause
1001	Account not found	Account lookup failed — can be auth service degradation or a local credential issue
1002	Can't connect to meeting	General connection failure — try the web client or a different network
2008	Invalid Zoom meeting ID	The meeting link is wrong or expired — confirm the host's link, or check for API failures affecting scheduling
3000	Cannot connect to Zoom service	Network or firewall blocking Zoom, or a genuine Zoom infrastructure failure
5000	Connection error	Firewall or proxy blocking Zoom; also appears during broader service outages
5003	Cannot connect — firewall or proxy	Your network is blocking Zoom's ports (TCP 443, UDP 8801–8802)
5004	Timed out	Zoom's servers are not responding within the expected window — either an outage or extreme latency

Codes in the 3000 and 5000 range are almost always network-path issues — either your local network or Zoom's infrastructure. Check Statusfield first to rule out a platform outage, then investigate locally.

Why Zoom Outages Happen

Understanding the failure modes helps you plan for them:

Synchronized traffic spikes. Millions of meetings start on the hour and the half-hour across every time zone. Monday at 9 AM across North America, Europe, and Asia-Pacific means a simultaneous surge that is structurally difficult to provision for. Zoom's infrastructure must absorb these cliffs without degradation.

Media infrastructure complexity. Video conferencing is orders of magnitude more resource-intensive than chat or file sharing. Zoom operates a global network of media relay servers to keep latency low. A regional media server failure can degrade video quality or cause connection failures in specific geographies without triggering a full platform incident.

Client software issues. A bad update to the desktop or mobile app can cause widespread connectivity failures that look exactly like a server-side outage — same symptoms, different cause. This is why always testing the web client first is useful: if the web client works, the problem is in the installed app.

Cloud infrastructure dependencies. Zoom runs across multiple cloud providers. When the underlying cloud has an incident, Zoom can be affected even if Zoom's own code is fine.

Security incidents. DDoS attacks against Zoom's infrastructure have contributed to historical outages. Zoom has invested heavily in mitigation, but it remains a high-value target.

Why Waiting for an Email from Zoom Is Too Slow

Here is the uncomfortable truth about vendor incident communications:

When Zoom has an outage, the sequence typically goes:

1. Service degrades or fails
2. Users start reporting on social media
3. Zoom's on-call engineers investigate and confirm the issue
4. Zoom acknowledges the incident internally
5. Zoom sends email communications (if you subscribed)

Steps 1 to 4 can take anywhere from 10 to 45 minutes. Step 5 adds more delay on top. By the time an email arrives in your inbox, the incident has been live for a substantial portion of that window. Your users have already noticed, already complained, and already formed an opinion about your reliability — even if the cause is entirely outside your control.

The organizations that handle outages best are the ones who know about them before their users do. That requires monitoring from outside Zoom's own reporting system.

How Statusfield Catches Outages First

Statusfield monitors Zoom independently — not by reading Zoom's own status feed, but by watching the service externally. When something changes, Statusfield detects it and surfaces it immediately.

You can set up a Zoom monitor in Statusfield and route alerts to wherever your team already pays attention: email, Slack, Discord, Telegram, webhooks, or PagerDuty. That means when Zoom has an incident, you know about it immediately — in the channel you will actually see, not buried in an email inbox you check twice a day.

This matters especially for:

• Customer-facing teams that rely on Zoom for demos and support calls
• IT and ops teams responsible for communicating outage status across the organization
• Developers with integrations that depend on the Zoom API and webhook pipeline
• Remote-first companies where Zoom is the primary communication infrastructure

Because Statusfield monitors externally and alerts via independent channels (email, Slack, Discord, Telegram, webhooks), you receive the alert through a path that does not depend on Zoom being functional. That is the key point: you cannot rely on Zoom to tell you Zoom is down.

Frequently Asked Questions

Is Zoom down right now?

Check statusfield.com/services/zoom for real-time status. Statusfield monitors Zoom continuously and shows component-level status, so you can see whether meetings, webinars, phone, or the API are affected.

Why does Zoom say "Unable to connect" when my internet is fine?

This error usually means Zoom's client cannot reach its authentication or session servers — it is not necessarily a full platform outage. First, check whether multiple people on different networks are having the same problem. If yes, it is likely a Zoom infrastructure issue. If it is just you, check your firewall (Zoom needs TCP 443 and UDP 8801–8802), disconnect your VPN, and try the web client at zoom.us/wc as a quick diagnostic.

How long do Zoom outages usually last?

Most Zoom outages resolve within 30 minutes to two hours. Component-specific degradations (such as cloud recording processing delays) can linger longer — sometimes several hours — because the queue of affected operations has to drain even after the root cause is resolved. Major platform outages affecting meetings themselves have historically been shorter.

Does Zoom have scheduled maintenance?

Zoom does perform scheduled maintenance, typically during low-traffic windows. If you have Statusfield set up, you will receive a notification for scheduled maintenance events the same way you would for unplanned incidents — so you are never surprised.

How can I get notified when Zoom goes down?

Set up Zoom monitoring on Statusfield. Free accounts get 3 monitors and 10 alerts per month — enough to cover Zoom plus your most critical dependencies with no credit card required. Pro accounts ($29/mo) support 20 monitors; Team ($99/mo) supports 75 monitors with support for Slack, Discord, webhooks, and PagerDuty integrations.

---

Stop Reacting. Start Knowing First.

The difference between a smooth incident response and an embarrassing scramble is usually just information timing. When Zoom goes down, organizations that already have monitoring in place send a quick "we are aware and have a backup" message. Everyone else is still trying to figure out what is happening.

Monitor Zoom on Statusfield — 3 monitors, 10 alerts/month, no credit card required →

Set up takes about two minutes. When the next Zoom outage happens — and there will be a next one — you will know before your users do.

Published: June 27, 2026. Last reviewed: June 27, 2026. Check current Zoom status →