Tracert showing 30+ hops to my public IP on AzureVM.

Question

Tracert showing 30+ hops to my public IP on AzureVM.

Bob Penfold 0

I manage an Azure server farm and notice via tracert that all of my public IP show 30+ hops, most of which time-out. Notice 104.X twice and believe this is the Microsoft gateway range.

4 6 ms 6 ms 6 ms 71.155.x.x

5 9 ms 7 ms 7 ms 12.242.x.x

6 11 ms 19 ms 63 ms 12.90.x.x

7 * * * Request timed out.

8 * * 27 ms 104.44.34.174

9 29 ms 30 ms 31 ms 51.10.9.230

10 29 ms * * 104.44.52.135

11 * * * Request timed out.

12 * * * Request timed out.

...

29 * * * Request timed out.

30 * * * Request timed out.

1 answer

Your answer

Answer 1

Hello @ Bob Penfold

Thanks for reaching out to Microsoft Q&A

As discussed over the call. Another possibility is that your ISP blocks ICMP traffic either regularly or during periods of high network activity.

ICMP, which is the protocol traceroute uses, is considered low priority, so routers may drop ICMP packets when higher priority traffic is present. Additionally, some ISPs block all ICMP packets for security reasons, as many Denial-of-Service attacks use ICMP probing.

If you notice timeouts, it doesn't necessarily mean there's an issue on your end. This usually happens for security reasons, as the ISP may block ICMP traffic. This is expected behavior.

If you really facing the issue with latency, please clear application cache and try.

If the answer is helpful, Please and “up-vote” it. If you have extra questions about this answer, please click "Comment".

Share via

Tracert showing 30+ hops to my public IP on AzureVM.

1 answer

Your answer