These graphs show the evolution of default protocol, v6 address types, and average bandwidth in Malaysia over time. They are generated using the data collected by tens of thousands of tests that are done monthly at the ipv6-test.com connection test page, and are updated on a monthly basis.
The graph below shows the evolution of IPv6 support vs IPv4 for all our connection test. The numbers are percentages, so we can expect almost 100% of hosts supporting IPv4 with a slow growth for IPv6.
|ISP||IPv6 tests count|
|8.||Tm Vads Dc Hosting||6|
The graph below shows the evolution of IPv6 support vs IPv4 for unique users of our connection test. The numbers are percentages, so we can expect a slow growth towards 50% v4 / 50% v6.
|ISP||Unique IPv6 addresses|
|7.||Tm Vads Dc Hosting||3|
The graph below shows the percentage of browsers that default to IPv6 vs. IPv4 when visiting the ipv6-test connection test. Hopefully, in the not so distant future, the red bars will grow taller than the blue ones.
The graph below shows the percentage of browsers that default to IPv6 vs. IPv4 for users that have both v4 and v6 connectivity. Usually a system will default to v6 when it's available, but in some cases with tunneled connections, v4 stays the default.
|ISP||Test count||IPv4||IPv4 %||IPv6||IPv6 %|
|2.||Tm Vads Dc Hosting||6||0||0.0%||6||100.0%|
Here you can see the evolution of address types over time, and measure usage of 6to4 and Teredo tunneled connectivity. It should be noted that because 6rd works with native addresses, it cannot be detected here as tunneled. This is also the case with VPN based tunnels.
This one illustrates the connection speed gap between IPv4 and IPv6, numbers represent v6 speed as percentage of v4 speed. The lower IPv6 speeds are often caused by tunneling overhead or insufficient v6 connectivity or peering capacity at ISPs.
|ISP||Test count||IPv6 average|
|6.||Tm Vads Dc Hosting||6||0.0 Mbps|
|7.||Hurricane Electric||99||0.0 Mbps|
|8.||gogo6 Inc.||48||0.0 Mbps|