SCNX Frontend - Operational
SCNX Frontend
SCNX Backend - Operational
SCNX Backend
SCNX Bot-Manager - Operational
SCNX Bot-Manager
SCNX Image Generation API - Operational
SCNX Documentation - Operational
SCNX Documentation
SCNX RSS Hub - Operational
SCNX RSS Hub
SCNX Image CDN - Operational
@SCNX Bot - Operational
ScootKit Website - Operational
ScootKit Website
ScootKit Discord Support System ("DingBot") - Operational
ScootKit Discord Support System ("DingBot")
ScootKit Support System - Operational
ScootKit Support System
ScootKit Analytics - Operational
ScootKit Analytics
ScootKit Mail - Operational
ScootKit Mail
scootk.it URL Shortener - Operational
scootk.it URL Shortener
ScootKit Issue Reporting - Operational
ScootKit Issue Reporting
ScootKit Translations - Operational
DingBot - Discord Customer Suppot - Operational
Notice history
May 2026
- ResolvedResolvedThis incident has been resolved.
- MonitoringMonitoring
At a glance:
Bot-Host 6 is stable and operating correctly. We are continuing to monitor it.
Active recovery work is paused for the night. Operations are stable enough that further hands-on work can safely resume tomorrow, and we would rather do it well-rested than push through and risk a regression.
New bot creation is still limited while our automatic bot-assignment system remains offline.
If your bot still feels sluggish, you can switch Bot-Hosts from your dashboard. If you cannot switch, our customer service can help: https://scnx.app/help
If your bot was on Bot-Host 6 during the incident, you may be eligible for an SCNX Care voucher. Request one here: https://scnx.app/user/support/new?topic=cmnhok1np00kjtghxayiwcwmq
Bot-Host 6 is now stable and operating correctly. We are keeping it under close observation while it continues to settle.
A note on what comes next: there is still recovery work to do, but the situation is no longer urgent. Bot-Host 6 is healthy, customer-facing performance has returned to normal, and the remaining tasks are about restoring full system functionality rather than fixing active impact. We have decided to pause active recovery work for the night and continue tomorrow. We would rather complete the remaining steps carefully than rush them while operations are already stable.
If you are still noticing slow responses or dashboard errors on your bot, you can switch to a different Bot-Host at any time from your dashboard. That is the quickest way to get back to normal performance while the affected host completes its recovery. If you are unable to switch for any reason, please reach out to customer service at https://scnx.app/help and we will help you directly.
A note on new bots: our automatic bot-assignment system is still offline while recovery continues, so available slots for new bots are reduced. New bot creation may be temporarily unavailable for some customers until this is resolved. We will share an update tomorrow as recovery progresses. You can subscribe to notifications about new slots in the dashboard.
If your bot was on Bot-Host 6 during the incident, you may be eligible for an SCNX Care voucher as a goodwill gesture. To request one, please open a support request here: https://scnx.app/user/support/new?topic=cmnhok1np00kjtghxayiwcwmq. Vouchers are issued under the SCNX Care program and are valid for 14 days from the date of issue.
Thank you for your patience while we work through this carefully.
- InvestigatingInvestigating
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.
- ResolvedResolvedThis incident has been resolved.
- MonitoringMonitoring
Discord seems to have restored platform stability, but issues might continue to appear.
- IdentifiedIdentified
Bots might be unable to respond or take other action. This outage is outside of our control and is on Discord's end. Our systems are running without issues.
Please monitor this incident directly with Discord: https://discordstatus.com/.
Mar 2026
- ResolvedResolved
We have fully resolved the network issues affecting the Bot-Manager and Backend.
After a thorough investigation, we determined that the root cause was a DNS server failure at our hosting provider. This failure led to internal connection timeouts, which temporarily impacted the SCNX dashboard and some bots located on servers at that specific provider.
Our systems are now fully stable, and we are no longer seeing any failed requests. In total, the downtime for this incident was less than 45 minutes. We deeply apologize for the inconvenience and frustration this disruption caused to your experience.
If your services were impacted during this window, we invite you to claim an SCNX Care Voucher. You can file a request by visiting: https://scnx.app/user/downtime-refund
- UpdateUpdate
After reviewing user reports, we can confirm that a few bots attempting to start during the incident were stopped automatically due to network failures on Bot-Host #38. Most of these bots have now automatically started, but some bots - particularly bots that users attempted to manage during the downtime via the dashboard - might need to be started manually due to the failure affecting the network process.
- MonitoringMonitoring
The rate of failing requests has dropped below 1%, meaning that most requests now work. The dashboard should work now without issues again, but we're continuing to monitor the situation and will update this page with further information once available. Hosted Bots were not affected.
- IdentifiedIdentified
We've adjusted some networking systems and we're seeing a partial recovery, with now less than 10% of requests failing. We're still working on getting this resolved as soon as possible.
- UpdateUpdate
Quick additional note: It seems like only around 70% of requests fail, meaning that reloading the page might allow you to create a temporary connection. Still, please avoid spamming this to avoid ratelimits blocking your device.
- InvestigatingInvestigating
We're seeing an increased amount of internal traffic between Bot-Manager and Backend failing. We're investigating this. Hosted Bots are not affected and will continue to work normally, only the dashboard is affected.
- ResolvedResolvedThis incident has been resolved.
- InvestigatingInvestigating
Due to an issue at Discord, Bots are unable to start Discord connections at the moment. For details, view the Discord Status Page: https://discordstatus.com/incidents/9sng5r2j71sq