Wednesday, November 26, 2014

Data Center Down—Sites Offline

Wednesday morning, November 26th, 7:15am ET, the data center hosting all BWD sites (and email) is temporarily down/out of service. The current status predicts the service will be back online "within the hour”.

UPDATE: Issue resolved 7:17am ET.

Wednesday, April 9, 2014

ALERT: Possible Down Time, Wed Apr 9th, 2:20pm ET

I just received the following notice from the hosting service company:

This notice is regarding imminent, emergency service restarts within your VPS. A recently discovered openssl vulnerability has been patched in your VPS, however a restart of your server's Apache web service is still required in order to load the new openssl version.

Unfortunately, the nature of this vulnerability means we must do so as soon as possible.

In most cases, Apache will only be down for a fraction of a second while the old service stops and the new one starts.

Please be aware that this may cause some down time for your website, and/or email. I will monitor the process as it unfolds. Hopefully, their best-case scenario will be what actually happens.

Saturday, January 4, 2014

Server Offline - Reboot in progress

There were some mail server issues today (dropped connections, webmail inaccessible) and subsequent attempts to restart/repair services were also ineffective. An attempt to restart the server was made, and is currently in progress. The Tier II (and higher) techs are currently working to restore services.

UPDATE: 4:00pm ET:

Four hours later, and still "in progress". Very sorry. I am assured every time that the resolution will come soon, and I'll be notified once the server is back online.


The server is back online, and should be functioning properly. Please contact me if you are noticing any further connection issues.

The official response from the server techs was this: " seems there was an issue with the IP address associated with your account and routing. Our system administration team routed the IP correctly and this issue isn't happening anymore, we apologize for any inconvenience this issue may have caused."

Sadly, this was caused by their reconfiguration of *another* issue they were attempting to correct.

My apologies for the down time.