• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

High Ping

1

1000RR

Junior Member
Hi all,

Recently I noticed my ping on a gaming server spike after 6 o'clock every night, It would hover around 75-85 ping then spike to about 150 and sit there all night? I have done a few ping test and shows no packets loss, my DL/UL is 18mbps & .50 but varies each time I test it and the site I use. The server I am connecting to is located in Dallas Texas, I am in Toronto Canada. No programs/DL's are running in background when I'm connected to server.

My system specs:
AMD 4X3.2GHZ-->water cooled
8GIG DDR3
ATI6870 VC
MSI970A-G45 MB

Modem has a built in router from Rogers cable: Cisco dpc3825 (wireless is secured).

Any suggestions would be greatly appreciated.

1K
 
Server has 4 hosts (different maps) it runs 24/7. When I connect to one of the host that has no clients my ping is still 150+? Very strange how up until a few days ago it was fine but now it’s so high? Is there anything I can do to reset my modem connection? I already reset the modem manually but is there anything else I can do to get a better connection?

Any site you guys know off to test my upload/download/packet loss? I use speedtest.net/ speakeasy but would like other sites to try.
 
cmd > tracert

Find the culprit. If it's beyond your second hop then there's little-nothing you can really do about it other than provide the data to your ISP (and many may time out due to pingable response being refused by the machine).

I'm guessing you're not using WiFi, though that'd be one place to start if you were (by using a wired connection instead, changing channels on the router, moving the router to a better broadcast location, checking if any other devices or appliances are in the vicinity of the router that could be interfering with the signal, etc...). Run "ping www.google.com -t" during your suspected times of slowing. Rule out any correlation of local disturbances with times that spike then contact your ISP with your findings.

It probably just is congestion on the network, but depending on how useful the support is for your ISP they can actually investigate it and change routing if it becomes terrible. Make sure you diagnose that it's fault of the ISP routing prior to doing so, of course. 😉

For speed testing, I always use http://www.dslreports.com/stest

Welcome to the forums!
 
Wired connection, Once I do a cmd > tracert what option should I select for results? I did a ping google test and no packet loss --4 sent 4 received (0% loss) approximate round trip times in muili-seconds: minimum=41ms , maximum =42ms, average 41ms--
So it’s not bad also did the test when I had a high ping in server. When running the cmd > tracert what option should I select and what kind of result should I be looking for?

Thanks for the site, did a speed test and had to run it from NJ (Tekksavvy Toronto was not working) results: DL=15624 kb/s UL=.491kb/s 16ms ping .
 
Do you know the domain name (or IP address) of the game server you are using? If so, include that in the TRACERT command. (Put that address in place of www.google.com in my example below)

For example, to test the route between you and Google's closest server, open a command prompt and type: tracert www.google.com

You'll get results that will look something like this:

Tracing route to www.google.com [173.194.79.104] over a maximum of 30 hops:

1 2 ms <1 ms <1 ms unknown [192.168.0.1]
2 35 ms 48 ms 29 ms 76.23.38.1
3 9 ms 29 ms 11 ms te-5-3-ur08.saltlakecity.ut.utah.comcast.net [68.85.39.109]
4 13 ms 31 ms 11 ms te-9-4-ar02.saltlakecity.ut.utah.comcast.net [68.86.180.57]
5 29 ms 45 ms 23 ms pos-2-1-0-0-cr01.denver.co.ibone.comcast.net [68.86.90.237]
6 27 ms 40 ms 24 ms xe-0-0-2-0-pe01.910fifteenth.co.ibone.comcast.net [68.86.84.26]
7 92 ms 91 ms 88 ms 173.167.57.206
8 28 ms 22 ms 28 ms 72.14.234.57
9 37 ms 21 ms 23 ms 216.239.46.148
10 39 ms 54 ms 38 ms 216.239.46.159
11 46 ms 45 ms 47 ms 216.239.46.208
12 49 ms 45 ms 48 ms 216.239.48.167
13 * * * Request timed out.
14 48 ms 45 ms 45 ms pb-in-f104.1e100.net [173.194.79.104]

