lbcguy
join:2010-09-08
Sunset Beach, CA Reviews:
 ·Verizon FiOS
| [Southwest] Poor routing to EA servers from Southern California Im pretty sure ive figured out why all my ea games on xbox live are slow as hell. Turns out when I trace both the EA US servers(159.153.224.230 and 159.153.226.105) my trace jumps all the way across the country and back. I live in Los Angeles and the trace has me going through a server ins Dulles, VA! The ea servers are in redwood city, CA near San Francisco. Why cant i get a straight shot. Im getting tons of jitter and some games like fifa are nearly impossible to play. How can i contact Verizon to get this fixed?
|
|
|
|
Reviews:
·Verizon FiOS
| Re: [Southwest] Poor routing to EA servers from Southern CaliforThe moral of the story. Do not always trust whois or geoip data. Those servers are not in california.
Here is a traceroute from a 100 megabit metro ethernet AT&T connection in Brea, CA:
traceroute to fert07-eqx-iad.ea.com (159.153.224.230), 30 hops max, 46 byte packets
1 192.168.134.1 (192.168.134.1) 0.332 ms 0.484 ms 0.345 ms
2 12.248.40.137 (12.248.40.137) 1.550 ms 2.554 ms 1.419 ms
3 cr84.la2ca.ip.att.net (12.122.129.230) 74.199 ms 71.937 ms 72.027 ms
MPLS Label=16401 CoS=1 TTL=255 S=1
4 cr2.la2ca.ip.att.net (12.123.30.250) 73.246 ms 73.795 ms 71.977 ms
MPLS Label=0 CoS=1 TTL=255 S=0
MPLS Label=16250 CoS=1 TTL=255 S=1
5 cr1.slkut.ip.att.net (12.122.30.29) 72.835 ms 72.940 ms 84.629 ms
MPLS Label=23464 CoS=1 TTL=255 S=0
MPLS Label=16317 CoS=1 TTL=255 S=1
6 cr2.dvmco.ip.att.net (12.122.30.26) 92.425 ms 78.225 ms 76.283 ms
MPLS Label=19382 CoS=1 TTL=255 S=0
MPLS Label=16317 CoS=1 TTL=255 S=1
7 cr1.cgcil.ip.att.net (12.122.31.86) 75.299 ms 73.182 ms 72.415 ms
MPLS Label=24505 CoS=1 TTL=255 S=0
MPLS Label=16317 CoS=1 TTL=255 S=1
8 cr2.wswdc.ip.att.net (12.122.18.22) 72.702 ms 73.754 ms 72.877 ms
MPLS Label=0 CoS=1 TTL=255 S=0
MPLS Label=16317 CoS=1 TTL=255 S=1
9 cr84.wswdc.ip.att.net (12.123.10.250) 73.744 ms 72.220 ms 72.499 ms
MPLS Label=0 CoS=1 TTL=255 S=0
MPLS Label=16317 CoS=1 TTL=255 S=1
10 gar2.ascva.ip.att.net (12.122.134.117) 70.783 ms 70.689 ms 70.668 ms
11 * * *
12 159.153.224.46 (159.153.224.46) 70.942 ms 70.933 ms 70.942 ms
13 fert07-eqx-iad.ea.com (159.153.224.230) 70.998 ms 70.907 ms 70.893 ms
And from a 1000/1000 connection in Irvine, CA:
traceroute to 159.153.224.230 (159.153.224.230), 30 hops max, 60 byte packets
1 10.214.128.1 (10.214.128.1) 0.214 ms 0.209 ms 0.208 ms
2 ip-64-90-32-33.dreamhost.com (64.90.32.33) 2.555 ms 7.626 ms 7.633 ms
3 ip-66-33-201-125.dreamhost.com (66.33.201.125) 0.386 ms 0.401 ms 0.401 ms
4 xe-0-3-0.mpr1.lax103.us.above.net (64.125.187.173) 0.490 ms 0.518 ms 0.518 ms
5 xe-1-2-0.mpr1.lax12.us.above.net (64.125.30.46) 1.364 ms 1.385 ms 1.385 ms
6 above-att.lax12.us.above.net (64.125.12.2) 1.646 ms 1.517 ms 1.515 ms
7 cr2.la2ca.ip.att.net (12.123.30.190) 69.700 ms 68.698 ms 69.694 ms
8 cr1.slkut.ip.att.net (12.122.30.29) 67.146 ms 67.161 ms 67.156 ms
9 cr2.dvmco.ip.att.net (12.122.30.26) 68.681 ms 68.680 ms 68.712 ms
10 cr1.cgcil.ip.att.net (12.122.31.86) 67.921 ms 67.938 ms 68.195 ms
11 cr2.wswdc.ip.att.net (12.122.18.22) 69.572 ms 69.585 ms 69.573 ms
12 cr84.wswdc.ip.att.net (12.123.10.250) 70.581 ms 70.574 ms 70.570 ms
13 gar2.ascva.ip.att.net (12.122.134.121) 74.618 ms 74.578 ms *
14 12.116.77.34 (12.116.77.34) 66.697 ms 66.711 ms *
15 159.153.224.46 (159.153.224.46) 66.950 ms 66.899 ms 66.947 ms
16 fert07-eqx-iad.ea.com (159.153.224.230) 66.705 ms 66.890 ms 66.822 ms
And charter cable:
traceroute to 159.153.224.230 (159.153.224.230), 30 hops max, 40 byte packets
1 10.90.32.1 (10.90.32.1) 8.683 ms 9.561 ms 9.635 ms
2 dtr03rvsdca-tge-0-1-0-0.rvsd.ca.charter.com (96.34.100.64) 9.666 ms 9.699 ms 9.732 ms
3 crr01rvsdca-tge-0-4-0-0.rvsd.ca.charter.com (96.34.96.230) 16.894 ms 17.855 ms 17.964 ms
4 bbr01rvsdca-bue-2.rvsd.ca.charter.com (96.34.2.66) 19.498 ms * *
5 * * *
6 * 216.156.4.2.ptr.us.xo.net (216.156.4.2) 10.261 ms 14.220 ms
7 205.158.79.242.ptr.us.xo.net (205.158.79.242) 15.168 ms 11.266 ms 14.823 ms
8 cr2.la2ca.ip.att.net (12.123.30.190) 93.029 ms 88.649 ms 92.529 ms
9 cr1.slkut.ip.att.net (12.122.30.29) 93.453 ms 91.381 ms 94.786 ms
10 cr2.dvmco.ip.att.net (12.122.30.26) 93.675 ms 93.495 ms 93.561 ms
11 cr1.cgcil.ip.att.net (12.122.31.86) 92.434 ms 89.069 ms 88.532 ms
12 cr2.wswdc.ip.att.net (12.122.18.22) 91.768 ms 94.539 ms 90.015 ms
13 cr84.wswdc.ip.att.net (12.123.10.250) 93.505 ms 92.481 ms 91.389 ms
14 gar2.ascva.ip.att.net (12.122.134.121) 129.134 ms 129.027 ms 126.998 ms
15 12.116.77.34 (12.116.77.34) 86.482 ms 86.941 ms 87.107 ms
16 fert07-eqx-iad.ea.com (159.153.224.226) 224.924 ms !X * *
I would say the PTR records are accurate:
root@dekabutsu: 10:17 PM :~# host 159.153.226.105
105.226.153.159.in-addr.arpa domain name pointer meav5-pub.pt.iad.ea.com.
root@dekabutsu: 10:17 PM :~# host 159.153.224.230
230.224.153.159.in-addr.arpa domain name pointer fert07-eqx-iad.ea.com.
IAD is in Ashburn, VA. Actually here is a traceroute from a 1000/1000 server in Ashburn, VA:
traceroute to fert07-eqx-iad.ea.com (159.153.224.230), 30 hops max, 46 byte packets
1 ip-64-111-124-1 (64.111.124.1) 2.172 ms 2.625 ms 1.921 ms
2 ip-208-113-156-13 (208.113.156.13) 2.130 ms 2.179 ms 2.021 ms
3 apache2-kant.firestone.dreamhost.com (208.113.156.5) 0.209 ms 0.193 ms 0.199 ms
4 xe-2-1-0.er5.iad10.us.above.net (208.185.23.133) 0.226 ms 0.231 ms 0.202 ms
5 xe-1-2-0.er1.iad10.us.above.net (64.125.24.134) 0.241 ms 0.242 ms 0.228 ms
6 192.205.36.125 (192.205.36.125) 1.532 ms 1.495 ms 1.463 ms
7 cr2.wswdc.ip.att.net (12.122.81.250) 4.363 ms 5.931 ms 3.733 ms
MPLS Label=16317 CoS=0 TTL=250 S=1
8 cr84.wswdc.ip.att.net (12.123.10.250) 6.749 ms cr83.wswdc.ip.att.net (12.123.10.110) 5.485 ms cr84.wswdc.ip.att.net (12.123.10.250) 6.841 ms
MPLS Label=0 CoS=0 TTL=250 S=0
MPLS Label=16317 CoS=0 TTL=255 S=1
9 gar2.ascva.ip.att.net (12.122.134.117) 2.496 ms gar2.ascva.ip.att.net (12.122.135.121) 2.391 ms 2.379 ms
10 12.116.77.34 (12.116.77.34) 1.652 ms 1.548 ms 1.496 ms
11 159.153.224.46 (159.153.224.46) 1.509 ms 1.534 ms 1.378 ms
12 fert07-eqx-iad.ea.com (159.153.224.230) 1.780 ms 1.738 ms 1.541 ms
1.7ms from a server in Ashburn. Yup I would have to say they are indeed in Ashburn.
--
300/150 mbit Bonded Verizon FiOS connection FTW! |
|
 xdeadhead220, 221, Whatever It Takes.Premium
