Zoom IP Ranges
Zoom publishes the address ranges its meetings, phone and web services use as a plain text file, and network teams copy it into firewall rules so that video traffic is not throttled or inspected. On 16 October 2026 the file held 50 IPv4 prefixes and no IPv6, 539,092 addresses in all. About 60% of that space is announced by Zoom's own network, AS30103; the rest belongs to the clouds and carriers Zoom rents capacity from.
- Provider
- Zoom
- Hosting network
- AS30103 plus Amazon and regional carriers
- Category
- Tech
- Headquarters
- San Jose, CA, USA
- Published IPv4 prefixes
- 50
- Registry
- Self-published list
Known IP ranges
These are the prefixes in Zoom's combined list, assets.zoom.us/docs/ipranges/Zoom.txt, as fetched on 2026-10-16. Unlike most services that publish a list, Zoom also runs its own network, AS30103, and it carries the biggest share: 12 of the 50 prefixes, 324,864 of 539,092 addresses. The rest is spread over Amazon, Microsoft, Tata Communications and four Chinese carriers, and eight prefixes were not in the routing table at all on the day they were checked. Look an address up in the list, not in WHOIS.
134.224.0.0/16
144.195.0.0/16
159.124.0.0/16
170.114.0.0/16
206.247.0.0/16
137.66.128.0/17
149.137.0.0/17
156.45.0.0/17
168.140.0.0/17
198.251.128.0/17
What does a Zoom IP mean in a privacy test?
A Zoom address is a Zoom server: a meeting relay, a phone gateway, the web client's API. It shows up in a firewall log or a traffic capture because a meeting was running, and it is never a visitor's own address, so it says nothing about whether a VPN is working. Zoom does not offer its space to anyone else's machines.
One file, seven kinds of network
Checked against the routing table prefix by prefix, the 50 entries split like this. Twelve are announced by AS30103, Zoom's own network, among them the three largest blocks Zoom holds outright: 144.195.0.0/16, 159.124.0.0/16 and 206.247.0.0/16. Twelve more are announced by Amazon - eight by its commercial networks AS16509 and AS14618, four by AS8987, Amazon's GovCloud. Two of the Amazon ones are full /16s, 134.224.0.0/16 and 170.114.0.0/16, so a quarter of the list's address space runs on AWS. Two prefixes are Microsoft's, six belong to Tata Communications in India, and ten are announced by China Unicom, China Telecom, China TieTong and China Mobile.
The last eight are the odd ones: 64.224.32.0/19, 168.140.0.0/17, 198.251.128.0/17 and five smaller blocks had no origin at all on 16 October 2026 - 79,360 addresses that Zoom lists but that nobody was announcing. A rule that admits them costs nothing today, and a lookup on one of them will return a registry record and no route.
Why the list matters more than the ASN
An allowlist built from AS30103 - the natural move if you start from Zoom's network rather than from its file - covers 60% of the addresses and misses every meeting relayed through AWS or a regional carrier. The reverse mistake is just as easy: the Amazon and Microsoft prefixes in the list are shared with every other tenant of those clouds, so traffic from one of them is not proof of Zoom. The file is the boundary Zoom itself draws, and it is the only one that matches what its clients connect to.
The file is a list of prefixes and nothing else - no product labels, no date inside it - so the only way to know it changed is to fetch it again and compare.
Related tools
Frequently asked questions
What IP ranges does Zoom use?
The 50 IPv4 prefixes in assets.zoom.us/docs/ipranges/Zoom.txt, 539,092 addresses when checked on 16 October 2026. Zoom's own AS30103 announces 12 of them; the others are announced by Amazon, Microsoft, Tata Communications and Chinese carriers.
Why does a Zoom IP appear in my logs or a privacy test?
A Zoom address is a Zoom server: a meeting relay, a phone gateway, the web client's API. It shows up in a firewall log or a traffic capture because a meeting was running, and it is never a visitor's own address, so it says nothing about whether a VPN is working. Zoom does not offer its space to anyone else's machines.
Does Zoom have its own ASN?
Yes, AS30103, registered to Zoom Video Communications. It announces about 60% of the addresses in Zoom's published list, including 144.195.0.0/16, 159.124.0.0/16 and 206.247.0.0/16. The remainder runs on networks Zoom does not own.
Is 170.114.0.0/16 a Zoom range?
It is in Zoom's published list, and on 16 October 2026 it was announced by AS14618, Amazon. Zoom lists it because its services run there; WHOIS and routing lookups will point at Amazon's network rather than at AS30103.
Should I allowlist Zoom by ASN or by the list?
By the list. AS30103 alone misses roughly 40% of the addresses Zoom says its services use, including two whole /16s on AWS, and the cloud prefixes in the list cannot be allowlisted by ASN without admitting every other tenant.