During our last maintenance, we identified that one of our server storage drives was experiencing degraded performance. Thanks to our redundant storage system (RAID), no data was lost, as the remaining drives automatically covered the workload. To keep things running perfectly, we need to swap out the faulty drive. This requires a brief period of downtime.

14:00 update

The bot is now fully online! Thank you all so much for your patience, and we are incredibly sorry for the delay.

13:00 update

We have successfully resolved all the issues with broken packages and system dependencies. We are now officially starting up the bots!

12:00 update

The disk copy is 100% complete! Right now, we are double-checking all the data to make sure it’s perfect, sorting out the Linux boot setup, and updating the kernel so the server is fresh, secure, and ready to go.

10:15 update

Quick progress update: 30% of the data has been successfully copied so far.

10:00 update

Just a quick heads-up: the data is currently copying over to the second drive. Because of the volume, the transfer process is expected to take about 1.5 hours to complete. Everything is running smoothly and safely.

Here is the exact breakdown of our estimated timelines for bringing services back online:

• Now: Hardware sync and data copying (System offline).
• ETA ~1.5 Hours from now: Paid Users — Your bots will be turned back on first, immediately after the sync completes.
• ETA ~2 Hours from now: Free Users — Your bots will be activated right after the Plus queue is fully cleared.

Thank you for your continued patience while the hardware finishes the heavy lifting. We are almost at the finish line!

9:00 update

We are incredibly relieved to share that everything has gone exactly according to plan. The old drive survived the full transfer, and we have successfully restored all data to the new primary drive.

What we are doing right now: Now that the data is safely back on the server, we are taking the final step: pulling out that old, worn-out drive for the last time and replacing it with the second brand-new drive.

Once the second new drive is in, the system will automatically sync up, and we will begin bringing our services back online. Because the server is now running on two fresh, high-performance drives, you can expect the system to be much faster and more stable moving forward.

Thank you all so much for sticking with us through this rollercoaster of a day, your patience has meant the world!

8:00 update

We want to give you an honest and detailed update on where things stand with our recovery efforts.

First, the good news: our data is safe. We have successfully backed up and secured all critical data to an external server.

To be fully transparent about what happened, we experienced a rare cascading hardware failure during our scheduled maintenance. We have a two-drive system; one drive was old and scheduled for replacement, while the other appeared healthy. However, when our technician pulled the old drive, the remaining "healthy" drive unexpectedly suffered a total hardware controller failure at that exact moment. In enterprise environments, drives under identical stress for years can sometimes fail together when the system is disturbed.

Because the healthy drive failed completely, we had to reinsert the old, worn-out drive just to see if we could read it. Fortunately, it worked, and we spent the last few hours carefully compressing and copying all of your data off it to safety.

What happens next: Now that the data is secured, we are moving to the final phase: copying everything onto two brand-new, fresh drives.

• If the old drive survives the stress of this final transfer, we will be back up and running relatively quickly.
• If the old drive fails mid-copy, we will have to rebuild and reinstall the entire server configuration from scratch using our external backups, which will extend our timeline.

Either way, the end result will be a server running on brand-new hardware that is much faster and highly stable. We are working through this as fast as humanly possible, and we will share another update with an estimated ETA shortly.

Thank you again for your incredible patience and understanding.

6:00 update

We are writing to you with a heavy heart to give you an update on today's maintenance. Unfortunately, we’ve run into a serious roadblock. After replacing the drives, our system encountered an unexpected error, and we are currently unable to load certain data and services.

We are doing everything humanly possible to resolve this, but the recovery is proving to be much more complex than anticipated. Because of this, services will remain disrupted for the time being.

We honestly apologise for this situation and the stress it may cause you. I will share another update as soon as we know more.

4:03 update

We started working on the drive repair.

2:30 update

We have paused dashboard access for new users. If you are already logged in, you can still update and modify your server as long as you don't refresh website.

Schedule

29 May 2026 03:00 (CEST) — Safety First: We will perform a full database backup (bot still online).
29 May 2026 04:00 (CEST) — Bot Offline: A qualified technician will physically replace the drive. This process is expected to take between 30 to 60 minutes.
29 May 2026 05:00 (CEST) — Coming Back Online: The bot will gradually power back on. To manage the server load safely while the new drive copies the data, we will bring plus/paying customers back online first, followed immediately by our free users.

Thank you for your patience and understanding while we keep our infrastructure healthy!