ScootKit - Bot-Host Migration for Bot-Host #6 – Maintenance details

All systems operational

Bot-Host Migration for Bot-Host #6

Completed
Scheduled for 05-24-2026 at 1:20 PM – 4:41 PMUTC

Affects

Updates
  • Completed
    05-24-2026 at 4:41 PMUTC
    Completed
    05-24-2026 at 4:41 PMUTC
    Maintenance has completed successfully.
  • Update
    05-24-2026 at 3:29 PMUTC
    Update
    05-24-2026 at 3:29 PMUTC

    We've completed the migration; all bots are now running on Bot-Host #40. We're continuing to monitor the situation to ensure network stability, but all customer processes should be up and running. The dashboard can also be used again for affected bots. We apologize for the brief downtime, but this update was necessary to ensure that your bot can continue running without issue in the future. We aim to keep maintenances like this as brief as possible and appreciate your kind understanding.

  • Update
    05-24-2026 at 3:17 PMUTC
    Update
    05-24-2026 at 3:17 PMUTC

    We've completed the migration and are now restoring bot processes. This will take approximately 15 minutes. After that time, all bots should be running again and we will unlock the dashboard for affected bots again.

  • Update
    05-24-2026 at 2:39 PMUTC
    Update
    05-24-2026 at 2:39 PMUTC

    We're continuing the migration procedure. For this step, bots hosted on Bot-Host #6 are temporarily not available and will shortly be moved to Bot-Host #40, where they will be started automatically once the migration has concluded. During this time, affected bots won't be able to connect to Discord, and the dashboard can't be accessed. This maintenance is required for network stability reasons.

  • In progress
    05-24-2026 at 1:20 PMUTC
    In progress
    05-24-2026 at 1:20 PMUTC
    Maintenance is now in progress
  • Planned
    05-24-2026 at 1:20 PMUTC
    Planned
    05-24-2026 at 1:20 PMUTC

    We're migrating bots hosted on Bot-Host #6 to another bot-host to increase network stability. During this time, bots hosted on Bot-Host #6 might be temporarily unavailable. We'll do our best to minimize downtime.