Atlassian IP Ranges
Atlassian publishes the addresses behind Jira, Confluence, Bitbucket, Trello, Statuspage, Opsgenie and its other cloud products as one JSON file, and unlike most published lists it says what each range is for. On 16 October 2026 the file, stamped 12 October, held 110 IPv4 prefixes - 77,614 addresses once overlaps are merged - and 60 IPv6 prefixes. Atlassian Cloud runs on Amazon Web Services, and the routing table agrees: 103 of the 110 IPv4 prefixes are announced by Amazon.
- Provider
- Atlassian
- Hosting network
- AS16509 (Amazon Web Services, host)
- Category
- Tech
- Headquarters
- Sydney, Australia
- Published IPv4 prefixes
- 110
- Registry
- Self-published list
Known IP ranges
Atlassian does not announce these addresses under an ASN of its own. They are the prefixes it publishes in https://ip-ranges.atlassian.com/, as fetched on 2026-10-16; the space itself is routed by AS16509 (Amazon Web Services). The list decides whether an address belongs to Atlassian - WHOIS for any of them returns the host network.
167.89.0.0/17
168.245.0.0/17
76.223.176.0/20
104.192.136.0/21
131.162.88.0/21
52.82.172.0/22
185.166.140.0/22
131.162.88.0/23
131.162.90.0/23
13.35.248.0/24
2401:1d80:3000::/36
2401:1d80:32fd::/48
2401:1d80:32fe::/48 (IPv6)
What does an Atlassian IP mean in a privacy test?
An Atlassian address in your logs is Atlassian Cloud reaching you: a Jira webhook, a Bitbucket pipeline fetching from your server, a Confluence macro loading a page, a notification email. It is never somebody's own visible IP, and it says nothing about a VPN. What it does tell you, through the product tags in the file, is which Atlassian product made the call.
Every range is labelled
Each entry in ip-ranges.atlassian.com carries four labels: region, product, direction and perimeter. Direction is the one most people need. egress means traffic leaving Atlassian - webhooks, outbound integrations, email - and is what an inbound firewall rule on your side should admit. ingress means addresses you connect to. In this snapshot 160 entries are tagged egress and 28 ingress, and some carry both.
The product tags are broad: Jira and Confluence appear on 106 of the 170 entries, Trello, Statuspage and Halp on 99, Bitbucket and Opsgenie on 97. Narrower ones are where the file is most useful: 24 entries are tagged email, 13 rovo-crawler - the crawler behind Atlassian's Rovo AI search - 12 loom and 3 github-for-jira. The file also carries a creationDate and a syncToken, so a script can tell whether it changed without diffing it.
Amazon, SendGrid, and two outliers
Checked against the routing table, 75 IPv4 prefixes are announced by AS16509 and 28 by AS14618, both Amazon. That includes 104.192.136.0/21, the block long associated with Bitbucket: it is in Atlassian's file, but Amazon announces it. Four prefixes are Google Cloud's AS396982, and one, 52.82.172.0/22, is announced by AS135629, the operator of Amazon's Ningxia region in China.
The two largest entries are not Atlassian's at all. 167.89.0.0/17 and 168.245.0.0/17 are tagged email and announced by AS11377, SendGrid - 65,536 addresses, most of the IPv4 space in the file. They are there because Atlassian's notification mail goes out through SendGrid, and every other SendGrid sender uses them too. Admitting them in a mail filter admits far more than Atlassian; for mail, SPF and DKIM on Atlassian's sending domain are the check that actually identifies it.
Related tools
Frequently asked questions
What IP ranges does Atlassian use?
The ranges in ip-ranges.atlassian.com: 110 IPv4 prefixes, 77,614 addresses after merging overlaps, and 60 IPv6 prefixes, checked on 16 October 2026. Each one is tagged with the products that use it and whether it is egress or ingress.
Why does an Atlassian IP appear in my logs or a privacy test?
An Atlassian address in your logs is Atlassian Cloud reaching you: a Jira webhook, a Bitbucket pipeline fetching from your server, a Confluence macro loading a page, a notification email. It is never somebody's own visible IP, and it says nothing about a VPN. What it does tell you, through the product tags in the file, is which Atlassian product made the call.
Which Atlassian IPs do Jira webhooks come from?
From the entries tagged jira with direction egress. Jira appears on 106 of the 170 entries, so filter the file by product and direction rather than allowing all of it; an inbound rule needs egress ranges only.
Why does WHOIS say Amazon for an Atlassian IP?
Because Atlassian Cloud runs on AWS. 103 of the 110 IPv4 prefixes in the file are announced by Amazon's AS16509 and AS14618, including 104.192.136.0/21. The registry record names the network that routes the space, not the service using it.
Are 167.89.0.0/17 and 168.245.0.0/17 Atlassian ranges?
They are in Atlassian's file, tagged email, but they are SendGrid's: AS11377 announces both. Atlassian's notification mail is sent through SendGrid, and so is mail from SendGrid's other customers.