Ping issues is QL's fault

[Epitaph]

I use to ping pretty good to every server and I can even remember what the exact pings were. Currently I only ping 'decent' to Chicago and Toronto servers. I only play on Toronto servers. Sadly I paid for the pro of this which is becoming a waste of money at this point. Ping has been 140+ on most servers, which NO other games having any issues at all. Just QL. I'm sure others must be having these issues.

Previous Pings:

Toronto - 35
Ashburn - 50
Chicago - 70
Dallas - 90
New York - 75

All are 140-160 now except for Toronto which has stayed the same. What the ****.

[hakujin]

The problem is most of the servers for Quakelive are all like on single-homed level3. So if your paticular ISP does not have good/direct connectivity to level3 than you are probably gonna get fux0rd. Yeah QL chose a bad provide to go with game-servers.

[DoktorTeeth]

anyone who reports a latency issue should include a traceroute log. Plus you shouldn't even consider complaining UNTIL you've done a traceroute. The internet has been seeing a lot of slowdowns recently, either way the traceroute is your proof of a problem IF it's the server and not somewhere halfway between. As you can see below, there's many devices between your computer and the destination
(note: this destination was quakelive.com, and NOT a quakelive game server. you need to trace to a server directly if you want any proof):

Hop Hostname IP Time 1 Time 2
1 me.local.router 0.292ms pmtu u-&
1 myisp.gateway 0.566ms asymm Y(;
1 myisp.gateway 1.846ms asymm Y(;
2 myisp.gateway 1.476ms pmtu Y(;
2 myisp.com 52.396ms * Y(;
3 Myispsmiddleman.net 52.600ms * Y(;
4 out onto the WWW.NewYork1.Level3.net 56.235ms asymm Y(;
5 ae-1-60.edge3.NewYork1.Level3.net 55.575ms asymm Y(;
6 te2-5.bbr01.tl01.nyc01.networklayer.com 58.026ms * Y(;
7 ae1.bbr01.eq01.chi01.networklayer.com 79.324ms asymm u-&
8 no reply * Y(;
9 ae6.dar02.sr01.dal05.networklayer.com 93.083ms asymm Y(;
10 po2.fcr01.sr01.dal05.networklayer.com 94.328ms asymm Y(;
11 50.23.229.123-static.reverse.softlayer.com 102.129ms reached Y(;

[Mythz]

Target Name: N/A
IP: 69.12.54.12
Date/Time: 10/16/2011 3:13:39 PM to 10/16/2011 3:13:48 PM

1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms phub.net.cable.rogers.com [192.168.0.1]
2 20 ms 6 ms 6 ms 8 ms 6 ms 6 ms 6 ms 6 ms 6 ms 48 ms [7.53.200.1]
3 19 ms 7 ms 7 ms 7 ms 7 ms 7 ms 7 ms 7 ms 7 ms 59 ms gw03.lndn.phub.net.cable.rogers.com [66.185.90.65]
4 18 ms 9 ms 11 ms 17 ms 11 ms 11 ms 8 ms 10 ms 9 ms 28 ms so-5-1-3.gw02.mtnk.phub.net.cable.rogers.com [66.185.81.181]
5 27 ms 9 ms 12 ms 9 ms 11 ms 9 ms 11 ms 12 ms 13 ms 78 ms [69.63.250.129]
6 54 ms 23 ms 23 ms 23 ms 23 ms 22 ms 23 ms 23 ms 38 ms 73 ms [64.71.241.118]
7 28 ms 26 ms 28 ms 28 ms 26 ms 25 ms 26 ms 25 ms 26 ms 84 ms [162.97.119.153]
8 37 ms 26 ms 34 ms 27 ms 31 ms 51 ms 37 ms 26 ms 26 ms 92 ms lag9.csr1.DCA3.gblx.net [67.16.146.25]
9 29 ms 25 ms 25 ms 27 ms 27 ms 44 ms 25 ms 27 ms 27 ms 74 ms po4-20G.ar2.DCA3.gblx.net [67.16.145.34]
10 44 ms 44 ms 43 ms 44 ms 46 ms 45 ms 153 ms 43 ms 44 ms N/A [155.229.48.45]
11 78 ms 44 ms 44 ms 44 ms 45 ms 44 ms 44 ms 45 ms 45 ms N/A [155.229.101.149]
12 67 ms 62 ms 60 ms 58 ms 59 ms 61 ms 59 ms 58 ms 60 ms N/A ae1-mxc2.atlngamq.bb.megapath.net [155.229.57.154]
13 75 ms 64 ms 60 ms 60 ms 60 ms 111 ms 60 ms 63 ms 60 ms N/A [155.229.101.194]
14 77 ms 61 ms 60 ms 60 ms 60 ms 60 ms 78 ms 60 ms 58 ms N/A [155.229.101.30]
15 67 ms 58 ms 59 ms 61 ms 59 ms 59 ms 71 ms 59 ms 59 ms N/A [69.12.54.12]

Ping statistics for 69.12.54.12
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 58ms, Maximum = 71ms, Average = 61ms


Used to be 30-40ms

Its not just level 3, although l3 is the worst sometimes hitting 100ms on servers I pinged 40 to before the problems started. And its the same ISP.

[r3zurector]

I am in Georgia. Used to ping <20 to ATL servers. Level3 changed their routing and now my route goes from ATL to Washington and back to ATL causing a 75+ ping to ATL. (ping shows 42ms but server ping is actually 75+) VA is the only server I ping decent to anymore. I used to be able to play TX\IL\Toronto\VA\ATL with ATL being my preference because of the <20 ping............!

Target Name: N/A
IP: 69.12.54.12
Date/Time: 11/29/2011 9:29:25 AM

1 0 ms Redacted [192.168.254.1]
2 27 ms [76.97.212.1]
3 9 ms xe-11-0-0-0-sur01.r2conyers.ga.atlanta.comcast.net [68.85.173.49]
4 10 ms xe-10-0-3-0-ar01.b0atlanta.ga.atlanta.comcast.net [68.86.106.254]
5 17 ms pos-3-7-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.93.205]
6 11 ms [4.28.24.77]
7 12 ms vlan52.ebr2.Atlanta2.Level3.net [4.69.150.126]
8 11 ms ae-73-73.ebr3.Atlanta2.Level3.net [4.69.148.253]
9 25 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]
10 28 ms ae-91-91.csw4.Washington1.Level3.net [4.69.134.142]
11 26 ms ae-42-90.car2.Washington1.Level3.net [4.69.149.196]
12 24 ms ge1-1.bbsr1.iad.megapath.net [166.90.148.2]
13 42 ms [66.80.131.46]
14 42 ms ae3-10.c01.ash.bb.megapath.net [155.229.57.180]
15 28 ms [155.229.101.149]
16 42 ms ae1-mxc2.atlngamq.bb.megapath.net [155.229.57.154]
17 43 ms ge-2-1-0-0.c00.atp.bb.megapath.net [155.229.101.194]
18 41 ms ge0-3.a20.atp.bb.megapath.net [155.229.101.30]
19 42 ms [69.12.54.12]

Ping statistics for 69.12.54.12
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 42ms, Maximum = 42ms, Average = 42ms

[Dr_Mr_Ed]

I am in Georgia. Used to ping <20 to ATL servers. Level3 changed their routing and now my route goes from ATL to Washington and back to ATL causing a 75+ ping to ATL. (ping shows 42ms but server ping is actually 75+) VA is the only server I ping decent to anymore. I used to be able to play TX\IL\Toronto\VA\ATL with ATL being my preference because of the <20 ping............!

Interesting. My path from central PA looks almost the same as yours:

Tracing route to 69.12.54.12 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2    48 ms    25 ms    29 ms  174.49.192.1
  3    11 ms     9 ms     9 ms  te-0-1-0-2-sur01.york.pa.pitt.comcast.net [68.85.43.245]
  4    10 ms     8 ms     9 ms  te-0-12-0-2-ar03.lowerpaxton.pa.pitt.comcast.net [69.139.194.57]
  5    21 ms    23 ms    19 ms  te-0-6-0-0-ar03.pittsburgh.pa.pitt.comcast.net [69.139.195.241]
  6    26 ms    26 ms    26 ms  pos-4-13-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.91.185]
  7    26 ms    26 ms    26 ms  xe-9-1-0.edge1.NewYork2.Level3.net [4.71.186.33]
  8    31 ms    28 ms    30 ms  vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
  9    31 ms    29 ms    66 ms  ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]
 10    31 ms    45 ms    29 ms  ae-72-72.csw2.Washington1.Level3.net [4.69.134.150]
 11    32 ms    29 ms    28 ms  ae-22-70.car2.Washington1.Level3.net [4.69.149.68]
 12    31 ms    28 ms    28 ms  ge1-1.bbsr1.iad.megapath.net [166.90.148.2]
 13    48 ms    31 ms    30 ms  ae1-0.c00.ash.bb.megapath.net [155.229.57.162]
 14    45 ms    45 ms    45 ms  ae3-10.c01.ash.bb.megapath.net [155.229.57.180]
 15    35 ms    28 ms    33 ms  155.229.101.149
 16    46 ms    45 ms    45 ms  ae1-mxc2.atlngamq.bb.megapath.net [155.229.57.154]
 17    45 ms    44 ms    45 ms  ge-2-1-0-0.c00.atp.bb.megapath.net [155.229.101.194]
 18    45 ms    45 ms    45 ms  ge0-3.a20.atp.bb.megapath.net [155.229.101.30]
 19    74 ms    45 ms    45 ms  69.12.54.12

Lots of players in there - comcast, Level3, megapath. Beyond the general route path, there's no particular spikes that I see.