ScootKit - Notice history

Our upstream hosting provider has confirmed that their emergency maintenance is complete, and full service has been restored to our platform.

While we design our software to be highly resilient, we ultimately rely on physical data center infrastructure managed by our hosting partners. As with any complex physical system, underlying hardware components can occasionally fail or degrade without warning. In this instance, our provider had to execute an emergency hardware replacement on the host nodes to prevent a more severe outage, which resulted in the temporary disconnection.

Our monitoring systems confirm that all servers are back online, stable, and operating normally.

Thank you for your patience and understanding during this unexpected downtime. We sincerely apologize for any inconvenience it caused.

Summary of the Event

Earlier today, many of you noticed that servers where you hold Administrator permissions (but are not the server owner) suddenly disappeared from your management dashboard. We want to clarify that this bug not only hid the servers from your view but also locked your access to manage them through our interface.

Please be assured that this was strictly a dashboard authorization issue. All of your hosted bots and automated systems remained online and functioned perfectly throughout this incident.

What Happened & Why

This issue was caused by a backend update we rolled out yesterday. We updated our systems to use Discord’s latest API version (v10) to ensure future stability.

However, we missed a critical detail: in older versions of their API, Discord sent user permissions in a specific background format (a data field called permissions_new). In v10, Discord completely dropped this legacy field. Because our dashboard's background logic was still explicitly looking for the old format, it read everyone's admin permissions as "0". As a security precaution, when our system reads "0" permissions, it defaults to hiding the server and locking dashboard access to it.

Why Our QA Missed This

We take full responsibility for this slipping through to production. Our Quality Assurance (QA) process absolutely should have caught this before the update went live yesterday. It didn't because our older testing procedures only verified dashboard access for Server Owners and users with specific Trusted Admin permissions. Because both of those permission types use different verification logic, they were completely unaffected by the API change, keeping the bug hidden during our automated and manual tests.

How We Reacted

• Issue Detection: Once the update went live, we began receiving an increased volume of support tickets regarding missing servers.

• Investigation: Our engineering team immediately began investigating the reports to find a common denominator, identifying that it only affected non-owner admins.

• Identification: We traced the bug to the GET /users/@me/guilds Discord API endpoint and pinpointed the missing permissions_new field.

• Resolution: We updated our backend logic to read Discord's current, official permissions format and deployed the fix to production.

What You Need to Do

The fix is completely rolled out on our end. To regain access and see your missing servers again, you need to make sure your browser loads the newest version of the dashboard:

• Perform a hard refresh of the page (Press Ctrl + F5 on Windows or Cmd + Shift + R on Mac).

• Alternatively, you can clear your browser cache.

Looking Ahead

• QA Process Update: We have immediately updated our QA testing protocols to explicitly include standard Administrator permission checks alongside Owner and Trusted Admin checks.

We apologize for the frustration this caused and appreciate you bringing it to our attention so quickly!

We have confirmed that the fix for the missing servers in the dashboard is fully operational and this incident is now resolved.

If you still do not see your servers, please remember to perform a hard refresh (Ctrl + F5 / Cmd + Shift + R) or clear your browser cache.

As a final reminder, all hosted bots and systems were unaffected by this visual bug and continue to work perfectly. Thank you for your patience and understanding while we sorted this out!

We have successfully rolled out a fix for the issue that prevented servers from appearing in the dashboard for users with Administrator permissions. We are currently monitoring the situation to ensure everything is functioning correctly.

Important: To see your missing servers again, you will need to perform a hard refresh of the dashboard page (Ctrl + F5 / Cmd + Shift + R) or clear your browser cache.

As a reminder, all hosted bots and systems remain fully operational and working without any issues. Thank you for your patience while we resolved this!

We have successfully identified the root cause of the issue preventing some servers from appearing in the dashboard for users with Administrator permissions. The problem was related to a recent change in how permissions are formatted in the underlying Discord API.

Our team is currently implementing and deploying a fix. All hosted bots and systems continue to be fully operational and unaffected by this dashboard issue. We will update this page again as soon as the fix is fully rolled out and the dashboard is back to normal.

Our upstream hosting provider has confirmed that the network connectivity issues in their EU region are fully resolved.

The severe packet loss, timeouts, and intermittent connection drops that were affecting roughly 20% of our non-premium servers and bots have completely cleared up. We are monitoring the network on our end, and traffic has returned to normal.

What you need to do: Your servers and bots should be running smoothly again. If your bot is still hung up or your server seems stuck, try giving it a quick restart. If you are still running into any lingering issues after a restart, please open a support ticket so we can take a closer look.

Thanks again for bearing with us through the spotty connections today. We know dealing with upstream outages is incredibly frustrating, and we really appreciate your patience while we waited for the host to apply the fix!

To clarify, these servers aren't completely offline, but they are experiencing high packet loss, severe timeouts, and intermittent connection drops. You might find your server or hosted bot is reachable sometimes, but the connection drops shortly after. The remaining parts of the non-premium servers remain fully operational.

The hosting provider has officially acknowledged the issue. At 03:47 PM (UTC+1), they confirmed a "network connectivity issue in the EU region" and stated their technical team is actively working to resolve it as a top priority.

Please know our team is doing everything we can on our end. We are actively monitoring the routing and are fully staffed, ready to ensure everything is stable the exact second the provider fixes their network.

We know dealing with an unstable connection is incredibly frustrating, and we really appreciate your patience. We'll post another update as soon as the packet loss clears up and connections stabilize.