Bottiger

Administrator
Our host sent us this message.

We made a configuration change to the router -- one that should not have caused it to crash -- and it crashed. We are currently in the process of opening an emergency remote hands ticket with the site to switch back to the old router, leaving this one offline for now, as it is clearly not stable from a software standpoint yet.

Update @ 2:52 pm CDT: We're back on the old, known-stable router now.

We have data telling us why the new router crashed (it was a software bug) that should allow us to coordinate with kernel developers to fix the problem. We will schedule another early-morning maintenance to switch back to the new router after it has been resolved, likely within the next several days.
 
We have made adjustments to our new router in Chicago and confirmed that they fix the crashing behavior that we saw before. Shortly after 4am CDT on Friday (March 13), we will be instructing on-site staff to switch us back over to this new router, after which we will do further testing.

We expect for total downtime to be less than 5 minutes. However, as before, if something goes wrong, there may be further downtime as we switch back to the old router, which will continue to be on hot standby. The overall window for this maintenance will be from 4am to 6am.

Please accept our apologies for the short notice. We have been working furiously to test the changes thoroughly and we want to push this out before the upcoming busy weekend, so that customers can benefit from the increased DDoS resistance of the more powerful hardware.