Atlassian cloud will start using new IP address ranges as we expand our cloud infrastructure
- Announced
- Tags
- rovo-mcp, forge-core-platform, rest-jira-cloud-platform, rest-jsm-cloud, rest-jsw-cloud, rest-cloud-admin, rest-confluence-cloud, rest-opsgenie, graphql-compass, graphql-confluence, graphql-jira
- Severity
- info, set by
reef/atlassian-rule-v2 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3519
What's changing From January 1, 2027, Atlassian cloud will add new IP address ranges as we expand our cloud infrastructure.
The new ranges are in addition to our existing ones.
The new ranges are:
- New range:
131.162.88.0/21- Requests to Atlassian (browsers and your clients calling Atlassian APIs):
131.162.88.0/23 - Requests from Atlassian (webhooks, Connect lifecycle calls, and other requests from Atlassian to your app):
131.162.90.0/23
- Requests to Atlassian (browsers and your clients calling Atlassian APIs):
What you need to do If your app, remote backend, or integration allowlists Atlassian IP addresses, you must add these ranges before January 1, 2027, to avoid service interruptions.
These ranges are already included in our official IP range list (viewer tool). If you automate your allowlist updates from this file, no further action is required. For more details, see our documentation on IP addresses and domains for Atlassian cloud apps.
The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.