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.
Dotcom-Monitor now offers a dedicated IPv6 monitoring location, which means that tasks being monitored from this location will not be able to resolve traffic across an IPv4 network, so if the communication cannot travel across an IPv6 compatible network, this location will return a failed monitoring result.
Now you can test IPv6 connections specifically from an “IPv6 only” location to ensure that your services are accessible via IPv6 only nodes. This is useful for testing IPv6 specific resolution because there are configurations available on different networking devices that may allow traffic between IPv4 and IPv6 nodes that will not work with IPv6-Only nodes. For example, it is possible that you may have a router on one end of the communication that attempts to send IPv6-Only traffic using a tunneling mechanism to tunnel IPv6 through an IPv4 only network while the router on the other end is not capable of extracting the IPv6 address from the IPv4 tunneled data.
Utilizing an IPv6 location also allows you to ensure that any APIs you use are capable of handling IPv6 communications. The IPv6 monitoring location will let you know if your application is not IPv6-aware by triggering an alert when the application is unable to respond.
As a Web developer or IT team member, you can never have too much data detailing the performance of your website and how it compares to others across the industry. One simple way to understand how your website performance compares to a cross sampling of the internet takes just three steps:
Google Announces HTTPS as a Ranking Signal for SEO It’s official, Google openly “encourage(s) all website owners to switch from HTTP to HTTPS to keep everyone safe on the
Leveraging Dotcom-Monitor services, NCM Online developed fact-based observations about the performance of 20 leading web hosts in June, and continues to test additional hosts throughout the year (the most recent update to the list was 8/2/2014). These tests include purchasing a shared hosting plan from each provider and gathering page-load speed averages and uptime percentages from at least 10 concurrent days using identical websites on each provider. This process provides 2 of the ten criteria NCM Online uses to rank different shared hosting service providers.
Dotcom-Monitor is currently tracking a Facebook downtime incident.
To verify the current status of Facebook in real-time from around the world, users can attempt to connect simultaneously from 20 locations worldwide using Dotcom-Monitor’s free Facebook downtime test tool.
Voice Connectivity is Critical. Your phone systems have gone down and you are unable to communicate with your customers. After several hours of troubleshooting you have managed to get the services up again but what do you do now? Whether you utilize a SIP based VoIP system, digital voice over T1 lines or POTS (plain old telephone service), those voice services need to be available.
How Often are You Asked “Is the Website Down?” Such calls can lead to hours of lost time only to find out it was a minor issue for a limited user base. Do you have the tools in place to proactively detect and deal with such issues?
The new DNS caching features at Dotcom-Monitor allow you to perform some interesting tests that show how DNS caching can affect your page load speed.
We realize that many organizations monitor their online services with a number different goals in mind, and so we listened to the feedback we received that some users want to include the DNS response time in their monitoring and some users want to be able to remove DNS response from their monitors.
How you wish to handle DNS response time in regard to your monitoring needs is up to you, but we want to take this opportunity to show the differences in how DNS response time affects website load using our new tools.
We ran a test monitoring YouTube from a single location in the midwest United States with three different DNS cache settings. A basic HTTP full page load on the YouTube front page resulted in some interesting, although not that surprising results.
Keep in mind the results will vary depending upon a number of variables such as which locations you are monitoring from, the time of day, the load on the DNS servers, and on the website servers.
Parallax websites are compelling and easy to follow. However, because all of the graphics and text are on one page and these sites often use video, they can also be a performance nightmare if not optimized correctly.