CHYP.ai · ORBIT // Cloudy_Day Security Suite

Collaboration & meetings

Maintenance Zoom status

zoom.us · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

Zoom's status page shows “Maintenance” in Knowledge Base and Ticketing; the vendor is doing maintenance. User reports haven't spiked, so wide impact isn't visible yet. Amazon Web Services, a provider it may run on (inferred), also reports trouble. Coincidence, not causation.

confidence: low Vendor: minor issue · users: normal · routing: normal · upstream providers: major.

Vendor status vs. reality: Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal)

Regions mentioned: Knowledge Base, Ticketing, Zoom Phone

The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started19 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the change13 h 22 min

Evidence

  • Official page: Maintenance (“Service Under Maintenance”). evidence confidence: high
  • Vendor stage: doing maintenance on “Scheduled Maintenance – Contact Center Services: November 20, 2026”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low
  • AS30103 prefixes seen by 100% of RIPE RIS peers. evidence confidence: medium
  • Amazon Web Services reports an issue. Zoom may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low

What we don't know: what is happening inside Zoom's own systems, how many users are actually affected (reports are self-selected and unverified). Routing data shows reachability, not whether the app works.

Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “doing maintenance”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: normal · upstream providers: major. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).

Who depends on whom

Zoom may run on Amazon Web Services, Oracle Cloud (OCI) (inferred). We don't map other services that depend on Zoom. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Zoom or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; routing visibility returning to normal; and whether dependents start reporting issues.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Zoom. No blame or attack claims without an official source. Generated .

Where to next