On this page
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?
Start with the latest reported state: check live Zoom status on Statusfield →
Statusfield polls Zoom's published status source and displays the latest observed component state. Check the observation time and the affected product. A status aggregator using that source cannot establish an unreported outage before the provider publishes it; use your own connection tests alongside it.
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:
- 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.
- Disconnect your VPN if you use one. VPNs frequently block the UDP ports Zoom needs for media.
- 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.
- 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:
- 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. - 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.
- 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
- 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.
- 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.
- 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 for reported Zoom issues, then compare them with local diagnostics. An operational report does not rule out an unreported problem.
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:
- Service degrades or fails
- Users start reporting on social media
- Zoom's on-call engineers investigate and confirm the issue
- Zoom acknowledges the incident internally
- 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.
Give your team a place to check reported incidents and a tested backup meeting option. Configure alerts before an incident so you know where updates should arrive.
Follow Zoom updates with your team
Statusfield follows reported Zoom status and routes detected changes to your configured channels. It depends on the vendor source for that context; it does not independently test every Zoom meeting or account.
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. Choose the components and events that matter to your team, then test delivery. Notification timing depends on Zoom reporting the change, Statusfield processing it and your configured destination receiving it.
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
Choose a destination outside Zoom, such as email or a supported chat channel, for reported Zoom status changes. Check plan availability and test the destination so your team knows where to look.
Frequently Asked Questions
Is Zoom down right now?
Check statusfield.com/services/zoom for recorded Zoom status and supported components. Review observation timestamps and reported incident details alongside your meeting or API symptoms; provider reports do not test your own connection.
Why does Zoom say "Unable to connect" when my internet is fine?
Compare the issue across devices and networks, then review Zoom’s reported status and your client diagnostics. Connection failures can involve local network controls, the client or a provider issue. Shared symptoms are useful evidence, but do not by themselves prove a platform outage.
How long do Zoom outages usually last?
Recovery time depends on the affected service and incident. Follow Zoom’s published updates for the specific issue rather than relying on a typical duration. After reported recovery, verify that your own meetings or integrations work before closing the incident.
Does Zoom have scheduled maintenance?
Check Zoom’s official status communications for published maintenance notices. Statusfield can display available vendor maintenance context, but notification coverage depends on supported events and your configuration. Do not assume every future maintenance window will generate an alert.
How can I get notified when Zoom goes down?
Set up supported Zoom components on Statusfield and configure destinations for detected status changes. Eligible first-time customers can start a trial without a credit card. See current plans for monitor limits and channels, and test your destination before relying on it.
Prepare your team for the next incident
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 — Free trial, no credit card required →
Select the supported Zoom components your team uses, configure an alert destination and test it before relying on the setup.
Published: June 27, 2026. Last reviewed: June 27, 2026. Check current Zoom status →
Keep your vendors in view.
Choose from 7,000+ services, follow the components you use, and configure alerts for your team.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.