CRL sites ordered by site name over the last 1 day, updated every 15 mins. 305 sites
Click on a column heading to sort by that column, click twice to reverse order.
Click the site name to see graphs of site performance.
Rank Performance graph Company site OS Outage hh:mm:ss Failed Req% DNS Connect First byte Total Kb/s size(K)
301 Linux  0:00:00  0.000  0.363 0.093 0.188 0.188 - 0
302 Linux  0:00:00  0.000  0.544 0.008 0.035 0.035 - 1
303 unknown  23:48:41  100.000  - - - - - -
304 Windows Server 2012  0:00:00  0.000  0.393 0.073 0.149 0.149 - 0
305 Windows Server 2003  0:00:00  6.886  0.275 0.094 0.194 4.640 591 2628
First page   Previous page  


Report from 23-Feb-2020 09:01 till 24-Feb-2020 08:53

Generated on 24-Feb-2020 09:04

Note: Outage times display the minimum outage time which may understate each outage by up to 15 minutes, which is the sampling frequency.

If you are researching prospective hosting locations, or performing competitor analysis and would like to buy bespoke performance monitoring of sites of your choice, or access to historical data, please mail us at

Interpreting the Tables

By default the sites are ranked in order of failed requests and time to connect, shortest first, in order to give the clearest indication of network capacity and congestion, with the least impact from the performance of the individual web server, though it is possible to sort by other columns by clicking on the column heading.

Presently our performance collectors are located at New York/New York Internet-2, Italy/Aruba-2, Pennsylvania/INetU-3, Amsterdam/Webair-2, US West/Azure, Singapore/DigitalOcean and Ireland/Amazon. Sites located near one of our collectors may have an advantage over others listed in the table, though this effect is mitigated by using averages collected from multiple points. Sites exclusively hosted in the Far East are at a disadvantage as we do not currently have a performance collector in the region.

Sites using a Content Distribution Network, such as Akamai, have a particular advantage as the response to our request would come from the node closest to each performance collector.

More information can be found in the FAQ.