Verizon and VA servers

[chernobyl]

No change for me.

[prettydamnotbad]

Yeah, there's absolutely nothing that QL can do about this if it's your ISP that's the issue. You'd have to contact them yourself if you've got that much of an issue with it.

There's plenty QL can do about it. For starters, they could invest in better servers (fat chance of that happening right?! LOLZ). There are plenty of Quake 3 servers in Texas where I get my normal 15 ms ping.

[Dr_Mr_Ed]

But it's not the servers, it's the routing to the servers. So "better" isn't going to help. "Different" might help because the routing would change. Again, it's an ISP issue - a combination of yours and theirs. Moving data centers is a possibility, but usually there are contractual obligations that prevent jumping around.

[pikaluva13]

But it's not the servers, it's the routing to the servers. So "better" isn't going to help. "Different" might help because the routing would change. Again, it's an ISP issue - a combination of yours and theirs. Moving data centers is a possibility, but usually there are contractual obligations that prevent jumping around.

Plus, changing server providers might make it worse. Changing ISP providers doesn't guarantee better routing.

[MexicanPadre]

but people who have other ISPs in the same area seem to ping better...

[pikaluva13]

Just noticed I typo'd. I meant to say *server* providers.

[drastic56]

So today i began pinging normal in VA servers. 30-40's, played a few games without any problems. Hopefully the routing problems fixed on my end.

[_zoom]

So today i began pinging normal in VA servers. 30-40's, played a few games without any problems. Hopefully the routing problems fixed on my end.

I noticed the same, however it still spikes now and then

[Scorpwolf]

so i contacted verizon again, showed them some traceroutes and told them about the alter.net problem that other users are having problems with..but of course they didn't do anything about it..they told me i need to do some port configuration just for this game and gave me a number to call..turns out i need to pay for it for them to do it..so i told them no thanks..lol

Does port forwarding even work for this game..would it make any difference or are they just ********ing me?..and does anyone else get lag even when the ping is low?..my 50 ping feels like 80 usually, everyone is choppy and i get thru shots all over the place (i only play insta btw)..the game just feels like total crap most of the times..i guess at this point my only other option would be to switch isp..

Here are some traceroutes..


1 <1 ms <1 ms 3 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 7 ms 7 ms L100.TAMPFL-VFTTP-42.verizon-gni.net [173.65.36.
1]
3 8 ms 9 ms 10 ms G0-3-3-6.TAMPFL-LCR-21.verizon-gni.net [130.81.1
90.248]
4 8 ms 10 ms 10 ms so-2-0-0-0.TPA01-BB-RTR1-verizon-gni.net [130.81
.28.212]
5 14 ms 15 ms 14 ms 0.xe-7-0-0.BR1.MIA19.ALTER.NET [152.63.85.158]
6 15 ms 17 ms 17 ms 204.255.168.14
7 13 ms 17 ms 17 ms ae-3.r21.miamfl02.us.bb.gin.ntt.net [129.250.4.2
50]
8 44 ms 42 ms 42 ms ae-7.r20.dllstx09.us.bb.gin.ntt.net [129.250.3.1
74]
9 42 ms 42 ms 42 ms ae-0.r21.dllstx09.us.bb.gin.ntt.net [129.250.2.5
9]
10 64 ms 109 ms 64 ms ae-4.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.2
01]
11 66 ms 69 ms 63 ms ae-2.r06.chcgil09.us.bb.gin.ntt.net [129.250.4.2
02]
12 71 ms 69 ms 67 ms xe-0-0-0-12.r06.chcgil09.us.ce.gin.ntt.net [129.
250.193.2]
13 75 ms 72 ms 70 ms ae11.cr1.ord6.us.scnet.net [204.93.204.73]
14 71 ms 77 ms 76 ms ae4.ar6.ord6.us.scnet.net [204.93.204.67]
15 74 ms 72 ms 69 ms as36352.xe-2-0-2.ar6.ord6.us.scnet.net [50.31.15
4.182]
16 72 ms 72 ms 71 ms 10ge-1-3-1.gf146.cr1.chi.colocrossing.com [206.2
17.137.250]
17 72 ms 71 ms 70 ms 50.113.21.199.hypernia.com [199.21.113.50]



1 <1 ms 2 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 6 ms 7 ms L100.TAMPFL-VFTTP-42.verizon-gni.net [173.65.36.
1]
3 9 ms 7 ms 7 ms G0-3-3-6.TAMPFL-LCR-22.verizon-gni.net [130.81.1
90.250]
4 9 ms 10 ms 9 ms so-2-0-0-0.TPA01-BB-RTR2.verizon-gni.net [130.81
.28.214]
5 28 ms 30 ms 29 ms ge-1-0-0-0.ATL01-BB-RTR2.verizon-gni.net [130.81
.17.48]
6 30 ms 29 ms 30 ms 0.ge-7-1-0.XT2.ATL4.ALTER.NET [152.63.81.1]
7 44 ms 42 ms 44 ms 0.xe-4-1-2.XL4.IAD8.ALTER.NET [152.63.32.21]
8 43 ms 47 ms 42 ms GigabitEthernet5-0-0.GW8.IAD8.ALTER.NET [152.63.
33.97]
9 44 ms 44 ms 45 ms tinet-gw.customer.alter.net [152.179.50.30]
10 138 ms 87 ms 87 ms xe-3-0-0.dal33.ip4.tinet.net [89.149.183.53]
11 86 ms 89 ms 87 ms peer1-gw.ip4.tinet.net [77.67.71.30]
12 92 ms 92 ms 92 ms 10ge-ten1-2.sat-8500v-cor-1.peer1.net [216.187.1
24.78]
13 94 ms 97 ms 94 ms 10ge.xe-0-0-1.sat-8500v-sbdis-1.peer1.net [216.1
87.124.66]
14 94 ms 96 ms 98 ms 69.174.243.25



1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 7 ms 7 ms L100.TAMPFL-VFTTP-42.verizon-gni.net [173.65.36.
1]
3 25 ms 26 ms 47 ms G0-3-3-6.TAMPFL-LCR-22.verizon-gni.net [130.81.1
90.250]
4 11 ms 9 ms 22 ms so-4-0-0-0.TPA01-BB-RTR2.verizon-gni.net [130.81
.199.28]
5 13 ms 14 ms 15 ms 0.xe-8-0-0.BR1.MIA19.ALTER.NET [152.63.85.162]
6 220 ms 234 ms 219 ms 204.255.168.30
7 138 ms 208 ms 218 ms te3-7.ccr02.mia01.atlas.cogentco.com [154.54.80.
49]
8 42 ms 42 ms 42 ms te0-4-0-4.mpd22.atl01.atlas.cogentco.com [154.54
.42.109]
9 214 ms 207 ms 204 ms te3-1.ccr01.ind01.atlas.cogentco.com [154.54.7.7
8]
10 50 ms 49 ms 50 ms 38.104.214.74
11 52 ms 49 ms 49 ms quakelive.atheos.net [38.123.6.11]