FiOS Internet

[#1]

I'm in Dallas and ping to some local Dallas servers has gotten really bad recently. It went from 8 to 45+.

I've tried talking to Level3 about this, but they're completely unresponsive and they refuse to do anything about it.

Where do I go from here?

Trace route:

[~]$ traceroute 69.174.243.26 []
traceroute to 69.174.243.26 (69.174.243.26), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 2.957 ms 1.200 ms 1.168 ms
2 l100.dllstx-vfttp-75.verizon-gni.net (173.64.201.1) 5.865 ms 7.044 ms 5.685 ms
3 g0-3-875.dllstx-lcr-08.verizon-gni.net (130.81.129.106) 6.567 ms 7.398 ms 7.176 ms
4 so-5-1-0-0.dfw01-bb-rtr2.verizon-gni.net (130.81.29.182) 7.104 ms 14.012 ms 6.548 ms
5 0.ae2.br2.dfw13.alter.net (152.63.2.230) 8.669 ms 8.658 ms 8.788 ms
6 ae7.edge2.dallas3.level3.com (4.68.62.33) 8.283 ms 8.172 ms 8.434 ms
7 ae-4-90.edge9.dallas1.level3.net (4.69.145.208) 10.166 ms
ae-2-70.edge9.dallas1.level3.net (4.69.145.80) 8.725 ms 8.405 ms
8 peer-1-netw.edge9.dallas1.level3.net (4.59.118.6) 33.390 ms 35.434 ms 36.502 ms
9 10ge-ten1-3.sat-8500v-cor-2.peer1.net (216.187.124.178) 40.087 ms 41.169 ms 41.126 ms
10 10ge.xe-1-0-1.sat-8500v-sbdis-1.peer1.net (216.187.124.82) 44.407 ms 48.098 ms 43.723 ms
11 * * *

[#2]

See if you can get Verizon to talk to Level3. It's clearly a problem with them and if they are notified about their network issue by one of the companies they peer with, they will be more likely to fix it.

Those large jumps in latency seem to be common with Level3 though. Often times than sometimes up to a few weeks to fix problematic hops. Beats me as to why it takes that long but normally their network is rather robust.

[#3]

How do I go about contacting Verizon about this?

[#4]

where is the latency?

am I missing something   ?   o_O 

Sub 100 MS trace routes will get little to no attention from an operator for obvious reasons.