2009 IPv6 Address Use Report
Since 2005, bgpexpert.com been compiling an IPv4 address use report every year. With the start of the new decade, this is a good moment to start doing the same thing for IPv6.
This page shows the amount of IPv6 space given out by RIR and by year, while this page shows the amount of IPv6 address space by country. Both these pages are updated weekly from the delegation data that the RIRs publish on their FTP servers.
The full report is here
Hurricane Electric Network Expansion & IPv6 Deployment Growth
* Hurricane Electric has expanded to Tokyo, Stockholm, and Zurich
Hurricane Electric now connects over 500 IPv6 networks and announces over
1000 IPv6 customer prefixes.
Hurricane Electric has over 4500 BGP sessions with over 1100 IPv4 and
IPv6 networks at 29 different exchange points in North America, Europe,
and Asia.
Updated network map:
http://he.net/Hurricane_Electric_Geographic_Network_Map.jpg
* New tunnel servers live in Tokyo, Stockholm, and Zurich
You are welcome to log in and reconfigure your tunnel if you like.
Chosing a closer tunnel server will improve your performance. You will
receive a different /64 and /48 if you chose to do this.
* IPv6 Deployment Growth
The global IPv6 routing table has passed 2000 IPv6 prefixes.
There are now over 1500 IPv6 glue records in the TLD zone files. The
addition of IPv6 glue records at the TLD level is a good gauge of
hosting infrastructure IPv6 growth, since it indicates operational
commitment on the part of individual nameserver operators.
Source: http://bgp.he.net/ipv6-progress-report.cgi
* New Exchange Point Connections
We have added exchange point connections to Equinix Tokyo, NETNOD,
SOLIX, and Equinix Zurich.
Where ever possible, we prefer native IPv6 BGP sessions with your
network directly on our core routers at any facilities we have in common
or via any exchange points we might have in common.
Stopwatch Rollout – 2hrs from Application to live
Andy Davidson documents his 2 hour IPv6 deployment
"On Wednesday at 2:30PM uk time, I applied for a /32. One hour later, we were allocated 2a02:c30::/32. I straight away assigned a /48 for our network infrastruture, and another for our production hosting lan, another for our development hosting lan. From these /48s, several /64s were reserved, one for router loopbacks, another for point to point links, more for individual hosting applications. An hour later, this was implemented on our network - routers had loopbacks, and a v6 IGP was up and running, and working. I filed a ticket with our upstreams, and the first announcement was turned up minutes later - check BGPlay for exact times. Around 2 hours after making our application to RIPE, we were participants on the IPv6 internet."
[ source www.andyd.net ]