Trace complete.
Click to expand...

Look for abnormal results, such as my hop #7 has a significantly higher ping than any other hop on the route, and my hop 13 doesn't reply to pings at all. Not responding to a PING isn't necessarily a problem as long as you can get to the end of the route, but a series of several steps all giving asterisks for their ping times may be a sign of a problem. Excessively high ping times on a single hop can result in a slower response from the end server as well, although that isn't always the case. A TRACERT isn't a definitive test, but can give you a place to start looking if there is a problem in one of the first few steps as that will usually be an issue with your ISP. If the problem is farther down the list, then there's usually not much that you can do about it since that could be a router on the other side of the country (or the other side of the world).
 
Last edited:
Tracing route to www.google.com [173.194.75.104]
over a maximum of 30 hops:
1 * * * Request timed out.
2 12 ms 11 ms 11 ms 66.185.91.137
3 20 ms 11 ms 11 ms 24.156.156.149
4 24 ms 23 ms 25 ms 64.71.240.66
5 75 ms 75 ms 77 ms 74.125.49.229
6 25 ms 23 ms 110 ms 209.85.255.68
7 26 ms 29 ms 25 ms 209.85.251.35
8 31 ms 35 ms 33 ms 72.14.239.93
9 41 ms 46 ms 42 ms 209.85.243.114
10 41 ms 43 ms 43 ms 216.239.48.157
11 * * * Request timed out.
12 41 ms 42 ms 41 ms ve-in-f104.1e100.net [173.194.75.104]
Trace complete.

Google test, what do you guys think of the results? just to get an idea of my connection.
 
Last edited:
Hop 5 is rather high, and hop 6 had a spike. Start running ping -t on those 2 IPs (you can do them simultaneously in multiple cmd windows) and see if you get constant high pings or loss. That'll be where you'll be focusing your issues with your ISP routing if they acknowledge your findings.

However, the true test will be for tracert on your gaming server. This acknowledges a possible routing issue to google, which doesn't necessarily represent anything when connecting to your gaming server.
 
Last edited:
1000RR said:
how do I trace an IP address IP: 72.232.196.164:28930?

Website is http://www.edge-gamers.com/forums/cmps_index.php?pageid=serverlist&game=cod4 is there server I am connecting to an dthose are the host? I dont know how to enter the command to do the trace using IP address?
Click to expand...

tracert 72.232.196.164


edit: I just did 1000 consecutive pings on that IP address and while the average time was 42 ms (reasonable), there were quite a few spikes over 150 ms so it seems like it might be teh server itself that is occasionally lagging.
 
Last edited:
Tracing route to bmbinternet4.meulog.com.br [72.232.196.164]
over a maximum of 30 hops:
1 * * * Request timed out.
2 15 ms 11 ms 11 ms 66.185.91.137
3 17 ms 11 ms 11 ms 24.156.156.149
4 25 ms 25 ms 24 ms 64.71.240.66
5 24 ms 24 ms 23 ms xe-2-0-0.er1.lga5.us.above.net [64.124.128.193]
6 25 ms 25 ms 23 ms xe-5-1-0.cr1.lga5.us.above.net [64.125.30.205]
7 25 ms 26 ms 29 ms xe-0-0-0.cr2.lga5.us.above.net [64.125.29.42]
8 25 ms 25 ms 25 ms xe-0-0-1.er4.lga5.us.above.net [64.125.24.169]
9 55 ms 33 ms 25 ms above-l3.lga5.us.above.net [64.125.13.130]
10 29 ms 25 ms 25 ms vlan80.csw3.NewYork1.Level3.net [4.69.155.190]
11 26 ms 26 ms 24 ms ae-82-82.ebr2.NewYork1.Level3.net [4.69.148.41]
12 60 ms 59 ms 59 ms ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121]
13 60 ms 72 ms 60 ms ae-82-82.csw3.Dallas1.Level3.net [4.69.151.153]
14 * 63 ms 61 ms ae-32-80.car2.Dallas1.Level3.net [4.69.145.132]
15 55 ms 65 ms 55 ms DATABANK-HO.car2.Dallas1.Level3.net [4.71.170.2]
16 * * * Request timed out.
17 * * * Request timed out.
18 54 ms 55 ms 55 ms bmbinternet4.meulog.com.br [72.232.196.164]
Trace complete.


