The Hurricane Electric network covers the US and major locations in Europe. Each location is IPv6 enabled and provides IPv6 transit services in both native and dual stack formats. As the network expands to include additional geographic locations, it will always expand as a fully capable IPv6 network.
There are various ways to compare Hurricane Electric’s IPv6 backbone to other IPv6 backbones. One of the most important metrics is the number of BGP adjacencies at the edge of the network. The greater the adjacency, then the backbone has higher connectivity with the rest of the Internet. In the IPv6 world, this is even more important than in the IPv4 world because disconnected pockets of connectivity can cause enormous disruption for end users. Hurricane Electric’s IPv6 backbone has the number-one count of BGP adjacencies.
Top Twenty IPv6 Backbones Number of BGP Peering Adjacencies Measured 4/6/2008 through 4/30/2008
# BGP Peering Adjacencies
Global Crossing (AS3549)
Asia Netcom (AS18084)
Canble & Wireless (AS1273)
ODN Softbank (AS4725)
IPv6 Backbone Provider
Data collected from http://bgp.potaroo.net/v6/as6447/bgp-as-adj.txt For more information and additional statistics please visit http://he.net/
http://he.net/bgp-as-adj.pdf Graph showing BGP adjacencies for the top-twenty IPv6 backbones April 2008
That last graph shows a pictorial view of the data from Geoff Huston’s website. The data is collected from live IPv6 Internet routers.
Native IPv6 is available to all Hurricane Electric colocation, transit customers, and root dedicated server customers
Native IPv6 is available on the same port as IPv4 at no additional charge.
You may request IPv6 address allocations by sending email to firstname.lastname@example.org .
If you operate a router, you may request a /48, otherwise request a /64 per port.
In the IPv6 world, as stated at the beginning of this document, there are 128 bits included in the IPv6 header. Addresses have four times to number of bits that an IPv4 header would have. This is where the 79 billion billion billion number comes from. Its 2128 divided by 232 and yet best practices, as stated in RFCs, shows that IPv6 address allocations are not the same as in IPv4. The allocation on an individual
IPv6 at Hurricane Electric © 2008 http://he.net/
Page 7 of 9 April 2008