Add Static Outbound IP Addresses

Enabling this feature can result in slower workspace startup times, because workspaces with static IPs are configured with custom network routing.

Warning

Agentforce Vibes IDE workspaces can route outbound traffic through a fixed set of static IP addresses. IP allowlisting is an opt-in feature that Salesforce needs to enable for your organization. When active, all outbound traffic from newly created workspaces exits through these IPs.

If your organization enforces IP-based access restrictions, such as login IP ranges, add these IPs to your allowlist.

Important

Shared Outbound IP Considerations

All Agentforce Vibes IDE workspaces share the static outbound IP addresses and don’t uniquely identify a specific customer, organization, or workspace.

Global IP Sharing: Adding these addresses to an allowlist permits network-level connection requests from all Agentforce Vibes IDE workspaces, including those outside your organization.
App-Level Protection Required: IP allowlisting controls network connectivity only—it doesn’t grant data access. Continue to protect your endpoints with appropriate app-level authentication and valid Salesforce authorization checks.

Add IP Ranges for an Org

Before you add other IPs, you must first add the outbound IP of your IDE. Use curl ifconfig.me to retrieve the local IP and add it to the allowlist, as explained in these steps.

You can add an IP range for a user profile by:

Using the setup option.
Editing the .profile-meta.xml file for a profile.

Use the Setup Option

Click .
In the Quick Find box, enter Agentforce Vibes IDE.
Verify that the Enable Static IPs option is enabled.
In the Quick Find box, enter Profiles, and select Profiles under Users.
From the list of user profiles, select an Agentforce-Vibe-IDE-user profile. For example, System Administrator.
Scroll down to the Login IP Ranges option and click New.
To add an IP range, enter the same IP address in the Start IP Address and End IP Address boxes.
Enter a description. For example, AFV IDE Static IP Address.
Save your changes. To add more IP addresses, repeat the process.

Edit the .profile-meta.xml File

You can manage login IP ranges as profile metadata, which is useful for automation or for CI (Continuous Integration) and CD (Continuous Deployment) pipelines. Add these IP ranges to your .profile-meta.xml file as given in this example.

