Question About Zoom Webhook Source IPs and Service Infrastructure Locations

API Endpoint(s) and/or Zoom API Event(s)

  • Zoom Meeting Webhooks

  • Meeting-related webhook events

Description

We are currently using Zoom Meeting Webhooks and have observed webhook requests originating from an IP address geolocated to the United States.

According to the IP lookup information from ipinfo.io, the source IP has the following details:

We would like to clarify the following points:

  1. Are Meeting Webhook requests expected to originate from the United States, or can they also originate from other countries or regions?

  2. Besides Meeting Webhooks, are there any other Zoom features or services that may initiate requests to our systems, such as callbacks, event notifications, or other server-to-server communications?

  3. Where are the relevant Zoom service infrastructure and data centers located? Is there any official documentation listing the countries or regions from which requests may originate?

  4. If we restrict access to our systems based on source IP addresses or geographic locations for security reasons, which official IP ranges or documentation should we use to ensure that legitimate Zoom services are not blocked?

Our goal is to understand the potential source locations of requests from Zoom so that we can configure our access restrictions appropriately without disrupting Zoom functionality.

Error?

No error occurred. This is a question about the source IP addresses and geographic locations used by Zoom services.

How To Reproduce

  1. Request URL / Headers / Body: We observed incoming requests to our webhook endpoint from an IP address with the following information:

    • Source IP: 170.114.6.88

    • Hostname: 172-114-6-88.zoom.us

    • IP Range: 170.114.0.0/20

    • Location reported by ipinfo.io: Reston, Virginia, United States

  2. Authentication method or app type: Zoom Meeting Webhooks.

  3. Any errors: No errors. We are investigating the source IP addresses and geographic locations of requests from Zoom for security and access-control purposes.

hi @Dungvl76 ,

I would suggest you ignore the ip address of webhooks.
Zoom does not suggest where they come from.
Instad is passes a security key for you to confirm it is legitimate and you should test for this from all webhooks.
Look at the access page on your marketplace entry

All the best

John
Zoom MVP Developer
Not Zoom Employee

@expertswho
Thank you for your response.

Our concern is that we are planning to restrict access to our system by country using AWS WAF. If Zoom Meeting Webhooks originate from countries outside our allowed list, legitimate webhook requests may be blocked.

We understand that webhook authenticity should be verified using the Secret Token. However, we would also like to understand whether Zoom Meeting Webhooks can originate from multiple countries or regions.

Could you clarify whether there is any official documentation about the geographic locations from which Zoom Webhook requests may originate?

hi @Dungvl76 ,

I am not aware of any documentation for zoom webhooks.

There are ranges of ip addresses published for the data centres that are supporting Zoom and this is the link below. I have never seen speicfic webhook references.

I think this is a legitimate request, but Zoom may not be setup to deliver the address ranges.

John

Zoom’s webhook documentation doesn’t specify that Meeting Webhooks originate from specific countries or regions. Zoom operates infrastructure across multiple regions, including North America, Europe, Asia, and Australia. The official data center location list identifies these locations. However, data center region settings apply to meeting and webinar content processing, not necessarily webhook delivery. These documents don’t establish which countries webhook requests can originate from.

If you’re exploring alternative meeting integrations, Recall.ai’s Meeting Bot API can help capture meeting data across supported platforms.

Hopefully, it will be resolved! :+1::black_large_square::roller_coaster: