ScootKit - Notice history

All systems operational

Operational

SCNX Frontend - Operational

100% - uptime
Mar 2026 · 100.00%Apr · 100.00%May · 100.00%
Mar 2026
Apr 2026
May 2026

SCNX Backend - Operational

100% - uptime
Mar 2026 · 99.989%Apr · 100.00%May · 100.00%
Mar 2026
Apr 2026
May 2026

SCNX Bot-Manager - Operational

100% - uptime
Mar 2026 · 99.975%Apr · 100.00%May · 100.00%
Mar 2026
Apr 2026
May 2026

SCNX Image Generation API - Operational

SCNX Documentation - Operational

SCNX RSS Hub - Operational

SCNX Image CDN - Operational

@SCNX Bot - Operational

100% - uptime
Mar 2026 · 100.00%Apr · 100.00%May · 100.00%
Mar 2026
Apr 2026
May 2026
Operational

ScootKit Website - Operational

100% - uptime
Mar 2026 · 100.00%Apr · 100.00%May · 100.00%
Mar 2026
Apr 2026
May 2026

ScootKit Discord Support System ("DingBot") - Operational

ScootKit Support System - Operational

ScootKit Analytics - Operational

ScootKit Mail - Operational

scootk.it URL Shortener - Operational

ScootKit Issue Reporting - Operational

ScootKit Translations - Operational

DingBot - Discord Customer Suppot - Operational

100% - uptime
Mar 2026 · 100.00%Apr · 100.00%May · 100.00%
Mar 2026
Apr 2026
May 2026
Operational

Discord API - Operational

Stripe API - Operational

OpenAI API - Operational

Cloudflare CDN - Operational

Notice history

May 2026

A Discord Outage is affecting bots hosted via SCNX
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    Discord seems to have restored platform stability, but issues might continue to appear.

  • Identified
    Identified

    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/.

Apr 2026

Oracle Cloud Infrastructure Compute - Maintenance Scheduled
  • Completed
    04-29-2026 at 8:30 AM
    Completed
    04-29-2026 at 8:30 AM
    Maintenance has completed successfully
  • In progress
    04-29-2026 at 5:30 AM
    In progress
    04-29-2026 at 5:30 AM
    Maintenance is now in progress
  • Planned
    04-29-2026 at 5:30 AM
    Planned
    04-29-2026 at 5:30 AM

    Scheduled Maintenance Notification: Oracle Cloud Infrastructure

    We want to inform you that our infrastructure provider, Oracle Cloud Infrastructure (OCI), will be performing scheduled maintenance on their systems. Please note that this is an upstream maintenance managed entirely by Oracle, rather than an update on our end.

    Scope of Impact:

    • 🟢 Unaffected: Your dashboard will remain fully online and accessible. Any bots hosted on servers not listed in this notification will continue to operate normally.

    • 🔴 Affected: Only bots located on the specific hosts listed below will experience downtime.

    How this provider maintenance affects your services:

    • Expected Downtime: During Oracle's maintenance window, the affected underlying servers will be powered off. As a result, your bot will be unreachable for approximately 20 minutes, though some instances may take slightly longer.

    • Automatic Recovery: Once Oracle completes their maintenance, our systems will step in to automatically restart your bots. No action is required on your part.

    • Temporary Restrictions: To protect network stability during their update, the ability to change Bot-Hosts for bots on SCNX may be disabled starting 24 hours prior to the maintenance window.

    While this maintenance is outside of our direct control, routine updates by our providers are essential to guarantee the long-term reliability of our hosting environment. We apologize for any inconvenience this brief interruption may cause and appreciate your patience.

Mar 2026

Unplanned maintenance at our hosting partner
  • Resolved
    Resolved

    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.

  • Investigating
    Investigating

    We have been notified by our upstream hosting provider that they are currently conducting emergency, unplanned maintenance on the underlying physical infrastructure that houses our systems. Because this is an upstream hardware event, the resulting downtime is unfortunately out of our direct control.

    We are actively monitoring the situation and remain on standby. The provider's technicians have stated they are working to minimize the downtime as much as possible. We will immediately restore and verify all operations on our end the moment the provider concludes their maintenance.

    We sincerely apologize for the disruption and appreciate your patience. We will update this page as soon as we have more information or an "all-clear" from our hosting partner.

    Only Bots on the Bot-Hosts mentioned below are affected, other bots are running without issue. The dashboard and other core services are also unaffected.

Network issues on Bot-Manager & Backend
  • Resolved
    Resolved

    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

  • Update
    Update

    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.

  • Monitoring
    Monitoring

    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.

  • Identified
    Identified

    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.

  • Update
    Update

    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.

  • Investigating
    Investigating

    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.

Discord Bots aren't starting
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    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

Missing Servers in Dashboard
  • Postmortem
    Postmortem

    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!

  • Resolved
    Resolved

    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!

  • Monitoring
    Monitoring

    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!

  • Identified
    Identified

    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.

  • Investigating
    Investigating

    We are currently receiving an increased number of reports regarding missing servers in the dashboard. Specifically, users are unable to see servers where they hold Administrator permissions but are not the server owner.

    Our team is actively investigating these reports to identify the root cause. At this time, we have not yet been able to reproduce the issue on our end. Please note that all hosted bots and underlying systems are fully operational and working without any issues. We are monitoring the situation closely and will provide further updates as soon as we have more information or a potential fix. Thank you for your patience while we work on this.

Mar 2026 to May 2026

Next