---
schema_version: "1"
id: 6b18045f229c35aa484446e2d744d9f39c5b7b173df3b45c7bbee627d4792e3e
title: Get Ready for IPv6
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_general_ipv6_ready.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_general_ipv6_ready.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 29f35d94041c365d8354083ee3a9c686bd82b3a045cfd2fc55c0fb339122f3c5
description: To help mitigate the IP address scarcity of IPv4, Salesforce is working behind the scenes to support IPv6. If you use an IP allowlist to restrict network traffic or you restrict access to Salesforce via IP address, consider implementing a preferred alternative. Otherwise, prepare to update your allowlists to include IPv6 addresses.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Get Ready for IPv6

To help mitigate the IP address scarcity of IPv4, Salesforce is working behind the scenes to support IPv6. If you use an IP allowlist to restrict network traffic or you restrict access to Salesforce via IP address, consider implementing a preferred alternative. Otherwise, prepare to update your allowlists to include IPv6 addresses.

**Where:** This change applies to Lightning Experience and Salesforce Classic in all editions.

**When:** Today, IPv6 is supported only for the Salesforce Content Delivery Network (CDN) for Experience Cloud sites. With full IPv6 support, users and integrations can connect to Salesforce via an IPv6 address. We’re announcing this upcoming change to give you time to update your allowlists.

There’s no specific target date for full IPv6 support. Salesforce plans to roll out IPv6 support in stages, starting with Salesforce Government Cloud orgs. Government Cloud customers, check the [IP Addresses to Allow for Government Cloud Plus](https://help.salesforce.com/s/articleView?id=000386297&type=1&language=en_US) Knowledge Article for that information in early 2026.

Check future release notes for the specific timing for each stage. For other stages, Salesforce plans to provide the IPv6 addresses to allow at least 2 months before IPv6 is fully supported in the affected orgs.

**Why:** IP address restrictions can exist both in and outside Salesforce.

In Salesforce, an IP address allowlist range can include either IPv4 or IPv6 addresses but not both types. When Salesforce supports IPv6 for your org, IPv4 allowlists remain active, and users can only log in via an IPv6 address that their profile allows. To make sure that your users can continue to access Salesforce after this change, for each profile with a login IP range, add one or more login IP ranges with those users’ IPv6 addresses.

Outside Salesforce, your company can restrict network traffic. An example is an allowlist that determines which IP addresses your users can access or which IP addresses can access your network. If those allowlists don’t include Salesforce IPv6 addresses when Salesforce supports IPv6, users can experience disruption, and integrations can fail.

**How:** If you use IP allowlists, consider a [preferred alternative](https://help.salesforce.com/s/articleView?id=000394078&type=1&language=en_US), such as domain allowlists or Service Name Indication (SNI).

If you continue to restrict access to Salesforce by IP address, update your allowlists in Salesforce. There’s no correlation between an IPv6 address and an IPv4 address. To determine your users’ IPv6 addresses, work with your network team.

If you continue to restrict network traffic via IP address, plan to update those allowlists to include Salesforce IPv6 addresses when those addresses are available.

#### See Also

- [_Salesforce Help_: Set Trusted IP Ranges for Your Organization](https://help.salesforce.com/s/articleView?id=xcloud.security_networkaccess.htm&type=5&language=en_US)
- [_Salesforce Help_: Restrict Login IP Addresses in Profiles](https://help.salesforce.com/s/articleView?id=platform.login_ip_ranges.htm&type=5&language=en_US)