4 ms·

We know that we've dropped the ball here. To be frank, it's just been extremely difficult to take our people off of mitigation long enough to write something mo

We know that we've dropped the ball here. To be frank, it's just been extremely difficult to take our people off of mitigation long enough to write something more coherent than "they're attacking our webservers", "they're attacking our core routers", etc. > And it looks like the attackers decided to start things back up again, as Linode.com is unavailable... They're watching our status page for updates and starting new attacks when we resolve previous ones. There's been an almost 1:1 correlation lately.

silverlight 11y ago
Indeed, well, keep fighting the good fight. We are cheering for you.
reefoctopus 11y ago
Thank you for the update. We really appreciate the information and wish you the best of luck in dealing with this.
00deadbeef 11y ago
I just registered to thank you for the update and to let you know I won't be moving away from Linode as this just gives the attackers what they want.
SudoAlex 11y ago
The correlation could also be the fact that you've blocked the attack, they can see that their previous attack is no longer working by testing it themselves - so they'll switch anyway, regardless of a status page update.
erikpukinskis 11y ago
> it's just been extremely difficult to take our people off of mitigation long enough to write something more coherent This always rings hollow to me, and yet I hear it over and over. A company like Linode surely has at least a dozen people who can be on call in a situation like this, probably much more. All it takes is for one engineer or even a product person... Heck a technically-minded support person could listen in on the war room meetings and get enough information to post something better than "we're fixing it". 5 minutes of blogging every six hours would be plenty. And yet, people always claim it's impossible and there's no time. Frankly I find it frightening... If you are coding that fast that no one on your team has five minutes to step aside, take a breather after six hours of coding and summarize what the team just spent the last six hours doing, I shudder to think what kind of panicked alarmist interventions you are making. There's no excuse for silence. There just isn't. It's a gross failure on the part of management to prioritize the responsibilities they have to your customers customers. Full stop. Sure, the engineers can't be expected to remember to tap out to blog. But if that's the extent of the accountability structures you can assemble during a crisis, that is a serious organizational failing, particularly for an organization the size of Linode.
- collyw 11y ago
  I would say that 5 minutes of blogging every 6 hours is just as likely to cause more harm than good. Wording something badly could lead to far more fear and confusion than the present situation if taken out of context.

silverlight 11y ago

Indeed, well, keep fighting the good fight. We are cheering for you.

reefoctopus 11y ago

Thank you for the update. We really appreciate the information and wish you the best of luck in dealing with this.

00deadbeef 11y ago

I just registered to thank you for the update and to let you know I won't be moving away from Linode as this just gives the attackers what they want.

SudoAlex 11y ago

The correlation could also be the fact that you've blocked the attack, they can see that their previous attack is no longer working by testing it themselves - so they'll switch anyway, regardless of a status page update.

erikpukinskis 11y ago

> it's just been extremely difficult to take our people off of mitigation long enough to write something more coherent This always rings hollow to me, and yet I hear it over and over. A company like Linode surely has at least a dozen people who can be on call in a situation like this, probably much more. All it takes is for one engineer or even a product person... Heck a technically-minded support person could listen in on the war room meetings and get enough information to post something better than "we're fixing it". 5 minutes of blogging every six hours would be plenty. And yet, people always claim it's impossible and there's no time. Frankly I find it frightening... If you are coding that fast that no one on your team has five minutes to step aside, take a breather after six hours of coding and summarize what the team just spent the last six hours doing, I shudder to think what kind of panicked alarmist interventions you are making. There's no excuse for silence. There just isn't. It's a gross failure on the part of management to prioritize the responsibilities they have to your customers customers. Full stop. Sure, the engineers can't be expected to remember to tap out to blog. But if that's the extent of the accountability structures you can assemble during a crisis, that is a serious organizational failing, particularly for an organization the size of Linode.

collyw 11y ago
I would say that 5 minutes of blogging every 6 hours is just as likely to cause more harm than good. Wording something badly could lead to far more fear and confusion than the present situation if taken out of context.