This page is provided to give an up-to-date status of the iCompute.com services. It will announce downtimes and disruptions in service – both planned and unplanned. Please see our policies here.
At 7:05 Am this morning 21 Jan 2024, our upstream connection failed and was not restored until 12:26 PM CST. All services were “up”during this period, but this appeared to be downtime to all users because access to all iCompute … Continue reading
A mistake in network configuration this evening at 6:17 PM CDT caused our internal network to become unusable. Though all services were “up”, this appeared to be downtime to all users because access to all iCompute services was unavailable through … Continue reading
Our mailserver was attacked early this morning with many thousands of unwanted emails. The cause was that two accounts on one domain got hacked. Having two email accounts at their disposal, the spammers took full advantage, and overwhelmed the mailserver … Continue reading
Our upstream connection was down from 6:41 AM to 8:55 AM CDT. Services have now been restored. We are sorry for the interruption in service. … Continue reading
At 17:23 CDT on Aug 17th a power failure caused our DSL upstream to fail. The upstream connectivity was restored at 18:09 CDT. … Continue reading
Our power failed again today. Power was out from 10:36 AM CST to 1:13 PM CDT, when upstream connectivity was restored. … Continue reading
From 12:23 AM CDT to 7:57 PM we were down, due to a power failure followed by a failure of our upstream DSL We apologize for the interruption of service.. … Continue reading
One of our old webservers crashed today at 2:35 PM CDT. It was brought on line at 3:04 PM CDT. … Continue reading
Our upstream connection to the internet failed this morning at 8:53 AM CDT. It was restored at 9:12 AM CDT. … Continue reading
Late yesterday afternoon (Nov 24th, 2021) the VM server had software problems with its swap space. The server struggled for almost 12 hours before becoming comatose and no longer responding. Our VM machines (VM1) also became unresponsive at some point … Continue reading