Checked 4 minutes ago
Nothing wrong in the last 48 hours.
Last problem before that: 4 days ago, lasting 16h 39m.
This longer record is here so the 48-hour picture above can mean something — without it we could tell you a problem happened, but not whether that is normal for Zoom.
Something was impaired on 22.84% of our checks over that window. That is how often Zoom was reporting a problem somewhere, which is not the same as how often it was unreachable. The longest outage we have on record ran 347h 0m.
The last 30 days of Zoom, one row each.
| Day | Clear | Up | Checks | Started | Longest ended |
|---|---|---|---|---|---|
| 2026-11-01 so far today | 100% | 100% | 185 | none | — |
| 2026-10-31 | 100% | 100% | 287 | none | — |
| 2026-10-30 | 100% | 100% | 287 | none | — |
| 2026-10-29 | 70.63% | 100% | 286 | none | 16h 39m |
| 2026-10-28 | 60.63% | 100% | 287 | 1 | — |
| 2026-10-27 | 100% | 100% | 287 | none | — |
| 2026-10-26 | 100% | 100% | 287 | none | — |
| 2026-10-25 | 100% | 100% | 287 | none | — |
| 2026-10-24 | 100% | 100% | 287 | none | — |
| 2026-10-23 | 63.41% | 100% | 287 | 1 | 12h 49m |
| 2026-10-22 | 80.42% | 100% | 286 | 1 | — |
| 2026-10-21 | 93.03% | 100% | 287 | 1 | 1h 42m |
| 2026-10-20 | 94.77% | 100% | 287 | none | 11h 48m |
| 2026-10-19 | 56.79% | 100% | 287 | 1 | — |
| 2026-10-18 | 100% | 100% | 287 | none | — |
| 2026-10-17 | 96.88% | 100% | 288 | 1 | 50 min |
| 2026-10-16 | 100% | 100% | 287 | none | — |
| 2026-10-15 | 100% | 100% | 287 | none | — |
| 2026-10-14 | 18.12% | 100% | 287 | 1 | 19h 40m |
| 2026-10-13 | 100% | 100% | 281 | none | — |
| 2026-10-12 | 97.21% | 100% | 287 | none | 2h 16m |
| 2026-10-11 | 93.73% | 100% | 287 | 1 | — |
| 2026-10-10 | 86.76% | 100% | 287 | 1 | 347h 0m |
| 2026-10-09 | 49.83% | 100% | 287 | 1 | 331h 50m |
| 2026-10-08 | 50.17% | 100% | 287 | 1 | 308h 55m |
| 2026-10-07 | 45.99% | 100% | 287 | 1 | 12h 57m |
| 2026-10-06 | 49.83% | 100% | 287 | 1 | 259h 50m |
| 2026-10-05 | 44.95% | 100% | 287 | 3 | 235h 50m |
| 2026-10-04 | 47.04% | 100% | 287 | 2 | 211h 45m |
| 2026-10-03 | 41.81% | 100% | 287 | 2 | 187h 50m |
Clear is the share of checks that found nothing wrong at all; Up is the share that found Zoom actually reachable — a vendor reporting one impaired component scores zero on the first and a hundred on the second, and both are true. Started counts outages that began that day and Longest ended the longest that finished on it, so a problem running across midnight is counted once, on the day it began, and measured on the day it stopped.
Rows recorded before 8 August 2026 do not carry a check count — the figure was kept and the denominator was not — so their percentages are shown without one rather than with a number borrowed from somewhere else. Rows before 9 August 2026 have no Up figure either: until then we recorded only whether something was wrong, not whether it was down, and the two are different questions.
| Started | Lasted | Severity | What happened |
|---|---|---|---|
| 2026-10-28 14:31 UTC | 16h 39m | having problems | Service Degradation Affecting the Evaluations Acknowledge Button in Zoom Quality Management in the US Region |
| 2026-10-23 16:01 UTC | 49 min | having problems | Service Degradation Affecting Multiple Zoom Services. |
| 2026-10-22 19:16 UTC | 12h 49m | having problems | Service Degradation Affecting Zoom Meetings Services in the US. |
| 2026-10-21 14:43 UTC | 1h 42m | having problems | Service Degradation Affecting Zoom Learning Webpage |
| 2026-10-19 13:32 UTC | 11h 48m | having problems | Service Degradation Affecting Zoom Website in UK region. |
| 2026-10-17 06:10 UTC | 50 min | having problems | Service Degradation Affecting Zoom Chat Compose and SMS Summarisation with AI Companion |
| 2026-10-14 00:20 UTC | 19h 40m | having problems | Service Degradation Affecting Zoom Clips |
| 2026-10-11 22:29 UTC | 2h 16m | having problems | Service Degradation Affecting Zoom Scheduler. |
| 2026-09-25 17:45 UTC | 347h 0m | having problems | Service Degradation Affecting Customer Using Polycom Devices Going Offline |
| 2026-09-25 17:45 UTC | 331h 50m | having problems | Service Degradation Affecting Customer Using Polycom Devices Going Offline |
| 2026-09-25 17:45 UTC | 308h 55m | having problems | Service Degradation Affecting Customer Using Polycom Devices Going Offline |
| 2026-10-07 02:08 UTC | 12h 57m | having problems | Service Degradation Affecting Zoom Slides Generation in US Region |
| 2026-09-25 17:45 UTC | 259h 50m | having problems | Service Degradation Affecting Customer Using Polycom Devices Going Offline |
| 2026-10-05 21:57 UTC | 28 min | having problems | Service Degradation Affecting ZoomMate |
| 2026-09-25 17:45 UTC | 235h 50m | having problems | Service Degradation Affecting Customer Using Polycom Devices Going Offline |
| 2026-10-04 23:19 UTC | 1h 36m | having problems | Service Degradation Affecting Zoom Rooms Management and Workspaces Management in SA01. |
| 2026-10-04 23:19 UTC | 1h 26m | having problems | Service Degradation Affecting Zoom Rooms Management and Workspaces Management in SA01. |
| 2026-09-25 17:45 UTC | 211h 45m | having problems | Service Degradation Affecting Customer Using Polycom Devices Going Offline |
| 2026-10-03 16:49 UTC | 1h 56m | having problems | Service degradation affecting Developer Documentation Website |
| 2026-09-25 17:45 UTC | 187h 50m | having problems | Service Degradation Affecting Customer Using Polycom Devices Going Offline |
Status pages report the vendor's view of their own service, and they lag real
outages — often by many minutes, sometimes by hours, because a human usually has to
confirm before anything is posted. They also can't see the two things most likely to
be wrong at your end.
The first is your own connection under load. A line that idles at 20 ms can
jump to 300 ms the moment something starts uploading, which drops you from sessions
and looks exactly like a server fault. Your plan speed says nothing about this; it's
called bufferbloat and almost nobody measures it.
The second is where everyone else in your group is. A service can be healthy in your
region and unwell in theirs, and if one person is hosting, their problem is everyone's
problem.
Zoom being fine where you are does not mean it is fine for everyone in your group. The live dashboard resolves status against each person's own region, and will tell you which of your friends is in an affected area — plus who has the connection to host, which is usually a different question from who has the fastest plan.
Worth a look when more than one thing feels broken at once: if several are genuinely down together, the fault is usually something they share rather than anything at your end. We are not claiming these particular services fail together — the live dashboard says when they actually do.