For about the past 96 hours, I've had broken links outbound and inbound on traceroutes. I was told Wednesday evening that there was a 'core router' problem in my immediate area, and that it'd be fixed within 12 hours, and that I'd be attached to the 'larger ticket' of those who'd had the same complaint.
According to Verizon, the problem's 'fixed,' but I'm still showing broken links in the chain:
C:\Users\pbdye>tracert www.verizon.com
Tracing route to e10696.g.akamaiedge.net [23.196.56.206]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 17 ms 7 ms 6 ms L100.WASHDC-VFTTP-100.verizon-gni.net [173.66.23
5.1]
3 9 ms 9 ms 9 ms G101-0-0-23.WASHDC-LCR-22.verizon-gni.net [100.4
1.135.166]
4 * * * Request timed out.
5 * * * Request timed out.
6 47 ms 11 ms 11 ms 0.ae2.BR2.IAD8.ALTER.NET [140.222.229.169]
7 10 ms 11 ms 10 ms 64.212.107.57
8 10 ms 15 ms 9 ms lag17-30G.csr2.DCA3.gblx.net [67.16.149.161]
9 15 ms 13 ms 12 ms akamai.ethernet14-1.csr2.dca3.gblx.net [64.214.1
29.106]
10 12 ms 12 ms 11 ms a23-196-56-206.deploy.static.akamaitechnologies.
com [23.196.56.206]
Trace complete.
I use verizon.com because I want to spend as little time outside the Verizon network as possible. I know hops 4 and 5 are still within the FiOS network because I pretty routinely traceroute to find latency issues. But trying to explain this to a first-tier tech is getting me nowhere, because all they're concerned with is 'does it work?,' and when the answer is 'yes,' anything that follows that seems to take on the tone of Charlie Brown's teacher.
They've already released my IP address, 'reset my router' (something I already did)...I'm trying to get to someone who actually *administrates* the FiOS network.
