Hyperspin reports are BACK!
(we're not sure if they are staying; let us know if you use them)

Static reports:
(last updated :May 31 2006 11:02:05. CDT)

Network is up
Server is up
Issue:
Emerg maintenance is now complete. May need a quick reboot sometime today to verify some settings.
****
More Emergency maintenance to be scheduled.

****
We're dividing out team up and will be triaging all tickets; it seems that some tickets aren't getting responded to, and that is getting fixed.
There are 3 different areas we'll be moving tickets into; Emergencies, which include site down or critical failures; Support issues, where parts don't work (ie. a webcounter doesn't work, or softare config issues) that are non-critical, and finally billing related issues, which will be handled Monday-Friday 9am-5pm EDT.

****
Due to some issues identified on this last long weekend, we are reviewing the current response procedures, as well as the information dissemination and general setups. We are going to be making a number of changes that will improve reliability and cut down on response time. (We had a long solid run without issues, and want to improve on that base)

****
We have upgraded our ticketing and billing server. We have been experiencing various issues with our old host, and hope this solves all the problems.
We are also going to be upgrading and improving the hosting servers this weekend.

****

Recent Issues:
Date(s)Description of the issue
Weekend of May 20/2006 Scheduled maintenance; periodic reboots and unavailability of some services.
Mar 14/2006 Webserver sluggish/non-responsive over a 2 hour period. Tracked back to a form of DOS.
Feb 15/2006 Apache slowness (two 5 minute issues). Tracked down to script misconfiguration.
Feb 4/2006 Emergency maintenance following a server issue.
Jan 27/2006 Webserver slowness/timeouts.
Applied a number of patches to alleviate the issue.
Jan 25/2006 From approx 3am-9am EST, and then for brief periods throughout the day, we had occurances of the webserver being slow to so slow it appears to timeout.
Jan 23/2006 Started with a webserver load issue (approx 3pm EST), and turned into an access issue. Datacenter had a problem getting the box online. Had partial service within approx. 30 minutes. Some DNS errors had some sites unavailable for up to approx. 20 more minutes.

This report will be made dynamic shortly