join:2000-11-08
Mechanicsburg, PA | reply to lbcguy
n/m replying to wrong thread. my bad |
|
lbcguy
join:2010-09-08
Sunset Beach, CA | reply to houkouonchi
ok that shot down my theory to hell. Can you see any other reason why all my games would be so slow? |
|
lbcguy
join:2010-09-08
Sunset Beach, CA Reviews:
·Verizon FiOS
| Actually i seem to be getting significant packet loss.
|
|
| reply to lbcguy
Packet loss is now the 'norm' for FIOS, get used to it  |
|
Reviews:
·Verizon FiOS
| reply to lbcguy
When i played Battlefield 3 i was unable to play on any servers located in Chicago. the packet loss was horrible. would get routed thru NTT and at peak times I would get on average 10-30% packet loss thru their crappy equipment.
Was only able to play on dallas servers, or west coast servers.
It's not Verizon's fault, would always get .1- 3 ms ping times thru Verizon's network.. They have no control over what happens with your data once it leaves their network. |
|
lbcguy
join:2010-09-08
Sunset Beach, CA | Im getting between 10-50% packet loss to the first hop outside my network though. |
|
tito79
join:2010-03-14
Brewster, NY | That's called throttling maybe verizons network gets slammed where u live |
|
lbcguy
join:2010-09-08
Sunset Beach, CA Reviews:
·Verizon FiOS
| It would appear like verizon is doing some sort of funny business on my network. The packet loss doesn't start until about 5 seconds into the pingtest. If i stop the pingtest for a few seconds, and start it again the same thing happens.
Can verizon legally do this without telling me. This is completly ruining my gameplay. |
|
Reviews:
·Verizon FiOS
| reply to lbcguy
Are you seeing the packetloss throughout the entire route or just the first hop?
Might wanna try restarting your actiontec (if MOCA) or even the ONT by pulling the batter/unplugging.
At first I thought it could just be ICMP being filtered on vz's router but I am seeing no packetloss to that same IP from Ontario doing 20 pings/sec
--- 71.254.160.1 ping statistics ---
800 packets transmitted, 800 received, 0% packet loss, time 41293ms
rtt min/avg/max/mdev = 4.387/6.254/157.432/11.406 ms, pipe 3
If retarting your ONT doesn't work I would have vz send out a technical as your ONT or router probably needs replacing.
--
300/150 mbit Bonded Verizon FiOS connection FTW! |
|
lbcguy
join:2010-09-08
Sunset Beach, CA Reviews:
·Verizon FiOS
| I just had the router replaced this month and ONT replaced a couple months ago. If ICMP was being filtered wouldnt i get 100% packet loss instead of 50%. Also as i mentioned the first few seconds when i start a ping test there is no packet loss then it starts about 5 seconds in. Wouldn't this suggest that verizon is doing some sort of throttling? I am on ethernet btw |
|
Reviews:
·Verizon FiOS
| said by lbcguy:I just had the router replaced this month and ONT replaced a couple months ago. If ICMP was being filtered wouldnt i get 100% packet loss instead of 50%. Also as i mentioned the first few seconds when i start a ping test there is no packet loss then it starts about 5 seconds in. Wouldn't this suggest that verizon is doing some sort of throttling? I am on ethernet btw
Depends on how its being done There are rulse that just only allow a certain number per second after X amount have been done which can cause behavior with that but again if your getting packetloss at the end-destination too (and thus probably every hop after the first one) then that is a problem.
Also pretty much already ruled out possible filtering since I am not seeing loss to the same IP but yes its totally possible to see behavior like that depending on how the ACL's are setup on the router.
--
300/150 mbit Bonded Verizon FiOS connection FTW! |
|
lbcguy
join:2010-09-08
Sunset Beach, CA | How can i make sure my router is configured correctly? The verizon guy set it up and i haven't touched it so it should be on default settings still. |
|
 birdfeedrPremium,MVM
join:2001-08-11
Warwick, RI
kudos:8 | reply to lbcguy
said by lbcguy:the first few seconds when i start a ping test there is no packet loss then it starts about 5 seconds in. You said "a ping test." Question: all ping tests?
Is the first hop that's experiencing ping variation and/or loss the same all the time? Not sure based on your ping plots. |
|
lbcguy
join:2010-09-08
Sunset Beach, CA Reviews:
·Verizon FiOS
| I get no packet loss to my router but i get between 6% and 1% packet loss to the first hop. So the problem is definitely between ONT and first hop if what i've read online is correct. Last night for about an hour i was getting .5% packet loss and my games were playable, then it shot up to 1.2% and i start getting weird glitches, micro pauses, buttons not registering. I'd say 90% of the time im in the 2-3% loss which is impossible to play.
Im calling Rick Worthington(supposedly he is an upper tier fios support guy) tomorrow to see if i can get this fixed. Ill update this thread if anything happens. |
|
