The total upstream connectivity at the ISPs at where the PoPs are located far exceeds the local interface connectivity. The PoPs with 10GE interfaces then also tend to be the NRENs which have way more than 10GE available. People though who want to push several tens of megabits continuously are better off in geting native IPv6 from their local ISP And yes, the PoPs are underused, but that is mostly I guess because there is not that awful lot of content on IPv6, even though it changes already with this, the heavy traffic hitters remain BitTorrent and NNTP which are not affected by this "launch". And they have been for a long time already and quite a few have been using our resolver caches which have been giving out AAAA for various domains already. Also, youtube as IPv6 enabled for the content part for nearly a year already and that is the biggest chunk of traffic for that, at least a lot more than search traffic. That is not true, you forget that most people still use Windows and that Windows since Vista are Teredo enabled per default. And even a lot of other users already have IPv6 have enabled IPv6 on XP as they are using BitTorrent clients that enable it easily for them. There is one catch though with many platforms, in that they tend to not prefer IPv6 connections eg on Teredo, or apply Happy Eyeball-alike techniques. And on top of that, as I noticed yesterday in a hotel, some networks use OpenDNS which seem to drop requests for AAAA and rewrite it to their search engine. Fortunately 8.8.8.8 is always available as a last resort to circumvent that. Another catch to note is that people with IPv6 stacks but no connectivity might now be AAAA receiving answers for their DNS queries and as their connectivity is broken or their DNS resolver drops to requests can have issues because of this quite major change. This apparently is only 0.1% of the userbase though, and those folks likely are now either fixing their stuff or contacting their helpdesks.