Atlassian cloud IP ranges
Build your allowlist, understand an IP address, or check your network coverage. All from Atlassian’s published IP ranges.
Before you start Choose ranges by product and connection purpose. Keep all regions selected, including when using data residency.
Who starts the connection?
Egress and ingress, as used in the published data, are from Atlassian’s side of the connection.
- Atlassian → your systems (egress)
- For webhooks and integrations that connect to your infrastructure, choose Atlassian → your systems.
- Your clients → Atlassian (ingress)
- For browsers and API clients accessing Atlassian, choose Your clients → Atlassian. Replies use the same connection, not the egress ranges.
Build for global reach
Data residency does not pin network traffic to one region. Keep all regions selected for your products and connection purpose.
IP ranges are part of the picture. Review the domain and third-party requirements for your products, too.
Keep your allowlist current
Ranges can change. Subscribe to change notifications through Amazon SNS to help keep your allowlist up to date.
Having connection problems? Test connectivity from your browser to Atlassian services
Restricting who can access your Atlassian site? Use your organisation’s IP addresses. Learn about product access allowlisting
Your selection
Atlassian connecting to your systems
Does your allowlist cover this selection?
Paste the IPs or CIDRs you already allow. This checks address coverage only; ports, routing, authentication, and firewall rule order are outside its scope.
Text exports the displayed CIDRs. CSV and JSON retain every matching record’s metadata.
No matching ranges
Plain-text CIDR list
Explore the published data
Where does this IP belong?
Search all products, cloud environments, and directions. Your allowlist filters do not limit this lookup.