1<Profile xmlns="http://soap.sforce.com/2006/04/metadata">
2    <loginIpRanges>
3        <description>AFV IDE Static IP Address</description>
4        <startAddress>3.97.47.150</startAddress>
5        <endAddress>3.97.47.150</endAddress>
6    </loginIpRanges>
7    <loginIpRanges>
8        <description>AFV IDE Static IP Address</description>
9        <startAddress>3.96.231.152</startAddress>
10        <endAddress>3.96.231.152</endAddress>
11    </loginIpRanges>
12    <loginIpRanges>
13        <description>AFV IDE Static IP Address</description>
14        <startAddress>63.176.81.41</startAddress>
15        <endAddress>63.176.81.41</endAddress>
16    </loginIpRanges>
17    <loginIpRanges>
18        <description>AFV IDE Static IP Address</description>
19        <startAddress>35.156.227.229</startAddress>
20        <endAddress>35.156.227.229</endAddress>
21    </loginIpRanges>
22    <loginIpRanges>
23        <description>AFV IDE Static IP Address</description>
24        <startAddress>52.214.167.100</startAddress>
25        <endAddress>52.214.167.100</endAddress>
26    </loginIpRanges>
27    <loginIpRanges>
28        <description>AFV IDE Static IP Address</description>
29        <startAddress>34.255.93.118</startAddress>
30        <endAddress>34.255.93.118</endAddress>
31    </loginIpRanges>
32    <loginIpRanges>
33        <description>AFV IDE Static IP Address</description>
34        <startAddress>35.173.46.159</startAddress>
35        <endAddress>35.173.46.159</endAddress>
36    </loginIpRanges>
37    <loginIpRanges>
38        <description>AFV IDE Static IP Address</description>
39        <startAddress>98.85.15.64</startAddress>
40        <endAddress>98.85.15.64</endAddress>
41    </loginIpRanges>
42    <loginIpRanges>
43        <description>AFV IDE Static IP Address</description>
44        <startAddress>44.255.127.30</startAddress>
45        <endAddress>44.255.127.30</endAddress>
46    </loginIpRanges>
47    <loginIpRanges>
48        <description>AFV IDE Static IP Address</description>
49        <startAddress>32.184.174.148</startAddress>
50        <endAddress>32.184.174.148</endAddress>
51    </loginIpRanges>
52    <loginIpRanges>
53        <description>AFV IDE Static IP Address</description>
54        <startAddress>15.157.244.168</startAddress>
55        <endAddress>15.157.244.168</endAddress>
56    </loginIpRanges>
57    <loginIpRanges>
58        <description>AFV IDE Static IP Address</description>
59        <startAddress>35.183.200.37</startAddress>
60        <endAddress>35.183.200.37</endAddress>
61    </loginIpRanges>
62    <loginIpRanges>
63        <description>AFV IDE Static IP Address</description>
64        <startAddress>3.66.124.229</startAddress>
65        <endAddress>3.66.124.229</endAddress>
66    </loginIpRanges>
67    <loginIpRanges>
68        <description>AFV IDE Static IP Address</description>
69        <startAddress>3.120.64.58</startAddress>
70        <endAddress>3.120.64.58</endAddress>
71    </loginIpRanges>
72    <loginIpRanges>
73        <description>AFV IDE Static IP Address</description>
74        <startAddress>63.35.124.169</startAddress>
75        <endAddress>63.35.124.169</endAddress>
76    </loginIpRanges>
77    <loginIpRanges>
78        <description>AFV IDE Static IP Address</description>
79        <startAddress>52.214.96.158</startAddress>
80        <endAddress>52.214.96.158</endAddress>
81    </loginIpRanges>
82    <loginIpRanges>
83        <description>AFV IDE Static IP Address</description>
84        <startAddress>18.213.38.17</startAddress>
85        <endAddress>18.213.38.17</endAddress>
86    </loginIpRanges>
87    <loginIpRanges>
88        <description>AFV IDE Static IP Address</description>
89        <startAddress>3.217.1.37</startAddress>
90        <endAddress>3.217.1.37</endAddress>
91    </loginIpRanges>
92    <loginIpRanges>
93        <description>AFV IDE Static IP Address</description>
94        <startAddress>44.232.109.242</startAddress>
95        <endAddress>44.232.109.242</endAddress>
96    </loginIpRanges>
97    <loginIpRanges>
98        <description>AFV IDE Static IP Address</description>
99        <startAddress>54.190.205.95</startAddress>
100        <endAddress>54.190.205.95</endAddress>
101    </loginIpRanges>
102</Profile>

After you’re done updating the IP ranges, Deploy the metadata to Your org by using the sf project deploy start command.

Frequently Asked Questions

Will the List of IPs Change, and How Do I Know When They Do?

The list of IPs doesn’t undergo frequent changes. In the event of a planned change, customers are notified before any changes.

Do I Add All the IPs?

Yes. While your workspace currently uses a single IP, we can reassign it to any IP on our list at any time for maintenance or capacity. We recommend allowlisting the entire IP list rather than just your current one to avoid the risk of an immediate, unannounced loss of connectivity.

Does the IP List Replace Other Security Controls?

IP allowlisting provides an extra layer of defense, but Salesforce still fully enforces all standard authentication methods. The standard authentication methods include usernames, passwords, MFA (multi-factor authentication), and Single Sign-On (SSO), alongside authorization controls like profiles, permission sets, and sharing rules.

Can I Restrict Access to My Organization's Workspaces Alone?

IP allowlisting alone isn’t enough because multiple organizations share those IPs. Instead, Salesforce authentication secures your data by making sure that only authorized users can log in, no matter where they connect from.

Developer Preview

This feature is available as a developer preview. The feature isn’t generally available unless or until Salesforce announces its general availability in documentation or in press releases or public statements. All commands, parameters, and other features are subject to change or deprecation at any time, with or without notice. Don't implement functionality in production with these commands or tools. If you want to use the static outbound IPs, contact your account executive to request enablement.