CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · NetWeather event

Zoom: Service Degradation for a subset of users affecting outbound Zoom Phone calls in Australia.

Zoom resolved M2.2 Tremor since Nov 20, 12:30 PM PT

Zoom reported “Zoom: Service Degradation for a subset of users affecting outbound Zoom Phone calls in Australia.” starting Nov 20, 12:30 PM PT.

  • 14mDurationstart → resolved
  • 1Systems namedfrom the source
  • 1Places named1 on the map
  • 0Dependentscatalogued, inferred
  • 1/4Evidence kindsindependent families
  • 2Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Nov 20, 12 PMNov 20, 12 PMNov 20, 12 PMNov 20, 12 PMNov 20, 12 PMNov 20, 1 PM Official statusNov 20, 12:32 PM PT · Zoom: Service Degradation for a subset of users affecting outbound Zoom Phone calls in Australia.Nov 20, 12:44 PM PT · Zoom: Service Degradation for a subset of users affecting outbound Zoom Phone calls in Australia.Network & routingnothing in this windowEarly signalsnothing in this windowNews & chatternothing in this windowCoincidence (KEV)nothing in this window ▼ startresolved ▼

Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.

What happened

Zoom reported “Zoom: Service Degradation for a subset of users affecting outbound Zoom Phone calls in Australia.” starting Nov 20, 12:30 PM PT.

What broke

Zoom Phone.

Who was hit

Hit: 1 named location (Australia). No catalogued services depend on Zoom.

How it recovered

Resolved after 14m.

2Blast radius

