MiCarl
Member
Somewhere I saw instructions on how to identify the node my VPS is on. It instructed to use a tracert to my ip and the next to last hop would be the node.
When I tracert to my IP address (162.255.166.19) the next to last hop has no name just an IP address. The last few lines of my tracert:
11 43 ms 42 ms 43 ms 144.202.254.42
12 43 ms 41 ms 43 ms 144-202-238-253.baltimoretechnologypark.com [144.202.238.253]
13 43 ms 43 ms 47 ms 144.202.227.33
14 42 ms 53 ms 43 ms host.thundervalleypower.com [162.255.166.19]
Last night I did a tracert on another VPS that is in the Texas data center. That one showed the node in the next to last hop so I guess it's specific to either the hardware I'm on or the East Coast center.
I am a little curious which node I'm on. That way if there ever is a problem I can see in the Network and Hardware status board if you know about it and are working on it.
Is there something that needs fixing on your end, or should I be using a different method?
When I tracert to my IP address (162.255.166.19) the next to last hop has no name just an IP address. The last few lines of my tracert:
11 43 ms 42 ms 43 ms 144.202.254.42
12 43 ms 41 ms 43 ms 144-202-238-253.baltimoretechnologypark.com [144.202.238.253]
13 43 ms 43 ms 47 ms 144.202.227.33
14 42 ms 53 ms 43 ms host.thundervalleypower.com [162.255.166.19]
Last night I did a tracert on another VPS that is in the Texas data center. That one showed the node in the next to last hop so I guess it's specific to either the hardware I'm on or the East Coast center.
I am a little curious which node I'm on. That way if there ever is a problem I can see in the Network and Hardware status board if you know about it and are working on it.
Is there something that needs fixing on your end, or should I be using a different method?