If I'm reading this correct my ping starts to take a dive at hop 12.


pandemonium, this is the command I type in tracert 72.232.196.164 -t which returns a list of options:


Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout]
[-R] [-S srcaddr] [-4] [-6] target_name
Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list (IPv4-only).
-w timeout Wait timeout milliseconds for each reply.
-R Trace round-trip path (IPv6-only).
-S srcaddr Source address to use (IPv6-only).
-4 Force using IPv4.
-6 Force using IPv6.

What do I do from this point??
 
1000RR said:
What do I do from this point??
Click to expand...

Traceroute and Ping are meant to test connectivity. While they provide latency figures, they are not meant to diagnose performance.

I will reiterate again that pathping is a better tool for this. It will trace the path of your packet like traceroute, but will send 100 packets to each individual hop to identify if any hops in particular are dropping or delaying packets. You can do this manually with ping and traceroute, but it's time consuming.

To use it, expand the horizontal size of your command prompt window, and then run:
pathping 72.232.196.164
 
Ahh, Level3. No surprise there. Though, 70ms isn't much to complain against. If it were 100+ then you may have some ground to stand on. But to be honest, even if you go to your ISP with this information they probably won't bother with trying to do anything and wave you off.

The -t switch is for ping only (which means no set timed duration for the command). It makes the command continue to ping until you cancel/stop it (with ctrl-c), which is useful for seeing constant connection issues/time outs.
 
pandemonium said:
Ahh, Level3. No surprise there. Though, 70ms isn't much to complain against. If it were 100+ then you may have some ground to stand on. But to be honest, even if you go to your ISP with this information they probably won't bother with trying to do anything and wave you off.

The -t switch is for ping only (which means no set timed duration for the command). It makes the command continue to ping until you cancel/stop it (with ctrl-c), which is useful for seeing constant connection issues/time outs.
Click to expand...


Where do you seeing level3 and what point do I contact my ISP and complain the service they are providing is lagging.
 
1000RR said:
10 29 ms 25 ms 25 ms vlan80.csw3.NewYork1.Level3.net [4.69.155.190]
11 26 ms 26 ms 24 ms ae-82-82.ebr2.NewYork1.Level3.net [4.69.148.41]
12 60 ms 59 ms 59 ms ae-3-3.ebr2.Dallas1.Level3.net [4.69.137.121]
13 60 ms 72 ms 60 ms ae-82-82.csw3.Dallas1.Level3.net [4.69.151.153]
14 * 63 ms 61 ms ae-32-80.car2.Dallas1.Level3.net [4.69.145.132]
15 55 ms 65 ms 55 ms DATABANK-HO.car2.Dallas1.Level3.net [4.71.170.2]
Click to expand...

They're a major telecommunications infrastructure company that provides the backbone to a lot of the internet trafficking. And from personal and professional support experience, they're usually to blame for the majority of bottlenecking communications and overloading their routers.

Do ping -t where the connection seems to take a dump.

ping 4.69.137.121 -t

If you're seeing this go beyond 100ms frequently then I'd say you have grounds to complain to your ISP and ask them about rearranging their routing for you. Please note that this is a long shot, and they may not be able to do anything (logistically or policy-wise).

From here on out, you're next to SOL. Sorry, man. :/
 
Last edited:
You must log in or register to reply here.

TRENDING THREADS

Back
Top