said by serge87:said by SDunused:when i run a tracert to that 100.41.221.245 it comes off as my 2nd hop but when i run a tracert to google my 2nd hop is my CO equipment, what does that even mean?
why is 100.41.221.245 my 2nd hop only when running a tracert to it
I'm guessing that the location of that Verizon server is close enough to you(NYC or very near) that the route it takes(internally) is much shorter and direct than the route to Google which would need to reach a Verizon edge router that is closest(per BGP) to an external Google server.
BTW, what program do you use to produce those results?
MTR and Command Promt for tracert's and dslreports own line quality tests (minus the quality for fios)
the hop marked in red is the 100.41.221.245 IP, something weird must be going on.
since you stated if i run a tracert to it and it's coming up as the closest hop to me yet it's getting 30-70ms around peak time but 10ms non-peak time, really makes me wonder what that hop is..
Tracing route to xe-8-1-2-0.NYCMNY-VFTTP-352.verizon-gni.net [100.41.221.245]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 1 ms 2 ms 75 ms xe-8-1-2-0.NYCMNY-VFTTP-352.verizon-gni.net [100.41.221.245]
Trace complete.
Tracing route to 159.153.114.150 over a maximum of 30 hops
1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 9 ms 19 ms 5 ms lo0-100.NYCMNY-VFTTP-352.verizon-gni.net
[100.12.212.1]
3 5 ms 6 ms 6 ms T1-12-0-6.NYCMNY-LCR-21.verizon-gni.net
[130.81.98.136]
4 * * * Request timed out.
5 4 ms 6 ms 6 ms 0.ae1.BR3.NYC4.ALTER.NET [140.222.229.97]
6 * * * Request timed out.
7 * * 15 ms ae-3-80.edge2.Washington1.Level3.net
[4.69.149.142]
8 25 ms * * ae-3-80.edge2.Washington1.Level3.net
[4.69.149.142]
9 11 ms 13 ms 10 ms 4.79.23.202
10 109 ms 108 ms 113 ms 159.153.92.74
11 108 ms 109 ms 108 ms 159.153.114.150
Trace complete.
after doing extensive research i've found the level3 is the culprit of the horrible routing to EA's battlefield servers. those edge2 hops have 20-50% packet loss, i called level3 and they said those ip's are under verizon's contract with them and they see the issue but they require verizon to call in and create a ticket with them and they'd have it fixed in 1-2 days but see as simple as that is verizon will not even come close to performing such a task.
p.s those servers are all the way in california which explains the latency, usually they're around 70ms which is reasonable since i'm in new york but with the issues latency is going up to the 100's
west coast EA servers are using level3 which verizon is having issues with and east coast EA servers are using cogent which verizon is ALSO having issues with.
seems like a never ending cycle of issues when it comes to fios, trouble with capacity and CO's, trouble with peering and malicious throttling not to mention business class static-routing issues on top of it all make one very
un-optimized "fiber" experience.