Subject updated to be less wrong. On Thu, 3 Sep 2009, Peter Beckman wrote:
I can't reach 83.222.0.0/19 from Verizon, but I can via Cox Communications Business Fiber as well as Level3. Dies at a peering point it seems:
HOST: home Loss% Snt Last Avg Best Wrst StDev 1. mph 0.0% 20 0.7 0.6 0.5 0.7 0.1 2. 10.1.41.89 0.0% 20 2.3 3.6 1.7 26.4 5.6 3. G2-0-3-891.WASHDC-LCR-08.ver 0.0% 20 2.1 1.9 1.6 2.2 0.2 4. so-1-1-0-0.RES-BB-RTR2.veriz 0.0% 20 2.3 2.4 2.2 2.8 0.1 5. 0.so-6-1-0.XL4.IAD8.ALTER.NE 0.0% 20 2.8 2.8 2.6 3.0 0.1 6. 0.xe-8-1-0.BR1.IAD8.ALTER.NE 0.0% 20 5.1 8.4 3.0 40.3 9.4 7. 64.212.107.157 0.0% 20 203.2 14.0 3.0 203.2 44.6 8. ??? 100.0 20 0.0 0.0 0.0 0.0 0.0
Hop 7 alternates between 64.212.107.157 (GBLX) and 204.255.169.202 (MCI dba Verizon) and dies after that. 83.222.32.0/19 seems to route correctly.
I've called both the Verizon NOC and UUNET NOC, talked to friendly people who told me nicely to go talk to someone else. My next step will be to contact ip-noc@verizonbusiness.com as per the netops NOC list. Any IPs in 83.222.0.0/19 that ARE reachable on L3 and Cox are not reachable on Verizon. Please note I'm not doing traceroutes to 83.222.0.0 or 83.222.0.0/19. I'm tracing hosts that are known to be up and traceable, and are within this block. An interesting side note -- I can't get to retn.net either on Verizon, but can elsewhere, which is 81.222.33.89. As an end user smart enough to figure out why a website isn't loading, it is a GIANT PAIN and next to impossible to report a network issue when you are a non-customer, non-ISP employee. This is why I posted this on NANOG, because I'm trying to promote dialog between people concerning the operation of IP networks. Verizon asked me to reboot my router. I hung up. Beckman --------------------------------------------------------------------------- Peter Beckman Internet Guy beckman@angryox.com http://www.angryox.com/ ---------------------------------------------------------------------------