8 replies to this topic

[MikeDVB]

The hardware powering the S5 server is experiencing issues.  The issues are not so large that an automatic fail-over happened but enough to disrupt the busiest services on the server.

 

We're working to restore stability and will likely be balancing the S5 server over to another piece of hardware.

 

We apologize for the trouble and will provide updates here as they come.

[MikeDVB]

This is actually one of the larger DDoS attacks we've ever seen - large enough that action had to be taken at the network level to keep the network stable.

 

Currently there is an IP address that is null routed and we're going to be working to restore services to other IPs.  Hopefully the attack won't move to the new IP but without us knowing who, exactly, was the target it's hard to be sure.

 

We're going to be evaluating all of the logs to do our best to identify who the target of the attacks are so we can isolate the account.

[MikeDVB]

Still working to move accounts to new IPs.

[MikeDVB]

Most accounts have had their IP addresses updated.  We still have a few more to update.

[MikeDVB]

All accounts have had their IP addresses updated.  I'm going to be emailing everybody on the server [even those not affected] as there is no way for us to separate out emails by IP.

[MikeDVB]

An email has been dispatched to all clients on the S5 server.

[SarisIsop]

Thank you.

[SMoKeR]

Good job responding quickly to the attack.

If the attack was targeting a specific account, are you going to isolate it?

[MikeDVB]

Good job responding quickly to the attack.

If the attack was targeting a specific account, are you going to isolate it?

If we're able to identify it, we would and would reach out to the owner.

So far the attack hasn't changed IPs.