The official coComment weblog

As you certainly have noticed, we’ve had a bit of an outage over the last 24 hours. It was due to a problem at our hosting company, and to the best of our knowledge, it is now resolved.

Around 1pm local time (CET), the firewall started acting out. I’ll spare you the sordid troubleshooting details, but the situation was such that it had to be physically replaced. We then worked with the hosting company to reconfigure it, but despite our efforts — which involved Christophe connecting and doing some setup magic from his plane back from Japan, and many other more sordid details I’ll spare you too — there were still problems with the comment tracking service and our e-mail distribution until this morning. (This also means that if you sent us mail during the last 24 hours, you’re better off sending it again.)

The main thing is that as of 11:30 this morning (still CET) everything is (hopefully!) back to normal. We’re really sorry for any inconvenience this may have caused you.

If some of the conversations you wanted to track didn’t get recorded during the last day, remember you can simply go back to them and check the “Track this conversation” checkbox. If you want to reappropriate any comments you made during the outage, the old trick of selecting the comment and clicking on the bookmark (or toolbar button) still works.

technorati tags:outage, cocomment, service, firewall, problem, apologies, sorry, oops, configuration

We currently face problems with our Oracle Database.
We are investigating the problem and will try to fix it as soon as possible.

Don’t worry, your comments won’t be lost and you will retrieve a stable coCo-environment soon.
We are really sorry about this and apologize for any inconvenience you encounter.

RSS feeds are back to normal, was an encoding issue.

Thanks to all those who called to tell us that the RSS feed links are broken. It seems we have an encoding issue since the last release.

Sorry about that - we will fix it asap - and in the meantime please use the Your conversations page instead.