why did I have to do a separate search on a different engine to find this information?
/ranton
There’s no quick simple easy pinned anything like “Common Trace Route” etc. you have everything else, but this is buried and I don’t remember the magical click path to find it.
Just saying, might be helpful for those of us that have had issues for 10 years, are well familiar with these processes, and just want to get to the pertinent info quickly, without having to follow some hidden click script to finally arrive there.
/rantoff
why is my 8th hop to 137.221.66.164 the blizzard server located in France?
I’m in north America playing on the north American servers
running a winmtr is just their way of blaming the ISP off the start, why not hide the way to find out what’s actually wrong? It’s more than likely because it’s always them. I quit due to 1016’s @ 16-17th seasons because they literally refer me to the same guides over and over again with no results. Then when you post that good ole WinMTR they’re like looks like it’s your isp, then tell you to call them. This is HR saving face and keeping numbers up for the boss by saying everything is dandy here, by pushing all blame off like they have a repellent. Oh wait thats the claim to immunity every dev takes before they rip off the pubic for profits over consumer care.
What you’ll notice when you do a traceroute, pathping or WinMTR trace is that your network traffic goes through 20-30 hops between your PC and Blizzard’s servers. All but the final few of those hops are not Blizzard’s responsibility. The vast majority of the time that people actually post their traces, there’s packet loss early in the hops, i.e. intermediary network devices that have absolutely nothing to do with Blizzard.
This is like having to drive from one end of Route 66 to the other and complaining that it’s the fault of the hotel at your destination that there was a traffic jam half-way there.
This is exactly what I’m talking about, having clicked thru it wasn’t leaping out like it did on the old forums. It literally became easier because THESE forums search function are ineffective, at best. A third party got me the answer immediately, the source had hoops loops and hurdles to go through.
That is not correct. A dropped ping is typically because the network admin for that particular network has turned off ICMP echo ping replies on their edge router. It doesn’t mean anything more typically, especially if the trace goes past that dropped ping to the next hop…
PS I was a network admin for a small ISP for 8 years in my last job…
I guess my issue is in when doing something like a “whois ” search, that was published and updated last month, it’s still going to show France, even though that information is incorrect.
how then, do we actually know where these servers are?
You wouldn’t get a response on all three pings to that IP address if that device was set to not respond, not one or two.
Perhaps Meteor could clarify if what he typed was too broad.
Any router configured to drop ICMP would show up in a trace as 100% packet loss. Whilst that’s what happens in traces where the traffic reaches Blizzard’s edge hop and beyond, it’s not the case for the intermediary hops, and certainly wouldn’t explain issues where traces show small amounts of packet loss, i.e. more than zero, but obviously way less than 100%.
We regularly see traces where there’s packet loss within the first couple of hops, i.e. the customer’s own ethernet connection to the router/hub, or within their ISP’s network, long before it gets anywhere near to Blizzard’s edge.
If all 3 IP addresses were on the same network, being the same edge firewall that is…most ISP have multiple ranges, and will have front facing edge routers for each range…
Correct.
No response does NOT equal packet loss. If the next hop is responding, then the prior hop passed the network activity on via its routing table. If there is a break in the connection, then the network activity will not be passed onto any latter hops in the path, it’ll just die there…that would be data loss.
These days, routers are using BGP, which is pretty smart, rather than hard coded routing paths. And there is a reason for that and that is to avoid hard breaks in network connectivity.
Again, routers not responding [to ICMP echo pings] is very common. It’s not RFC compliant, but many ISP/networks don’t care about being RFC compliant.
Anyway, real men use ping, traceroute, finger, telnet, not that Windows winmrt crap. Hell, real men don’t use MS Windows (I am being cheeky here )
hey guy… just wanted to let you know I’m playing overwatch and running into a huge lag spike issue when i googled the highest latency server and found this thread on top. seems related. I also made tech support in other forum, but it’s nice to know you’re not hte only one with the issue.
You could post a new topic instead.
Your log missed the lower half. Anyway, I see some data packet loss at hop 3:
172.30.9.165 is a private (local) IP addresses. By the names of hop 2 and 4, I think belongs to your ISP mchsi.com (?)
Therefore you should contact your ISP to investigate and resolve the issue.
Hell, real men don’t use MS Windows