Follow Us

We use cookies to provide you with a better experience. If you continue to use this site, we'll assume you're happy with this. Alternatively, click here to find out how to manage these cookies

hide cookie message

IPv6 traffic plummets after global test day

There’s no place like 0:0:0:0:0:0:0:1

Article comments

The day after World IPv6 test Day, it looks as if the Internet 1.0 has been getting back to its IPv4-borne normality. Monitoring centres report that the IPv6 has one again retreated to the shadows with traffic “falling off a cliff.”

For the 24-hour test period, which ran from midnight UTC (ET+4) on 8 June, IPv6 traffic appears to have roughly doubled, as perfectly illustrated by the spike recorded by network infrastructure company Akamai, reaching perhaps fractions of a percent at peak.

Saying that IPv6 traffic at least ‘doubled’ is not the whole story however and contains good and bad news for those who hope that IPv6 migration can happen sooner rather than later. Indeed, traffic doubled but mainly because it was already at incredibly low levels that barely registered. Privately, many engineers are not even convinced that it is possible to accurately measure IPv6 traffic at all so insignificant is its presence.

On a positive note, measuring traffic against the Internet as a whole is misleading because some parts count more than others. Google’s servers are a part of the Internet that count more than most and the company recorded IPv6 traffic as hitting as much as 0.3 percent, a huge jump for a protocol that until a day ago had barely been used to do more than carry out engineering research.

If 8 June proved IPv6 can survive the real world, the problem is what appears to have happened next. Hopes that content delivery networks (CDNs) would keep the protocol switched on have been dashed, with every recording centre registering IPv6 melting away from the first minutes of 9 June as rapidly as it had advanced only the day before.

Akamai’s graph shows the plummet, most of it in North America where the most enthusiastic big-brand participants – Google, Netflix, Yahoo, Bing and Verizon – seemed to have just as eagerly flipped the switch back to the ‘off’ position, job done, the first minute they could.

“It’s going to be a long slog to IPv6. But for a 24-hour period the IPv6 network looked like a regular network,” says a reflective Rob Malan, co-founder and CTO of Net security company, Arbor Networks.

Until 8 June, IPv6 traffic had been categorised as “other”, says Malan, which was a polite engineering way of saying that it was not doing anything useful that anyone could explain. Throughout 8 June, for the first time in history, it suddenly shifted useful packets, a huge advance it its way.

“For a brief moment the IPv6 network looked like the Internet,” says Malan. “IPv4 has got a long life ahead. With scarcity will come better allocation of resources. We are going to be able to get away with IPv4 for a long time,” he adds as a heavy qualification.

Others remain more upbeat. “Despite the low traffic volumes I believe it was a success,” says Blue Coat Systems’ chief scientist and acknowledged IPv6 expert, Qing Li. “We are talking about IPv6 now. That is the success – it is no longer a backroom discussion.”

“IPv6 was designed not just to solve the addressing issue but to make packet routing much more efficient,” points out Li, who believes that its supremacy is only a matter of time. Until then, people need to prepare to run the two network addressing schemes in parallel.

For many participants, however, World IPv6 Day has come and gone and they have in different ways been left to pick up the scattered packets, musing over what it all meant beyond a welcome burst of publicity.

“I keep thinking of the old wagon trains that left for California. It took forever for them to get to the promised land. It’s going to be a long, hard slog,” says Arbor’s Malan.


More from Techworld

More relevant IT news


dourscot said: The story doesnt imply that IPv4 was turned off for the reason you state And who said IPv6 had to be turned offThe loopback address is meant to be IPv6 not IPv4 That would be 127001

v6 pusher said: The byline should have said Theres no place like 0000 The address used above - 00000001 is the loopback address in v6 not home in v4This story is misleading since the test required turning off v6 after those 24 hours to measure how combined v4v6 traffic was compared to v4 only The story seems to suggest that the reason it was turned off was that the sites had problems w v6 which was not the case

Send to a friend

Email this article to a friend or colleague:

PLEASE NOTE: Your name is used only to let the recipient know who sent the story, and in case of transmission error. Both your name and the recipient's name and address will not be used for any other purpose.

Techworld White Papers

Choose – and Choose Wisely – the Right MSP for Your SMB

End users need a technology partner that provides transparency, enables productivity, delivers...

Download Whitepaper

10 Effective Habits of Indispensable IT Departments

It’s no secret that responsibilities are growing while budgets continue to shrink. Download this...

Download Whitepaper

Gartner Magic Quadrant for Enterprise Information Archiving

Enterprise information archiving is contributing to organisational needs for e-discovery and...

Download Whitepaper

Advancing the state of virtualised backups

Dell Software’s vRanger is a veteran of the virtualisation specific backup market. It was the...

Download Whitepaper

Techworld UK - Technology - Business

Innovation, productivity, agility and profit

Watch this on demand webinar which explores IT innovation, managed print services and business agility.

Techworld Mobile Site

Access Techworld's content on the move

Get the latest news, product reviews and downloads on your mobile device with Techworld's mobile site.

Find out more...

From Wow to How : Making mobile and cloud work for you

On demand Biztech Briefing - Learn how to effectively deliver mobile work styles and cloud services together.

Watch now...

Site Map

* *