My sincere apologies for the unexpected downtime you've experienced today. We were offline from 11:28 to 13:23 GMT due to a small (alas, fatal) typo in one of our server settings. Normally we don't mess with these settings, and it only happened as we're preparing for our next infrastructure upgrade (bigger and faster hardware). Again, my apologies, and thank you to everyone who contacted me directly!

I still recall with embarrassment some of the mistakes in parameters I made back in my mainframe System Programming days. Nothing like a mistake causing you to have to restore a standalone system to allow you to edit the live system to bring it up

My sincere apologies for the unexpected downtime you've experienced today. We were offline from 11:28 to 13:23 GMT due to a small (alas, fatal) typo in one of our server settings. Normally we don't mess with these settings, and it only happened as we're preparing for our next infrastructure upgrade (bigger and faster hardware). Again, my apologies, and thank you to everyone who contacted me directly!

Far more trivial. We were cleaning up a few settings to prepare for upcoming hardware upgrades, and we missed to comment out one reference to a now non-existing entry. During log rotation the web server service followed that reference and subsequently complained about not finding the entry. All attempts of our fail-over system to restart the service, well, failed.

Far more trivial. We were cleaning up a few settings to prepare for upcoming hardware upgrades, and we missed to comment out one reference to a now non-existing entry. During log rotation the web server service followed that reference and subsequently complained about not finding the entry. All attempts of our fail-over system to restart the service, well, failed.