Still stuck trying to play in Chi/DC servers, pain in the a$$ when most of the CA servers are VA.
Still stuck trying to play in Chi/DC servers, pain in the a$$ when most of the CA servers are VA.
Having the same issues with VA. I'm in NY used to ping 20-30..I get 40 to CHI, 130-150 to VA. Got a new router from VZ, didn't help. They told me it's the website I'm connecting through since I'm getting 50/35. I'm gonna call again today and bring up the more specific server issue. Frustrating..
Ugh, I hope Verizon is fixing this soon, it's horrible playing on 120-180 ping. I'm directing anyone who has Verizon and is experiencing these problems to this thread.
well I am sorry to let you guys all know but Verizon called me back and pretty much told me to pound sand. They said they don't own that router which is garbage as far as i'm concerned. They also tried to argue the fact that all the other devices after that one experience the same latency. I tried to explain its caused by the first router in the bunch but they weren't having it. We can be sure that ID will not pursue this so I'd suggest figuring out a way around it. I likely will be switching ISPs if I can figure out a way out of my contract
Last edited by Sasparillo; 01-24-2013 at 10:49 AM.
I have verizon in Texas and my ping to the QL DFW server has been at least 100 for months now. This has really killed any kind of motivation for playing QL.
Have a nice FALL!
(o^.^o) PIKA PIKA!
The Search Bar is your friend...use it.
Problem? Check here!
Tastyspleen TastyCast
Why CTF4 is bad
Although, I've seen lots of warping lately in VA servers, and I've asked arround and people say they've noticed it too, maybe QL could do something about this, at least check.
I saw on another support forum that turning off your router for a while may change your routing.
I'm going to try it now and then post back with my results.
For reference, I just did another trace:
Tracing route to . [64.34.186.94]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms DMZ.Home [192.168.1.1]
2 1 ms 1 ms 1 ms L100.NWRKNJ-VFTTP-159.verizon-gni.net [96.242.244.1]
3 4 ms 3 ms 4 ms G0-6-2-2.NWRKNJ-LCR-22.verizon-gni.net [130.81.179.202]
4 5 ms 4 ms 5 ms ae0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.209.162]
5 8 ms 8 ms 8 ms so-2-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.17.4]
6 7 ms 7 ms 7 ms 0.so-4-0-2.XT2.NYC4.ALTER.NET [152.63.1.57]
7 31 ms 6 ms 8 ms TenGigE0-7-1-0.GW8.NYC4.ALTER.NET [152.63.21.125]
8 105 ms 110 ms 111 ms tinet-gw.customer.alter.net [152.179.72.122]
9 110 ms 110 ms 112 ms xe-1-3-1.was14.ip4.tinet.net [141.136.108.154]
10 119 ms 115 ms 114 ms peer1-gw.ip4.tinet.net [173.241.128.102]
11 128 ms 123 ms 118 ms 10ge-xe-1-0-1.wdc-sp225-sbdis-1.peer1.net [216.187.120.114]
12 120 ms 122 ms 124 ms . [64.34.186.94]
Trace complete.