Datapipe was the most reliable hosting company in October, impressively responding to all requests throughout the month, despite being in the area most affected by Hurricane Sandy.

Datapipe’s corporate offices are based in the heart of Jersey City, very close to areas where analysts had predicted a 100% probability of a storm surge higher than 6 feet. The southern tip of Manhattan eventually experienced a storm surge of 13 feet. Datapipe founder and CEO Robb Allen told Netcraft that the effects of the storm were also felt as far inland as Somerset, where Datapipe’s New Jersey datacenters are based.

After the grid became unstable on Monday, Datapipe switched to generators for their datacenter power supply. Even though their diesel reservoir was large enough to last at least four days, Datapipe also stationed additional fuel trucks on site in case roads became impassable.

Allen noted that previous events including grid blackouts, Hurricane Irene and 9/11 have all helped the internet connectivity and hosting industry in the US north east be better prepared for emergencies, though that there is currently a lot of strain on fuel delivery systems.

Datapipe’s performance and uptime remained remarkably calm before, during, and after the storm, in stark contrast to destruction depicted in photos taken during the event.

When there isn’t a storm brewing, Datapipe runs its United States data centers on entirely renewable energy and is recognized by the Environmental Protection Agency as a Green Power Partner. Datapipe’s other US datacenters are located in San Jose and North Virginia.

Datapipe also has datacenters in Iceland, London, Shanghai and Hong Kong. The location of the Iceland datacenter allows for free cooling and runs on 100% renewable power using only geothermal and hydroelectric energy sources. The physical infrastructure has been built with steel instead of concrete, making much of it recyclable at the end of its life.

Netcraft measures and makes available the response times of around forty leading hosting providers’ sites. The performance measurements are made at fifteen minute intervals from separate points around the internet, and averages are calculated over the immediately preceding 24 hour period.

From a customer’s point of view, the percentage of failed requests is more pertinent than outages on hosting companies’ own sites, as this gives a pointer to reliability of routing, and this is why we choose to rank our table by fewest failed requests, rather than shortest periods of outage. In the event the number of failed requests are equal then sites are ranked by average connection times.

Information on the measurement process and current measurements is available.