Is Zoom down right now?

While you wait: the Zoom incident checklist

1. Scope which service is hurt. Meetings, Phone, webinars, sign-in/SSO and the web portal are separate components. 'Zoom is down' is rarely all of Zoom — the response differs if it's auth versus media.
2. Move the war room first. If your incident bridge runs on Zoom, relocate it before debugging anything else — Meet, Teams, Slack huddle, whatever was pre-agreed. Post the new link in the incident channel and pin it.
3. Try the alternate joins. Joining from the browser instead of the desktop client, or via PSTN dial-in, rides partially different paths and sometimes works during partial outages. Worth sixty seconds before writing meetings off.
4. Check Zoom Phone dependencies. If support lines or on-call callbacks run on Zoom Phone, activate forwarding to cell phones or your backup provider now, not after the queue fills.
5. Communicate off-platform. One company-wide note in chat or email: what's down, the fallback bridge, where updates land. It stops thirty parallel 'is Zoom down?' threads.

What breaks when Zoom has issues

Zoom outages hit coordination more than production: standing meetings and customer calls drop, and — the SRE-specific trap — incident bridges die exactly when you need them most, which is why the pre-agreed fallback bridge matters more than anything technical. Zoom Phone takes support lines and callback flows with it; webinars and scheduled demos fail visibly to customers. In-progress meetings sometimes survive while new joins fail, so don't hang up a working bridge to 're-test' it.