On the evening of Saturday 29 December your humble admin was doing some admin work in preparation for some upcoming Domain Name Changes when he noted intrusion attempts coming in near-real-time from a foreign host attempting to break one of his daemons (services).
He took action - a little too much.
Thanks to some not-so-well-thought-out software syntax, maverick.blakjak.net went offline (for TCP purposes) and remained offline until our beloved Colo Provider Helix returned from holiday to reboot the server. ;-) (How's that for timing? Pick the one interval where there's noone handy to fix it...)
Total Down time was around 5 days and 18 hours. Fortunately, having come in under 7 days (barely) there should be no loss of mail (messages would've queued and will have been delivered over the course of this afternoon in the usual routine of retrys per RFC) and outside of the fact that things were a bit broken in the web department, services are back to how they were.
(If you do spot any weirdness, those hosted here should know how to get hold of me. Else hit the contact form above.)
What do we learn from this experience? When screwing with your firewalls, think real hard about the command you're entering before you submit it!!
The only thing to be grateful for was that due to the timing (holidays), little business was disrupted.
Unfortunately the timing also contributed to the delay in restoring service (which would otherwise have only been a few hours lost.) Lesson learnt.
This experience also has me working harder on the sequel to maverick; Stay tuned. (yeah, i keep saying that... but having broken all records for service interruption, I'm very interested making sure an event like this doesn't happen again.... !)