When I first moved to Seattle (I'm 20 miles south, in Auburn) I signed up for Comcast (XFinity Blast package, 25 down, 5 up). It's the only ISP that's available where I live. This was the beginning of June 2011, and I was getting 13 ping to Seattle servers. Now I get 65+ ping to Seattle servers, and have since sometime in July or August when everything just seemed to go south. Does anyone know if id switched hosters or hosting plans for their servers? Did anyone else notice major ping issues in the last few months? I was just on a seattle duel server, and got the server ip with the clientinfo command (or maybe client_info, don't remember), and did a tracert to it:
Tracing route to 22.214.171.124 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 7 ms 8 ms 126.96.36.199
3 39 ms 7 ms 7 ms ge-3-18-ur04.federalway.wa.seattle.comcast.net [188.8.131.52]
4 100 ms 35 ms 34 ms ae-11-0-ar03.seattle.wa.seattle.comcast.net [184.108.40.206]
5 9 ms 9 ms 9 ms pos-1-11-0-0-cr01.seattle.wa.ibone.comcast.net [220.127.116.11]
6 26 ms 29 ms 27 ms 18.104.22.168
7 37 ms 36 ms 35 ms ae-31-51.ebr1.Seattle1.Level3.net [22.214.171.124]
8 27 ms 31 ms 29 ms ae-7-7.ebr2.SanJose1.Level3.net [126.96.36.199]
9 30 ms 31 ms 30 ms ae-72-72.csw2.SanJose1.Level3.net [188.8.131.52]
10 26 ms 27 ms 27 ms ae-22-70.car2.SanJose1.Level3.net [184.108.40.206]
11 28 ms 31 ms 27 ms ge2-2.bbsr1.sjc.megapath.net [220.127.116.11]
12 45 ms 47 ms 47 ms ge-0-1-3-mxc2.snvacaid.bb.megapath.net [18.104.22.168]
13 27 ms 27 ms 27 ms ae0-mxc1.snvacaid.bb.megapath.net [22.214.171.124]
14 47 ms 47 ms 47 ms 126.96.36.199
15 45 ms 47 ms 47 ms ge3-0-0.m10.stl.bb.megapath.net [188.8.131.52]
16 60 ms 58 ms 59 ms ve191.ge0-1-0.core1.lax.megapath.net [184.108.40.206]
17 57 ms 58 ms 71 ms 220.127.116.11
From what I understand 3 packets are sent/returned at each hop, so the 3 columns is the time it took for each of the 3 packets to go round trip.
There's that weird 100ms anomaly for the 1st packet on the 4th hop, but it went away when I did another tracert. It seems like the last hop (17, the actual QL server) is the slowest hop in the chain. If I was a smart man, I would have done a tracert back in the glorious days when I got 13 ping to Seattle servers. That why I'd be able to compare it with what's happening now.
For $100/mo I could upgrade my service to 100 down, 10 up. But bandwidth isn't speed, it's capacity. A fatter pipe just means more data at once, it doesn't have anything to do with latency. Though, it could potentially be packaged with other priority routing and better treatment from the ISP.
My current plan is:
- call ISP see if there's a problem with routing
- possibly upgrade to the better service for a month or 2 and see if it improves
Anyone else have any advice?
I haven't played any other games in a long time, but I'll hop in some cs games or something today to see how my ping is for other servers.