Amazon Web Services · OperationalAmazon Web Serv…Oracle Cloud (OCI) · no official feed / staleOracle Cloud (O…Zoom0 dependents

Center: Zoom. Inner ring: what it runs on. Outer ring: catalogued services that run on it, coloured by their official status right now. Dependencies are inferred from public information.

3Blast map

Australia · monitoring · Calling (Inbound/Outbound)…
  1. Australia

Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Config propagation“maintenance”
  • Dependency cascade“subset of”
  • Retry amplificationno sign
  • Control-plane couplingno sign
  • Capacity exhaustionno sign

Automated keyword read of the public updates. A hypothesis to test, never a root cause.

5Evidence matrix

Official statusOfficial status · Nov 20, 6:30 AM PT: 0 itemsOfficial status · Nov 20, 6:46 AM PT: 0 itemsOfficial status · Nov 20, 7:01 AM PT: 0 itemsOfficial status · Nov 20, 7:17 AM PT: 0 itemsOfficial status · Nov 20, 7:32 AM PT: 0 itemsOfficial status · Nov 20, 7:48 AM PT: 0 itemsOfficial status · Nov 20, 8:04 AM PT: 0 itemsOfficial status · Nov 20, 8:19 AM PT: 0 itemsOfficial status · Nov 20, 8:35 AM PT: 0 itemsOfficial status · Nov 20, 8:50 AM PT: 0 itemsOfficial status · Nov 20, 9:06 AM PT: 0 itemsOfficial status · Nov 20, 9:21 AM PT: 0 itemsOfficial status · Nov 20, 9:37 AM PT: 0 itemsOfficial status · Nov 20, 9:53 AM PT: 0 itemsOfficial status · Nov 20, 10:08 AM PT: 0 itemsOfficial status · Nov 20, 10:24 AM PT: 0 itemsOfficial status · Nov 20, 10:39 AM PT: 0 itemsOfficial status · Nov 20, 10:55 AM PT: 0 itemsOfficial status · Nov 20, 11:11 AM PT: 0 itemsOfficial status · Nov 20, 11:26 AM PT: 0 itemsOfficial status · Nov 20, 11:42 AM PT: 0 itemsOfficial status · Nov 20, 11:57 AM PT: 0 itemsOfficial status · Nov 20, 12:13 PM PT: 0 itemsOfficial status · Nov 20, 12:28 PM PT: 1 itemNetwork & routingNetwork & routing · Nov 20, 6:30 AM PT: 0 itemsNetwork & routing · Nov 20, 6:46 AM PT: 0 itemsNetwork & routing · Nov 20, 7:01 AM PT: 0 itemsNetwork & routing · Nov 20, 7:17 AM PT: 0 itemsNetwork & routing · Nov 20, 7:32 AM PT: 0 itemsNetwork & routing · Nov 20, 7:48 AM PT: 0 itemsNetwork & routing · Nov 20, 8:04 AM PT: 0 itemsNetwork & routing · Nov 20, 8:19 AM PT: 0 itemsNetwork & routing · Nov 20, 8:35 AM PT: 0 itemsNetwork & routing · Nov 20, 8:50 AM PT: 0 itemsNetwork & routing · Nov 20, 9:06 AM PT: 0 itemsNetwork & routing · Nov 20, 9:21 AM PT: 0 itemsNetwork & routing · Nov 20, 9:37 AM PT: 0 itemsNetwork & routing · Nov 20, 9:53 AM PT: 0 itemsNetwork & routing · Nov 20, 10:08 AM PT: 0 itemsNetwork & routing · Nov 20, 10:24 AM PT: 0 itemsNetwork & routing · Nov 20, 10:39 AM PT: 0 itemsNetwork & routing · Nov 20, 10:55 AM PT: 0 itemsNetwork & routing · Nov 20, 11:11 AM PT: 0 itemsNetwork & routing · Nov 20, 11:26 AM PT: 0 itemsNetwork & routing · Nov 20, 11:42 AM PT: 0 itemsNetwork & routing · Nov 20, 11:57 AM PT: 0 itemsNetwork & routing · Nov 20, 12:13 PM PT: 0 itemsNetwork & routing · Nov 20, 12:28 PM PT: 0 itemsEarly signalsEarly signals · Nov 20, 6:30 AM PT: 0 itemsEarly signals · Nov 20, 6:46 AM PT: 0 itemsEarly signals · Nov 20, 7:01 AM PT: 0 itemsEarly signals · Nov 20, 7:17 AM PT: 0 itemsEarly signals · Nov 20, 7:32 AM PT: 0 itemsEarly signals · Nov 20, 7:48 AM PT: 0 itemsEarly signals · Nov 20, 8:04 AM PT: 0 itemsEarly signals · Nov 20, 8:19 AM PT: 0 itemsEarly signals · Nov 20, 8:35 AM PT: 0 itemsEarly signals · Nov 20, 8:50 AM PT: 0 itemsEarly signals · Nov 20, 9:06 AM PT: 0 itemsEarly signals · Nov 20, 9:21 AM PT: 0 itemsEarly signals · Nov 20, 9:37 AM PT: 0 itemsEarly signals · Nov 20, 9:53 AM PT: 0 itemsEarly signals · Nov 20, 10:08 AM PT: 0 itemsEarly signals · Nov 20, 10:24 AM PT: 0 itemsEarly signals · Nov 20, 10:39 AM PT: 0 itemsEarly signals · Nov 20, 10:55 AM PT: 0 itemsEarly signals · Nov 20, 11:11 AM PT: 0 itemsEarly signals · Nov 20, 11:26 AM PT: 0 itemsEarly signals · Nov 20, 11:42 AM PT: 0 itemsEarly signals · Nov 20, 11:57 AM PT: 0 itemsEarly signals · Nov 20, 12:13 PM PT: 0 itemsEarly signals · Nov 20, 12:28 PM PT: 0 itemsNews & chatterNews & chatter · Nov 20, 6:30 AM PT: 0 itemsNews & chatter · Nov 20, 6:46 AM PT: 0 itemsNews & chatter · Nov 20, 7:01 AM PT: 0 itemsNews & chatter · Nov 20, 7:17 AM PT: 0 itemsNews & chatter · Nov 20, 7:32 AM PT: 0 itemsNews & chatter · Nov 20, 7:48 AM PT: 0 itemsNews & chatter · Nov 20, 8:04 AM PT: 0 itemsNews & chatter · Nov 20, 8:19 AM PT: 0 itemsNews & chatter · Nov 20, 8:35 AM PT: 0 itemsNews & chatter · Nov 20, 8:50 AM PT: 0 itemsNews & chatter · Nov 20, 9:06 AM PT: 0 itemsNews & chatter · Nov 20, 9:21 AM PT: 0 itemsNews & chatter · Nov 20, 9:37 AM PT: 0 itemsNews & chatter · Nov 20, 9:53 AM PT: 0 itemsNews & chatter · Nov 20, 10:08 AM PT: 0 itemsNews & chatter · Nov 20, 10:24 AM PT: 0 itemsNews & chatter · Nov 20, 10:39 AM PT: 0 itemsNews & chatter · Nov 20, 10:55 AM PT: 0 itemsNews & chatter · Nov 20, 11:11 AM PT: 0 itemsNews & chatter · Nov 20, 11:26 AM PT: 0 itemsNews & chatter · Nov 20, 11:42 AM PT: 0 itemsNews & chatter · Nov 20, 11:57 AM PT: 0 itemsNews & chatter · Nov 20, 12:13 PM PT: 0 itemsNews & chatter · Nov 20, 12:28 PM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 20, 6:30 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 6:46 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 7:01 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 7:17 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 7:32 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 7:48 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 8:04 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 8:19 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 8:35 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 8:50 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 9:06 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 9:21 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 9:37 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 9:53 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 10:08 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 10:24 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 10:39 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 10:55 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 11:11 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 11:26 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 11:42 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 11:57 AM PT: 0 itemsCoincidence (KEV) · Nov 20, 12:13 PM PT: 0 itemsCoincidence (KEV) · Nov 20, 12:28 PM PT: 0 itemsNov 20, 6:30 AM PTNov 20, 12:44 PM PT

Correlation is not causation

Five independent lanes across the window. Brighter = stronger item. Items landing in the same column are coincidence unless the provider says otherwise.

6Four clocks

Source says it beganNov 20, 12:30 PM PTORBIT first saw itNov 20, 12:32 PM PTLatest source updateNov 20, 12:30 PM PTLast checkedNov 21, 5:20 AM PT

Detection gap: 2m between the source's start time and ORBIT's first sighting.

Public status always trails reality. These are the times each public record states, in PT.

7Historical twins

Nearest matches in the Control-Plane Meltdown Index (1.0.0, vendor-sourced, tracked since 2024 with earlier landmark cases). Similarity = provider + failure modes + scope.

Cloudy_Day take

  • Small, contained and documented. This is what a well-run status page looks like. Note it, don't panic.

Automated take: rules written by Cloudy_Day, applied to public data. Not a human verdict on this incident, not a root-cause finding, not affiliated with Zoom.

8Dissection capsule

Share card for this dissection

Everything above as one shareable, citable capsule with a content hash.

JSON capsuleMarkdownShare card (SVG)

Open Zoom in the War Room →NetWeather evidence page →Status page →

Embed this card
<a href="https://www.chyp.ai/dissect/event-nw-2e737bc03fa2d404/"><img src="https://www.chyp.ai/dissect/event-nw-2e737bc03fa2d404/card.svg" alt="Zoom: Service Degradation for a subset of users affecting o… · ORBIT Outage Dissector" width="600"></a>

Sources & limits

  • Provider-stated: this repeats what the vendor's public status page said. It is not an independent root-cause verification.
  • Temporal overlap with other events is coincidence, not causation, unless a provider states a causal link.
  • NetWeather is independent research, not an official status source. Confirm with the provider.
  • Correlation is not causation. Lanes are kept apart so overlap never reads as cause.
  • ORBIT is passive: it never contacts the provider or probes its systems. Independent researcher, not affiliated.