This morning, we were alerted to an issue with the MySQL service not running properly, which was causing pages that use the service to not display.  This issue has since been corrected. Downtime was about three hours.

Earlier this afternoon, Melvin experienced a slight load spike due to an exhorbitant amount of Apache processes running on the server.  During this time, domains were experiencing a 500 Internal Server Error when accessing the website(s).  We restarted the Apache process and the load was restored to normal. While websites were not “down” in a …

Early this morning, Melvin experienced approximately 51 minutes of downtime, starting at 6:52am MST.   Immediately upon notice from our monitoring service, we issued a response to the data center to reboot the server. Upon reboot, all services have been returned to normal.  No data loss was reported.

After over one hundred days of uptime, our primary server, Melvin, experienced some slight downtime for 58 minutes starting at 2:57am on 17 May, 2007.  Immediately upon notice from our monitoring service, we issued a response to the data center to reboot the server. Upon reboot, all services have been returned to normal.  No data …

One of our sites hosted here, techops.net, has been down for several hours. After some investigation, it has been determined that the downtime is not due to a problem with the server, and no other sites have been affected. We have already taken the necessary actions to correct this problem, although we currently do not …

Our main server (Melvin) experienced some slight downtime today.  As soon as we became aware of this, we contacted the Network Operations Center to reboot the server. Downtime was less than three hours.  No data loss has been reported.

Apache (the web server) had a bit of a blip this morning.  We restarted the service and all seems to be well. Downtime was minimal, less than five minutes.