If you are experiencing slowness or latency when connecting to Salesforce, this article helps you determine whether the root cause is your local infrastructure, a third-party ISP (Internet Service Provider), or Salesforce. Salesforce Support requires traceroute and ping data to investigate suspected network performance issues — have this information ready before opening a case.
Before running diagnostic tools, complete these quick checks to rule out known issues.
Always start by checking status.salesforce.com. The Salesforce Trust Status page reports ongoing incidents and maintenance that may already explain your issue. Salesforce also posts general status messages when engaged with an ISP on networking issues.
Document the following before contacting Support:
Check whether teammates are experiencing the same issue. Compare users on wired vs. Wi-Fi connections, VPN vs. non-VPN, and across different office locations. If the issue is localized to one connection type or location, this points to a network issue rather than a Salesforce platform issue.
Also check whether the issue occurs across all orgs including sandboxes — if sandboxes perform differently, this can be diagnostic.
Are other websites or applications also slow? If yes, the issue is likely with your local network or ISP, not Salesforce.
Contact your internal Helpdesk to determine if any recent network or infrastructure changes were made that could affect Salesforce connectivity.
If no Salesforce platform issue is identified in the initial checks, Salesforce Support will ask you to provide the following basic network data.
Ping and traceroute tools quickly identify whether the issue is with your local network, ISP, or Salesforce. Run these tools and share the output with Salesforce Support.
Steps can be found in this article: Use Pings and Traceroutes to Troubleshoot Network Issues
Hyperforce uses Network Load Balancers (NLBs) which do not support ICMP ping packets, except for Type 3 (Destination Unreachable). If your Salesforce instance is on Hyperforce, standard ping and traceroute results may be unreliable or return no response. In this case, use TCP-based diagnostic tools instead.
Provide your public IP address to Salesforce Support when reporting a network performance issue. You can find your public IP at http://whatismyip.com.
When contacting Support, provide the following:
If a network problem is suspected on your local network, an ISP, or the Salesforce network, additional steps are needed. These are best handled by your organization's network engineers. The suspected issue must be easily reproducible, as captures must be done while the issue is occurring.
Salesforce needs a packet capture from your organization's external network endpoint (such as an external firewall interface) to analyze the network protocols in use. Built-in tools such as tcpdump and downloadable tools such as Wireshark are used for capturing and analyzing PCAP files.
If your endpoint is hosted in a third-party cloud (Google Cloud, AWS, Microsoft Azure), contact the vendor and have their Support team take the capture.
If the suspected issue is on Salesforce's side, Salesforce will schedule a meeting for network engineers to collect a PCAP from the Salesforce endpoint simultaneously with your team's capture. To complete this step, you must be able to:
If you are unable to pinpoint any networking issues after completing the above steps, provide all collected data to Salesforce Support, including:
000385480

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.