What is request timed out in tracert mean ?
|
|
 May 13 2018, 08:04 PM
Return to original view | IPv6 | Post
#1
|
 
Junior Member
297 posts Joined: Jul 2010 
|
Ping test je. You don't need to know the next hop ip also. Request time out means unable to reach destination ip, for your case StarCraft la. Likely due to packet drops due to shitty internet connection or StarCraft server got issue
This post has been edited by xchaosdragon: May 13 2018, 08:05 PM |
|
|
May 14 2018, 10:13 AM
Return to original view | Post
#2
|
|
Junior Member
297 posts Joined: Jul 2010
|
QUOTE(maxizanc @ May 13 2018, 08:58 PM) Correct me if im wrong. Time out in tracert could mean that the node is busy. Or the icmp is busy. Busy because ICMP is given lowest priority. Or the icmp is disabled. So it fail to return the message to the requester but packets stil able to go through the next hop Yes, the node may be busy as it might be under heavy load. The server is incapable of handling the surge of traffic resulting in lost packets, so icmp packets lost is no surprise here. It's not really useful to know the next hop if you cannot find out who does the IP belong to. But from this case, seems like it exited your ISP cloud and to the internet. The 54.xx. may be the gateway to StarCraft server. It might be something happened in between the gateway and the server or the server itself died. Also, did you try to do a ping test? Is it reachable or intermittent? Not sure if your ISP might have block this as well though. Edit: a quick ping test using browser ping tester from.other rgions also shows that the server is unreachable tho This post has been edited by xchaosdragon: May 14 2018, 10:24 AM |
| Bump Topic Add ReplyOptions New Topic |
| Change to: |  0.0134sec
 0.79
 6 queries
 GZIP Disabled
Time is now: 15th December 2025 - 01:19 PM |
Quote