CheckUpstream measured Zoom at 100.000% availability across 1785 independent checks (global · api). 35 incidents were recorded in the past 12 months; the most recent resolved 1 day ago after 2 hours. Status signals are polled from Zoom's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=1785 · p95 868ms (30d)
Share of our own checks against Zoom endpoints that returned Zoom's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 10 incidents · 24 of 30 days with none posted · 6h 53m of declared impact
Fewer incidents in the last 30 days than 6% of 232 tracked services.
Share of each window with no impact declared by Zoom
7d
97.926%
30d
99.042%
90d
99.562%
180d
99.781%
1y
99.892%
Downtime like this can be refundable
If you're a paying Zoom customer, outages in these windows may count against Zoom's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Zoom entitlement →Does Zoom actually matter to you?
A Zoom outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Predicted resolution
n=20~132m (p25 54m – p75 264m)
Based on 20 historical Minor incidents · currently 396m elapsed.
From 9 incidents Zoom published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Zoom takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Excluded: 1 still open.
Sep 1, 00:11 UTC · in progress · Identified
Aug 31, 04:18 UTC · resolved in 1h 43m · Resolved
Aug 27, 19:07 UTC · resolved in 13m · Resolved
Live Zoom status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/zoom)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Zoom is currently Degraded. CheckUpstream tracks Zoom in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Zoom's last resolved incident started 1 day ago and lasted 1h 43m (degraded performance).
Looking for the live "is Zoom down" view? See the Zoom Live status page.
Aug 27, 19:02 UTC · resolved in 3h 17m · Resolved
Aug 24, 08:56 UTC · resolved in 9m · Resolved
Jul 31, 12:09 UTC · resolved in 3h 5m · Resolved
Jul 27, 09:08 UTC · resolved in 8h 31m · Resolved
Jul 23, 15:53 UTC · resolved in 2h 41m · Resolved
Jul 21, 18:25 UTC · resolved in 54m · Resolved
Jul 18, 14:17 UTC · resolved in 5h 42m · Resolved
Jul 18, 08:03 UTC · resolved in 1h 16m · Resolved
Jul 10, 16:18 UTC · resolved in 3h 2m · Resolved
Jul 10, 06:03 UTC · resolved in 36m · Resolved
Jul 8, 15:02 UTC · resolved in 1h 8m · Resolved
Jul 7, 10:15 UTC · resolved in 21h 5m · Resolved
Zoom's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Zoom endpoints. It is the share of checks that returned the expected response, not a figure taken from Zoom's status page.
Sign up to CheckUpstream and add Zoom to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Zoom's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.