OMG i get the same thing lately, i live in NY. It goes back down randomly after a while. But it's really annoying.

Ok here's what you do to help get a bad router in your path fixed or bypased.

- Type "command" in your run window to bring up a command dos prompt.
- Do a traceroute to the server in question giving you 120 ping.

ex:
c:\Users\you>tracert server.name.com.or.ip

-You will see a bunch of hops along the path, you'll want to find the one that jumps up a lot from the previous one.

ex:
1 1ms 2ms 3ms mymodem-gateway-ip[192.168.2.1]
2 12ms 14ms 15ms next-hop-isp.com[69.69.69.69]
... many entries later...
11 12ms 14ms 15ms next-hop-isp.com[69.69.69.69]
12 110ms * 115ms bad-chicago-router-BAD[187.187.187.187]
13 112ms 114ms 112ms game-server-chicago[98.98.98.98]

- Now you can send in this traceroute to your ISP, it might take a few calls to get to higher and higher level support but don't give up!!!

There's a good chance if you bug them enough, they will either contact the owner of that bad device or they will eliminate it from their list of allowed hops.

If this fails fret not, it's only because the economy is in the tanker in chicago so people are slow to fix stuff like this. But eventually it'll be replaced, rebooted or completely fail taking it out of your path.

I've been noticing the problem in people I scrim against.
I have optimum's "High speed" internet, he had Fios, both NY, I pinged better than him by about 50-60 on a Chicago server.

I have the same problem and I have a little bit faster fios than you pharoah. Last match I had was on a west coast server and people one state over from me had like 40 ping while I had 140 :/

FYI, Chicago has awful routing and will often start having higher ping during peak hours. I've noticed around 5-9 PST (8-12 Eastern) the routing can be sub par and ping in the hundreds. It's only a 30-40 ping from CA, but I never realized it was that bad from NJ. I understand that Chicago is suppose to be the best for Canadians and East coast (it's the main one), but it sucks.

EDIT: I guess maybe Verizon sucks on the east coast? Verizon is amazing on the west coast at least, never had major problems w/ fios. DSL, yes though.

verizon is just shit. nothing like pinging 100+ to east coast servers when i live on the east coast.

http://www.speedtest.net/result/2260747891.png

i never get bad ping to east coast servers and i have fios as well, thats your internet problem br0

show us your traceroute to these servers. We'll see if it's bad routing or 1 bad hop.

I also have had this problem with Verizon Fios NY. It seems to happen randomly and only to Chicago NFO servers

international routing to Chicago is scrapped also. I'm pinging 300ms+ on servers browser when I usually get 170ms. May share a few common routes. east coast and texas are ok.

said chicago, thats central.

Are you guys really american citizen?

scnet hosts some of the most shitty servers that I route through to get to chicago NFO servers. They bump up my ping by like 80ms pretty much at complete random. Fuck SCNET.

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 3 ms 3 ms L100.NWRKNJ-VFTTP-158.verizon-gni.net [71.187.19
2.1]
3 6 ms 7 ms 6 ms G0-3-3-0.NWRKNJ-LCR-21.verizon-gni.net [130.81.1
77.200]
4 6 ms 6 ms 7 ms ae0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.1
54]
5 6 ms 6 ms 10 ms 0.xe-6-0-2.XL3.EWR6.ALTER.NET [152.63.5.29]
6 31 ms 31 ms 31 ms 0.ge-5-2-0.XL3.CHI13.ALTER.NET [152.63.64.217]
7 28 ms 29 ms 31 ms TenGigE0-4-0-0.GW2.CHI13.ALTER.NET [152.63.66.10
6]
8 108 ms 108 ms 105 ms internap-gw.customer.alter.net [63.84.96.162]
9 104 ms 105 ms 104 ms border5.po2-bbnet2.chg.pnap.net [64.94.32.74]
10 101 ms 101 ms 103 ms c-72-5-195-157.internap-chicago.nfoservers.com [
72.5.195.157]

Trace complete.

I've had fios since it came out and I've never had a problem with it. It seems like nfo is the only chi server messing me up.