{"id":5483,"date":"2014-11-24T13:09:50","date_gmt":"2014-11-24T19:09:50","guid":{"rendered":"https:\/\/dcmblogmulti.wpengine.com\/?p=5483"},"modified":"2026-05-21T21:02:13","modified_gmt":"2026-05-21T21:02:13","slug":"ipv6-test-vs-ipv4-monitoring-errors","status":"publish","type":"post","link":"https:\/\/www.dotcom-monitor.com\/blog\/ipv6-test-vs-ipv4-monitoring-errors\/","title":{"rendered":"IPv6 Test vs IPv4: Testing Errors &amp; Resolution Issues"},"content":{"rendered":"<p>Take a look at the difference between how a page loads\u00a0(<a href=\"https:\/\/www.msnbc.com\/\" target=\"_blank\" rel=\"noopener noreferrer\">msnbc.com<\/a>) \u00a0from an IPv6-Only monitoring location and a monitoring location with native IPv6 or 6to4 translation. You may want to consider\u00a0running an IPv6 test on your own websites after seeing these results.<\/p>\n<h2 id='ipv6-test-from-ipv6-only-monitoring-location'  id=\"boomdevs_1\">IPv6 Test from IPv6-Only Monitoring Location<\/h2>\n<p>Here is a waterfall chart showing a web page\u00a0loading from an IPv6-Only location. You can see there are several\u00a0 elements attempting to load from 3<sup>rd<\/sup> party sites that are not able to resolve IPv6 addresses. This may cause\u00a0unexpected performance issues including pages that do not completely load.<br \/>\n<!--more--><br \/>\n[note note_color=&#8221;#fff7f7&#8243; text_color=&#8221;#000000&#8243;]<strong>Note: \u00a0<\/strong><em>You will\u00a0receive errors\u00a0if \u00a0any elements on your site do not resolve in IPv6 (including third party elements such as CDN content or other scripts and images). Only utilize the IPv6-Only location if you are prepared to deal with potential errors<\/em>.[\/note]\n<h2 id='testing-from-ipv4-monitoring-location'  id=\"boomdevs_2\">Testing from IPv4 Monitoring Location<\/h2>\n<figure id=\"attachment_5485\" aria-describedby=\"caption-attachment-5485\" style=\"width: 600px\" class=\"wp-caption aligncenter\"><a title=\"IPv4 Test\" href=\"https:\/\/www.dotcom-monitor.com\/wp-content\/uploads\/sites\/3\/2014\/11\/IPv4NoErrors.png\" target=\"_blank\" rel=\"noopener noreferrer\"><img fetchpriority=\"high\" decoding=\"async\" class=\"wp-image-5485\" src=\"https:\/\/www.dotcom-monitor.com\/wp-content\/uploads\/sites\/3\/2014\/11\/IPv4NoErrors.png\" alt=\"IPv4 Test - No Webpage Errors\" width=\"600\" height=\"278\" srcset=\"https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2014\/11\/IPv4NoErrors.png 1005w, https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2014\/11\/IPv4NoErrors-300x139.png 300w, https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2014\/11\/IPv4NoErrors-768x356.png 768w\" sizes=\"(max-width: 600px) 100vw, 600px\" \/><\/a><figcaption id=\"caption-attachment-5485\" class=\"wp-caption-text\">IPv4 Test Shows No Webpage Errors<\/figcaption><\/figure>\n<p>Here you can see how the results differ when a task is recorded from a location that is able to utilize IPv4. Because this location is able to resolve both IPv4 and IPv6, all elements on the page load successfully, giving the site visitor the proper user experience.<\/p>\n<p>As you can see in the comparison below, there are actually images, links and navigation that do not display from the IPv6 test location:<\/p>\n<figure id=\"attachment_5513\" aria-describedby=\"caption-attachment-5513\" style=\"width: 600px\" class=\"wp-caption aligncenter\"><a title=\"IPv6 Test vs IPv4\" href=\"https:\/\/www.dotcom-monitor.com\/wp-content\/uploads\/sites\/3\/2014\/11\/Missing-Elementssmall2.png\" target=\"_blank\" rel=\"noopener noreferrer\"><img decoding=\"async\" class=\"wp-image-5513\" src=\"https:\/\/www.dotcom-monitor.com\/wp-content\/uploads\/sites\/3\/2014\/11\/Missing-Elementssmall2.png\" alt=\"Missing Elements - IPv6 Test vs IPv4 Test\" width=\"600\" height=\"155\" srcset=\"https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2014\/11\/Missing-Elementssmall2.png 650w, https:\/\/www.dotcom-monitor.com\/blog\/wp-content\/uploads\/sites\/3\/2014\/11\/Missing-Elementssmall2-300x78.png 300w\" sizes=\"(max-width: 600px) 100vw, 600px\" \/><\/a><figcaption id=\"caption-attachment-5513\" class=\"wp-caption-text\">Full page load using IPv4 Test (Left) | Partial Page Load from IPv6 Test Location (Right)<\/figcaption><\/figure>\n<p>In conclusion, even if you&#8217;re ready to support IPv6, you need to run an external synthetic IPv6 test using the Dotcom-Monitor IPv6-Only location to ensure\u00a0all of the elements on your website are able to load properly. If you are an existing Dotcom-Monitor client, you can simply edit your devices and add the IPv6-Only location to the devices. If you are not yet a client,\u00a0<a href=\"https:\/\/userauth.dotcom-monitor.com\/Account\/SelectSignUpSolution\" target=\"_blank\" rel=\"noopener noreferrer\">sign up for the free trial &#8211; no credit card required<\/a>\u00a0and setup an\u00a0IPv6 test on your website for free.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Take a look at the difference between how a page (msnbc.com) loads from an IPv6-Only monitoring location and a monitoring location with native IPv6 or 6to4 translation. You may want to think about running an IPv6 test on your own websites after seeing these results.<\/p>\n","protected":false},"author":21,"featured_media":5484,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5483","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/posts\/5483","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/comments?post=5483"}],"version-history":[{"count":0,"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/posts\/5483\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/media\/5484"}],"wp:attachment":[{"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/media?parent=5483"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/categories?post=5483"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dotcom-monitor.com\/blog\/wp-json\/wp\/v2\/tags?post=5483"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}