Why tracert request timed out

Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Upcoming Events. Featured on Meta. Now live: A fully responsive profile. Related 1. Hot Network Questions. Question feed. Accept all cookies Customize settings. That said, without more details about who your ISP is, or at least your general geographical region, it's hard to say more.

Is this "standard IPv4 address" the first one after your computer? Or is this a few hops away? Here's an example going from my house to google - no, I don't really care if you see my traceroute output, because it tells you fuck-all about my location beyond a general city locality which I already provide via my Tribus. You're going to see that I use This is MacOS traceroute, but the output is about the same anyway.

Code: traceroute to 8. Basically it means nothing and is extremely common. Infrequent tasks like responding to traceroutes get handled by the CPU, which is also needed for other more important tasks.

They really aren't designed to respond to that stuff with high reliability. I have written down that specific IP and assume it's still the same one, it just doesn't respond anymore.

What's interesting is the following, and I hope you all read this carefully and think it through carefully before replying How can I gather further information to prove or disprove this theory? Even if I'm wrong, how could I route around this IP? That's how it works. A traceroute to that IP goes only one hop because there is only one device in the path: your router. So that's normal. Traceroute to anything else That's the internet.

Quote: I have written down that specific IP and assume it's still the same one, it just doesn't respond anymore. Wrong assumption. It may have changed.

The path your traffic takes to a certain website or server or IP address on the internet may change, even minute to minute. Also, they may be blocking ICMP now where they weren't before. Temporarily or permanently. It does pass through your external IP. You just may not see it depending on how your device is configured or your network setup. You see it in the traceroute to your IP because it is the final destination you told it to trace to.

When you traceroute to something outside of your network you will probably see the 'internal' IP of your gateway, not the public IP that shows up on whatismyip. Not sure what you mean by 'anonymised IP address', that is not a thing. The traceroute will only show network hops in your ISP network for a few lines assuming you are not using a Proxy or VPN service and then it will show hops in other networks.

That's how the internet works. Quote: How can I gather further information to prove or disprove this theory? What theory? That your misunderstanding of networks and traceroutes means you are being hacked? Well you are definitely wrong. As for how you can 'route around it', well, no one can tell you that because you have not explained what IP it is or where it is in the traceroute or well, anything.

Please feel free to ask for more Information and let me know if this helps. Details required : characters remaining Cancel Submit. Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. Traceroute request timed out? If the firewall blocked the traffic, why it is not blocking Wireshark because wireshark captured the packets and i can see the IPs of all of the middle hops as you can see in the screenshot.

As for the ISP blocking, I can trace without issue using mobile phone connected to the same Wifi or my colleagues can trace when we are in office and connected to the same wifi. I took a quick look at the url you shared. And I find something I really interested in, which is a tcp based trace route. I suppose it will work for me sometimes. But I dont know is there any software tools providing this function.

From the comments I see a linux command line tool " tcptraceroute ", but I am on Windows. I have a CentOS virtual machine running on my computer using Hyper-V , and in there, trace route works fine. The packet were sent by the tracert command, then Wireshark capture it and the response packet.

The problem is that in the Wireshark, i can see the routers those packets were passing but from the tracert command line result, I can't. Just now, I came to know that Wireshark can capture packet before firewall dropping packets, so I will surely check my Windows Firewall and Anti-virus software firewall. Althrough it looks wired that my CentOS Guest host could actually trace. Choose where you want to search below Search Search the Community.

Search the community and support articles Windows Windows 10 Search Community member.