Access to The Bay Citizen’s website was interrupted briefly Friday when the computer server that manages its incoming traffic forgot its name for reasons we’re still trying to sort out.

Anyway, in just a few minutes our technical gurus were able to remind the server of its true identity and our services were restored.

But then a bunch of people tried to visit baycitizen.org all at once to see what all the hoopla was about, resulting in a traffic jam that slowed response time to a pace that would be familiar to people who drive on Highway 101 at rush hour. The sudden popularity of the baycitizen.org site traveled through the Internet toward our hosting servers like a pig moving through an anaconda, and the “task server” that handles things like our user accounts and content management systems choked, which certainly didn’t help. As a result, you might have been able to visit baycitizen.org to read articles, but not to post comments. On our side of your computer screen, our ability to post new stories to our site was erratic for several hours.

The offending server has now received a software transfusion, and all is better now. We apologize for the inconvenience.

We now return you to our regular programming.