This morning, I noticed that I was able to successfully ping and tracert to IP 10.0.0.1. That is supposedly a non-routing IP address. I VPN to a company that uses the 10.0.0.x for their internal LAN, but I was not connected to the VPN at the time.
Another co-worker working from his home office also has Verizon FIOS, and he too says the 10.0.0.1 address is resolving. Here is my tracert:
>tracert 10.0.0.1
Tracing route to VPN-FCC [10.0.0.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router [192.168.249.1]
2 5 ms 4 ms 4 ms L100.PHLAPA-VFTTP-91.verizon-gni.net [98.114.133.1]
3 7 ms 7 ms 4 ms G0-6-2-5.PHLAPA-LCR-21.verizon-gni.net [130.81.131.136]
4 5 ms 17 ms 5 ms 130.81.199.18
5 25 ms 27 ms 26 ms 0.xe-4-0-2.XL3.CHI13.ALTER.NET [152.63.65.126]
6 27 ms 26 ms 27 ms 10.0.0.1
Trace complete.
Anybody else notice this? I have restarted both my PC and my Actiontec router, but it made no difference. I'm fairly certain this problem is upstream and it is Verizon that is messed up.