SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #12631897
Ticket Status: Remote Problem

PoP: usbos01 - OCCAID Inc. (Boston, Massachusetts)

no IPv6 route from occaid to verizon business
[us] Shadow Hawkins on Saturday, 08 November 2014 17:27:45
I've noticed for some time now that there is no route from OCCAID (and thus the sixxs boston pop) to Verizon Business. In contacting Verizon Business, they indicated that the issue lies on the OCCAID side, lacking either peering or transit that reaches them. Are there contacts at OCCAID who can work with them to resolve this? For example, traceroutes to two routers in front of two Verizon Business data centers: aurora:~$ traceroute6 2600:802:70f::19 traceroute to 2600:802:70f::19 (2600:802:70f::19) from 2001:4830:1100:1fa::2, 30 hops max, 16 byte packets 1 gw-507.bos-01.us.sixxs.net (2001:4830:1100:1fa::1) 2.742 ms 2.47 ms 2.504 ms 2 sixxs-ic-1139-bos.customer.occaid.net (2001:4830:e1:b::2) 2.488 ms 2.583 ms 2.548 ms 3 dcr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 2.72 ms 2.641 ms 2.727 ms 4 dcr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 2.604 ms !N 2.764 ms !N 2.665 ms !N aurora:~$ traceroute6 2600:802::2c traceroute to 2600:802::2c (2600:802::2c) from 2001:4830:1100:1fa::2, 30 hops max, 16 byte packets 1 gw-507.bos-01.us.sixxs.net (2001:4830:1100:1fa::1) 2.803 ms 2.717 ms 2.54 ms 2 sixxs-ic-1139-bos.customer.occaid.net (2001:4830:e1:b::2) 2.601 ms 2.556 ms 2.529 ms 3 dcr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 2.595 ms 2.674 ms 2.705 ms 4 dcr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 2.609 ms !N 2.762 ms !N 2.673 ms !N
State change: remoteproblem Locked
[ch] Jeroen Massar SixXS Staff on Saturday, 08 November 2014 19:53:02
Message is Locked
The state of this ticket has been changed to remoteproblem
no IPv6 route from occaid to verizon business
[ch] Jeroen Massar SixXS Staff on Saturday, 08 November 2014 19:59:38
As Verizon is in the Transit business themselves, I am very sure that they can figure out how to arrange transit to get to the networks they want to. Of course, as they are in that business they likely also try to get everybody to pay for transit, even to their own network... Transit and peering is a fun game, and the large guys (eg Verizon) play a nasty game there. I'll pass it on to OCCAID, but there is likely little they can do.
no IPv6 route from occaid to verizon business
[ch] Jeroen Massar SixXS Staff on Monday, 10 November 2014 17:10:39
OCCAID has requested AS701 / UUNet / Verizon to peer with them, but Verizon seems not interested. As such, if you want connectivity you'll have to talk to your Verizon Account Manager why they do not peer with noc@occaid.org.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker