At a glance:
Only customers with bots assigned to Bot-Host 6 were affected. All other Bot-Hosts continued operating normally throughout.
Affected customers saw errors loading the SCNX dashboard, and slash commands, buttons, and modals were slow to respond or timed out. Bots were not fully offline, but performance was clearly degraded.
New bot creation was temporarily limited for some customers while the automatic bot-assignment system was offline.
Customers on a Professional plan: we recommend switching to one of our Premium Hosting locations from your dashboard for the most stable experience.
This update is being posted after the incident. We have details on why below.
A note on timing: this update is being posted retroactively. During the incident itself we were focused entirely on bringing Bot-Host 6 back to a healthy state, and we made the call to communicate properly afterward rather than post partial information in the moment. We know that is not ideal, and we are sorry for the silence during the incident window. We are also revisiting our internal process so that future incidents get a status post in parallel with the technical response, not after it.
What happened: two planned operations were running on our infrastructure at the same time. The first was a service-provider migration affecting Bot-Host 6. The second was scheduled maintenance on the automatic bot-assignment component of Bot-Manager, which we had paused while preparing to bring a new Premium Bot-Host online. When the migration completed, the affected bots restarted. Because the bot-assignment system was paused, Bot-Host 6 reported incorrect initial load values during the restart window. Once the bot-assignment system came back online, it acted on those incorrect values and placed significantly more bots than it should have on Bot-Host 6, eventually pushing it well over its intended capacity.
What affected customers saw: errors when loading the SCNX dashboard, particularly when opening server configuration pages. Discord interactions such as slash commands, buttons, and modals took a long time to respond or timed out before Discord accepted the response. Bots remained connected and were not fully offline, but many interactions felt broken from the user side.
Impact on new bot creation: because the automatic bot-assignment system had to stay offline during recovery, the number of free bot slots was reduced and new bot creation was temporarily unavailable for some customers. This was a knock-on effect of the recovery process rather than a separate issue.
Recommendation for Professional plan customers: if you are on a Professional plan and were affected, we recommend switching your bot to one of our Premium Hosting locations from your dashboard. Premium Hosting offers higher average uptime and more resources per bot, and access is already included with your plan.
