routing issues
-
acemon
- New to forums
- Posts: 1
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Sat Aug 27, 2011 10:56 pm
routing issues
i live in idaho and i did a trace route to two different seattle servers and for some reason i am routed from idaho to california then colorado then 2 hops in new jersey then to georgia then to seattle i think this is ridiculous and explains when the menu screen says a 35 ping and i end up with a 70+ ping i amd on a 50 mb set up through the local cable company so i really dont understand the issue tand why im routed across the country and back again ti mean idaho borders washington the last time i looked at the map
Re: routing issues
It sounds as though you are using traceroute software that is incorrectly guessing where the routers are physically located along your path. This is very common, because most GeoIP data is culled from clients on an IP block who order services online and provide their address, and there are no clients on the IP blocks used by routers.
35ms would be normal from Idaho to Seattle, and it's normal in most games to see a higher number in-game because games show a latency on the scoreboard that is limited by the tickrate. Commonly, games run at only 30, 33, or 66 ticks per second; a tickrate of 30 means that your latency in-game would be up to 33ms higher at times (1000ms/30), giving you an in-game "ping" right around 70ms. (Some games, like BC2, show an even higher, and invalid, latency number, for no apparent reason.)
If you'd like me to take a closer look to see if your path can be improved, just give us a ring through the "Help!" page in your control panel, or email support@nfoservers.com. Include the command-line tracert from your client to the server and your personal IP address (a la http://www.nfoservers.com/forums/viewto ... =25&t=1539).
35ms would be normal from Idaho to Seattle, and it's normal in most games to see a higher number in-game because games show a latency on the scoreboard that is limited by the tickrate. Commonly, games run at only 30, 33, or 66 ticks per second; a tickrate of 30 means that your latency in-game would be up to 33ms higher at times (1000ms/30), giving you an in-game "ping" right around 70ms. (Some games, like BC2, show an even higher, and invalid, latency number, for no apparent reason.)
If you'd like me to take a closer look to see if your path can be improved, just give us a ring through the "Help!" page in your control panel, or email support@nfoservers.com. Include the command-line tracert from your client to the server and your personal IP address (a la http://www.nfoservers.com/forums/viewto ... =25&t=1539).