How to identify internal vs external networks
Sometimes you want to know what route your connection to C4C is taking or check what causes a high latency. For this, it is necessary to know if the issue is in the internal or the external network. There are several methods to identify this. Here are two:
-
Identify your external IP address with Google’s: “what is my IP”
Type “what is my IP” into the Google search. This will give you the external IP of your router. Anything after that on your trace route is an external network
Run a trace route and find your public IP address (or the first one on the same range)
-
Identifying if the IP in your trace route is Private or Public
The Internet Assigned Numbers Authority (IANA) reserves the following IP address blocks for use as private IP addresses:
- 10.0.0.0 to 10.255.255.255
- 172.16.0.0 to 172.31.255.255
- 192.168.0.0 to 192.168.255.255
If you see in your trace route something outside that range, it means that is an external IP address.
|
Hop |
RTT or Latency |
IP |
Location |
| 1 | 56, 14, 1 | 192.168.1.1 | Private |
| 2 | 2, 3, 2 | First Public | |
| 3 | 3, 2, 3 | Unknown | |
| 4 | 4, 4, 3 | 38.104.60.245 | Public |
| 5 | 125, 8, 8 | 154.54.41.66 | Public |
| 6 | 11, 9, 12 | 154.54.28.74 | Public |
| 7 | 51, 34, 10 | 154.54.11.34 | Public |
| 8 | 11, 15, 16 | 66.109.5.120 | Public |
| 9 | 10, 111, 8 | 66.109.6.181 | Public |
| 10 | 10, 9, 10 | 104.84.249.163 | Public |
It is important to point out, that some firewalls block trace routes and it might not be possible to see the external IP address. For information on how to go around that, check the TCP trace route section in the following article: How to troubleshoot high latency networks for SAP Cloud for Customer