Zoom's own status page recorded a service degradation hitting Zoom Canvas, My Notes, Sheets, In App Purchases, Billing Hub and Clips starting at 22:15 UTC. It lasted 1h 22m and the fault sat on Zoom's side, not yours.
Started
22:15 UTC
Duration
Lasted 1h 22m
Source
IsDown
Next time
Zoom is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Zoom Notes, Zoom Docs, Zoom Clips
What happened?
Zoom opened an investigation at 22:15 UTC, naming a cluster of features as degraded: Zoom Canvas, My Notes, Sheets, In App Purchases, Billing Hub and Clips. That is a mix of collaboration tools and billing-adjacent features, which suggests a shared backend component rather than one product acting up on its own. No cause was given in the opening update, just confirmation that the degradation was under investigation. At 23:23 UTC, just over an hour later, Zoom marked it as resolved and moved to monitoring, saying the degradation had been successfully resolved. A further update at 23:35 UTC closed the incident outright, stating the affected services had been restored. That is three updates total across the incident's life, which is a thin record for any outage touching six named features. No root cause was published in any of the three updates, so why this happened is not on the record. No user reports were filed during this window, which is unusual for an incident spanning Canvas, Notes and billing tools together, but it may simply reflect limited exposure to the affected features at that hour. The components list on this page shows three items, Zoom Notes, Zoom Docs and Zoom Clips, which is Zoom's own grouping of what it considered impacted, not independent confirmation. Over the past 90 days Zoom has logged 62 incidents with a median duration of 49 minutes, so this one ran longer than typical. Across all time Zoom averages 10.4 incidents a month, putting this one in a crowded field of similar filings.
Learning
UptimeRobot's own 30-day checks on Zoom show 28 incidents with 26 resolved and a median duration of 31 minutes, a different rhythm from Zoom's own 62-incident, 49-minute median over 90 days. Neither number is wrong. External probes test whether Zoom's endpoints respond at all, while Zoom's status page tracks degradations inside specific features like Canvas or Billing Hub that can misbehave without taking the service down from the outside. A feature can be broken for the people trying to use My Notes or Sheets while every uptime check against Zoom's core endpoints returns green, because the check and the feature are not testing the same thing. This incident is a clean example: Zoom's page shows real, named impact across six features for over an hour, with no explanation of cause and only three brief updates. If your product depends on Zoom Canvas, Clips or any of the named features, your own monitoring of your integration would show nothing unusual while the actual fault sat upstream at Zoom. Watching your own endpoints tells you your half is fine. It does not tell you whether Zoom's half just failed. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
