{"id":95401,"date":"2020-09-28T19:43:12","date_gmt":"2020-09-28T17:43:12","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/progress-vnedreniya-ipv6-za-10-let"},"modified":"2020-09-28T19:43:12","modified_gmt":"2020-09-28T17:43:12","slug":"progress-vnedreniya-ipv6-za-10-let","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/progress-vnedreniya-ipv6-za-10-let","title":{"rendered":"Progress of IPv6 Implementation Over 10 Years","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Probably everyone involved in implementing IPv6 or at least interested in this set of protocols knows about Google's IPv6 traffic chart<\/a><\/noindex>. Similar data is collected by Facebook<\/a><\/noindex> and APNIC<\/a><\/noindex>, but for some reason, Google's data is the benchmark (although, for example, there is no visibility from China).<\/p>\n

The chart experiences noticeable fluctuations \u2014 readings are higher on weekends and significantly lower on weekdays, with the current difference exceeding 4 percentage points.<\/p>\n

I became curious about what would happen if we removed this noise and whether interesting information could be seen by clearing the data of weekly fluctuations.
\n<\/a><\/noindex>
\nI downloaded the file from Google<\/a><\/noindex> and calculated the moving average. I excluded the results for February 29, as I couldn't figure out how to smooth them, and it seems it doesn\u2019t affect anything.<\/p>\n

Here are the results:<\/p>\n

\"Progress
\n
\nHere high-res here<\/a><\/noindex>.<\/p>\n

Some interesting observations:<\/p>\n