There's also the possibility that during your server outage, the box itself came up at some point between reboots/patches/etc. So if HS got a reliable ping 7 hours before the site was "really" back up, they are most likely considering the last outage window a seven hour period.
Pure speculation, but possible. I use HS as well and am also pretty happy with their service.
I'm not exactly sure about Hyperspin, but some paid uptime monitoring programs have a option of setting them to ignore downtimes up to several hours
[DC'S] SINGAPORE. AUSTRALIA. JAPAN. INDIA. CHINA HK. USA. UK. NETHERLANDS. GERMANY. SOUTH AFRICA MyCompanyWeb™: Start Your Own Professional Web Hosting Company in 24 Hours SkyNetHosting.Net - SEO Hosting. Reseller Hosting. Shared Hosting & VPS - 14 Years in Business!
Dedicated IP + SSL + WHMCS + Domain Reseller + Master Reseller + 100% SSD + End User Support and More!
Thanks for the info. I guess it makes some sense for things like scheduled downtime for maintenance and such but for the user using this as a gauge for reliability when looking for a host it seems very decptive to me.
I would guess that some hours after it went down the host scheduled a downtime then or whatever the correct terminology would be. And no, it was not only unpingable for 7 hours, it was many more than that. It's not downtime for the outage but 7 hours total for the month they are listing.
Oh well, due to downtime of 48 hours and less than adequate info during this time and after, as well as other recent issues, I have switched hosts. I chose a new host based on some reviews at this site as well as uptime stats. I hope those ones are more accurate.
When you schedule maintenance with hyperspin, the uptime reports states "maintenance" where down or up would be usually. Unknown could be that hyperspin couldn't really find the location or perhaps it was invalid.
-Steven | u2-web, LLC - Clustered Shared Hosting "It is the mark of an educated mind to be able to entertain a thought without accepting it" -Aristotle