Status

We’re investigating.

The server has been suspended by our provider for abuse. We hope to have the situation resolved in the next hour.

The suspension should be lifted in the next hour (confirmed by a telephone call). In the meantime, we’re preparing another server in case the issue lingers, which may explain the temporary SSH key change if you try to connect to ssh.alwaysdata.com.

ssh.alwaysdata.com is now up again, although using a temporary server.

Note: cron jobs and services (which is in beta) are still down.

The old SSH key and the crontabs have been reinstalled on the temporary server, so everything is pretty much back to normal.

Now that we’ve gained access to our regular ssh.alaysdata.com, we’ll investigate to prevent this issue from happening again. Once this is done, we’ll switch back to the regular server.

We have a clear understanding of what happened, as well as what needs to be improved on our internal firewall so that it doesn’t happen again. We’ve started working on it, it should hopefully be done by the end of the day.

We’ve switched back to the primary server.

We’ve detected and delete the account responsible for the abuse. We’re still working on our internal firewall to prevent this issue from happening again.