Regarding High Ping on 2nd Hop

[palflax]

Was just wondering why I would be getting 40ms on my 2nd hop in my tracert. It's quite annoying considering I play online games and I get 50 ping to servers located less than an hour driving distance to me.

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 40 ms 40 ms 39 ms 10.25.1.1
3 41 ms 40 ms 40 ms so-1-2-0-0.BING-CORE-RTR1.verizon-gni.net [130.8
1.9.74]
4 46 ms 46 ms 46 ms P3-0-0.BING-EDGE-RTR3.verizon-gni.net [130.81.21
.65]
5 41 ms 41 ms 41 ms so-0-3-0-0.BING-CORE-RTR2.verizon-gni.net [130.8
1.21.66]
6 45 ms 45 ms 46 ms so-2-0-1-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.20.186]
7 47 ms 47 ms 46 ms 0.so-3-1-0.XT1.NYC8.ALTER.NET [152.63.10.33]
8 47 ms 111 ms 46 ms 0.so-6-0-0.XL3.NYC4.ALTER.NET [152.63.16.221]
9 46 ms 48 ms 46 ms 4.68.110.105
10 47 ms 47 ms 47 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
11 48 ms 47 ms 47 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
12 53 ms 54 ms 53 ms ae-3-3.ebr4.Washington1.Level3.net [4.69.132.93]

13 55 ms 67 ms 54 ms ae-84-84.csw3.Washington1.Level3.net [4.69.134.1
86]
14 55 ms 55 ms 54 ms ae-3-89.edge1.Washington1.Level3.net [4.68.17.14
4]
15 54 ms 54 ms 55 ms GOOGLE-INC.edge1.Washington1.Level3.net [4.79.23
1.6]
16 58 ms 56 ms 56 ms 209.85.240.136
17 173 ms 68 ms 68 ms 66.249.95.149
18 70 ms 68 ms 69 ms 209.85.254.249
19 73 ms 72 ms 69 ms 209.85.255.190
20 * 68 ms 70 ms gw-in-f100.google.com [74.125.67.100]

Trace complete.

The problem is the second hop, which should not be at 40ms. There must be something wrong,  because it's exactly at 40ms every time I do a trace route.I'm using a Westell A90-750015-07 router/modem, and I'm using a wired connection.

[Imir2]

Depends on the game.

[palflax]

I know what you mean it depends on the game, I'm playing Counter-Strike 1.6 and ping is very very important. And having to start out with a 40 ping to any server is ridiculous, it means I will ping 40+ no matter where the server is even if it's in the same town. Unless you played CS 1.6 you would probably say, "Well 50 or 70 ping is fine" well it's not, when everyone else is running around with 10-20 ping and you're stuck with 70 ping, it's a huge advantage for them seeing as my recoil is all messed up and the fact they see me 50ms sooner.

[Imir2]

I know exactly what your talking about, 8 years of cs1.3-source.

Reasons for bad latency in counterstrike 1.6:

-Steam Client automatically updates its client every so often *background downloader.

-When VAC triggers its background scanning, it uses network resources due to its over on their side.

-When you first launch cs1.6 it naturally lags in the start of the game, waiting for a while should regulate normal ping rate.

-Third party applications would cause latency too and or framework type applications, java applications, visual basic applications.

If none of these are helpful run a scan on your computer for any bugs. I had a trojan that was sapping my network resources a while back. Good luck

[palflax]

My ping isn't that bad ingame, I get 50 ping to NYC servers which is reasonable considering my 2nd hop is ALWAYS at 40ms. That's what I'm trying to figure out here, it has to be the router they gave me or something on their end.

The thing I find odd is that it's exactly 40ms all the time, every time I traceroute, tried it on 3 different computers and the same thing as well. I believe this shouldn't be happening at all, it would be reasonable to have a 10-20ms 2nd hop but anything over that then I believe something is wrong. 

The mere fact that it's always at 40ms seems to be it might have to do with some sort of router setting delaying the connection to the gateway X ms for some unknown reason.