Jira Cloud Webhook Source IP Addresses for Firewall Allowlisting

Question

Hello Atlassian Support,

We have configured a Jira Cloud webhook that sends events to a callback endpoint hosted within our environment.

The webhook configuration appears to be correct, and testing on our side indicates that the callback endpoint is reachable internally. However, we are not receiving any requests from Jira Cloud, including initial webhook requests.

After investigating, we determined that our callback URL is hosted behind our corporate network and is not currently accessible from external sources. Since Jira Cloud webhooks originate from Atlassian infrastructure, our Network team needs to allowlist the appropriate Atlassian source IP addresses.

Could you please confirm which IP addresses or IP ranges should be allowlisted for Jira Cloud webhooks?

We found documentation that lists both:

* Atlassian summary IPv4 ranges (preferred)
* Individual IPv4 ranges used for outgoing connections

Can you confirm which list should be used specifically for Jira Cloud webhook traffic and firewall allowlisting?

Thank you for your assistance.

Best regards,
Abdul Gafoor

Rohit Utukuri · Answer

Hi @Abdul Gafoor Shaik ,

Forums are user supported and members of the forums do not have access to site information.

I would try to find out the NATed IP Address of the End point you are trying to reach within your network and configure the webhook using the NATed IP Address in Jira cloud (in case you haven't done so already).

From a quick glance, CIDR range under "Atlassian summary IPv4" include the CIDR range listed under "Individual IPv4 ranges".

In order to reach Atlassian support, you can submit a ticket using the URL: https://support.atlassian.com

Martin Runge · Answer

Hi @Abdul Gafoor Shaik

Welcome to the Atlassian Community!

I would recommend using the Individual IPv4 ranges used for outgoing connections list because Jira Cloud webhooks are outbound traffic sent from Atlassian to your external network. While the summary ranges cover everything including inbound user traffic, the outgoing list is narrower and more secure for a firewall.

These IP ranges are shared globally across Atlassian infrastructure and are not specific to individual geolocations or regional data residency zones. If your network uses geolocation filtering, I would allowlist these specific subnets regardless of their detected region to ensure webhook delivery does not get blocked.