Often cited as one of the reasons of slow IPv6 uptake, is the lack of Internet resources and services that require IPv6 for operation or access. In other words, “why bother implementing IPv6, if every website is accessible on IPv4 anyways?”

* (remove A-records from the primary visitor-facing domains and subdomains, leaving AAAA-records in place; optionally turn off listening on IPv4 sockets in software)

Participating websites and services will go IPv6-only* for 24 hours starting 00:00 UTC on 8th June 2013.

Raised awareness about the need to transition to IPv6; introducing expectation that there can be useful IPv6-only resources on the general Internet; wide testing and possible proposals of improvement to the web browser behaviour in case when a target domain has only AAAA-record, but there is no local IPv6 connectivity.

Possible loss of up to 95% of daily website visitor counts for 24 hours at participating websites; actual impact is difficult to estimate, as many visitors can be actually IPv6 capable, but won't connect over IPv6 in case a website also has IPv4 (e.g. Teredo, 6to4 tunneling).

With the appropriate preparations (instructions on obtaining v6 connectivity) can be somewhat mitigated.

Lasting effect (sustained visitor count loss after the event finishes) is expected to be minimal or none.