Ping way off last week or so.

[delems]

For the last year or two I've had a 50-60 ping; however, the last week or so my ping has gone to 90-100 everyday. What has happened?

[delems]

Here are traceroutes to different IPs - can you please check the mac code and see why it doesn't always use the fast one?

About 1 in 20 I log in I get the fast one; the rest of the time it is the slow one; AND that is slowing to 100 during the day and 50-60 at night now???

Slower one (used to be 50-60 --- but now slows to 100 half the day - never did that before)

traceroute to 66.28.224.144 (66.28.224.144), 64 hops max, 52 byte packets

1 wireless_broadband_router (192.168.1.1) 0.644 ms 0.393 ms 0.248 ms

2 l100.plspca-vfttp-10.verizon-gni.net (108.43.131.1) 5.073 ms 4.924 ms 3.468 ms

3 g3-0-1-2210.plspca-lcr-02.verizon-gni.net (130.81.221.146) 5.158 ms 5.584 ms 4.968 ms

4 so-7-0-3-0.lax01-bb-rtr2.verizon-gni.net (130.81.199.8) 9.040 ms 9.849 ms 9.508 ms

5 0.xe-4-2-0.br3.sjc7.alter.net (152.63.51.237) 20.745 ms 20.766 ms 20.657 ms

6 te0-2-0-5.ccr21.sjc03.atlas.cogentco.com (154.54.12.169) 20.778 ms 20.771 ms 20.591 ms

7 be2000.ccr21.sjc01.atlas.cogentco.com (154.54.6.105) 23.711 ms 25.038 ms 25.417 ms

8 te0-2-0-4.mpd21.sfo01.atlas.cogentco.com (154.54.6.133) 24.938 ms

te0-1-0-5.ccr21.sfo01.atlas.cogentco.com (154.54.2.137) 22.991 ms

te0-1-0-5.mpd21.sfo01.atlas.cogentco.com (154.54.2.53) 25.999 ms

9 te0-3-0-1.ccr21.mci01.atlas.cogentco.com (154.54.24.110) 79.556 ms

te0-1-0-3.mpd21.mci01.atlas.cogentco.com (154.54.2.209) 82.724 ms

te0-0-0-2.mpd21.mci01.atlas.cogentco.com (154.54.6.37) 88.419 ms

10 te0-3-0-1.ccr21.dfw01.atlas.cogentco.com (154.54.46.186) 91.278 ms

te0-4-0-2.ccr21.dfw01.atlas.cogentco.com (154.54.46.202) 91.400 ms

te0-4-0-5.ccr21.dfw01.atlas.cogentco.com (154.54.46.198) 91.195 ms

11 te4-2.ccr01.dfw02.atlas.cogentco.com (154.54.26.162) 91.066 ms 92.387 ms 94.855 ms

12 * playnet.demarc.cogentco.com (66.28.30.146) 56.092 ms !X *

13 playnet.demarc.cogentco.com (66.28.30.146) 57.153 ms !X * 55.422 ms !X

Faster one (when I connect here my ping is 45)

traceroute to 209.144.109.143 (209.144.109.143), 64 hops max, 52 byte packets

1 wireless_broadband_router (192.168.1.1) 0.552 ms 1.559 ms 0.253 ms

2 l100.plspca-vfttp-10.verizon-gni.net (108.43.131.1) 3.959 ms 4.380 ms 4.237 ms

3 g2-0-2-110.plspca-lcr-01.verizon-gni.net (130.81.54.248) 5.579 ms 5.666 ms 4.953 ms

4 130.81.199.46 (130.81.199.46) 10.666 ms 9.166 ms 8.868 ms

5 0.xe-8-1-0.br1.lax15.alter.net (152.63.112.233) 9.117 ms 9.273 ms 8.856 ms

6 209.144.222.249 (209.144.222.249) 9.742 ms 9.744 ms 9.755 ms

7 cr2-te-0-5-0-3.lay.savvis.net (206.28.97.249) 9.462 ms 10.020 ms 9.325 ms

8 cr2-te-0-2-0-2.dan.savvis.net (206.28.96.129) 43.506 ms 43.698 ms 44.747 ms

9 bcr1-so5-0-0.dallas.savvis.net (204.70.198.110) 47.376 ms 45.894 ms 46.119 ms

10 * t35494-2.savvis-internet.usdlls2-j20c.savvis.net (216.90.2.250) 81.251 ms !X *

11 t35494-2.savvis-internet.usdlls2-j20c.savvis.net (216.90.2.250) 82.071 ms !X * 83.625 ms !X

[wockawocka]

This is actually a question for your internet provider (verizon?) and because I live in Sweden I have very limited knowledge of which ISPs are good or bad in US for gaming.

But what I "read" from those "traceroutes" is:

• The re-routing occours in verizon parts of the network
  
• It happens somewhere near your home (lax area), meaning you could probably change this by changing ISP, or get help from your ISP
  
• It is not verizon that has a congestion, but it still uses "the cheapest link" instead of the "lowest latency link" (these are priority lists in each router on the internet, and ISPs pay for what they get)
  
• If using a cable between your computer and internet (instead of wireless) you would save 5ms directly, and not be affected of anyone using the same wireless router.
  
• savvis isp seem to be a uncongested part of internet around Dallas, and maybe they have priority for game traffic (UDP), but even them seem to congested adding some strange numbers around Dallas, adding about 30ms
  

What you (we all) want when playing is a stable ping, because then the prediction code will be more effective. High speed is not important as long you meet the minimum bandwidth requirement (which is only about 8kbytes per second (64kbit or ISDN))

Some ISPs have the option to pay for prioritized traffic on internet (good for gaming), and if your "packets" would have had that "tag" then you would have that "shorter route" all the time.

[delems]

Note: Here is the traceroute for the morning - note it is much faster, with 60.

traceroute to 66.28.224.144 (66.28.224.144), 64 hops max, 52 byte packets

1 wireless_broadband_router (192.168.1.1) 0.670 ms 0.368 ms 0.253 ms

2 l100.plspca-vfttp-10.verizon-gni.net (108.43.131.1) 5.403 ms 5.240 ms 4.968 ms

3 g3-0-1-2210.plspca-lcr-02.verizon-gni.net (130.81.221.146) 6.195 ms 5.503 ms 6.404 ms

4 so-7-0-3-0.lax01-bb-rtr2.verizon-gni.net (130.81.199.8) 9.536 ms 9.991 ms 8.819 ms

5 0.xe-4-2-0.br3.sjc7.alter.net (152.63.51.237) 22.862 ms 33.644 ms 23.514 ms

6 te0-2-0-5.ccr21.sjc03.atlas.cogentco.com (154.54.12.169) 23.549 ms 24.291 ms 23.336 ms

7 be2000.ccr21.sjc01.atlas.cogentco.com (154.54.6.105) 27.402 ms 26.263 ms 26.654 ms

8 te0-0-0-4.ccr21.sfo01.atlas.cogentco.com (154.54.1.129) 27.869 ms

te0-0-0-4.mpd21.sfo01.atlas.cogentco.com (154.54.1.25) 27.427 ms

te0-3-0-5.mpd21.sfo01.atlas.cogentco.com (154.54.86.185) 29.148 ms

9 te0-1-0-2.ccr21.mci01.atlas.cogentco.com (154.54.24.118) 60.136 ms

te0-0-0-2.ccr21.mci01.atlas.cogentco.com (154.54.30.54) 60.530 ms

te0-4-0-3.mpd21.mci01.atlas.cogentco.com (154.54.45.77) 61.384 ms

10 te0-2-0-2.ccr21.dfw01.atlas.cogentco.com (154.54.5.221) 60.452 ms

te0-0-0-5.ccr21.dfw01.atlas.cogentco.com (154.54.5.217) 58.711 ms

te0-5-0-7.ccr21.dfw01.atlas.cogentco.com (154.54.85.158) 61.726 ms

11 te4-2.ccr01.dfw02.atlas.cogentco.com (154.54.26.162) 58.692 ms 58.657 ms 59.063 ms

12 * playnet.demarc.cogentco.com (66.28.30.146) 59.349 ms !X *

13 playnet.demarc.cogentco.com (66.28.30.146) 59.948 ms !X * *

14 playnet.demarc.cogentco.com (66.28.30.146) 59.621 ms !X * 58.369 ms !X