Duration: 2 hours and 33 minutes

Affected Components: Discord API

May 8, 19:52:41 GMT+0
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/>..

May 8, 20:33:06 GMT+0
Monitoring - Discord seems to have restored platform stability, but issues might continue to appear. .

May 8, 22:25:40 GMT+0
Resolved - This incident has been resolved..

Duration: 3 hours

Affected Components: Bot-Host #5

Apr 29, 05:30:00 GMT+0
Identified - **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..

Apr 29, 05:30:01 GMT+0
Identified - Maintenance is now in progress.

Apr 29, 08:30:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 5 days, 22 hours and 57 minutes

Affected Components: Bot-Host #16, Bot-Host #6, Bot-Host #13

Mar 27, 12:02:51 GMT+0
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. .

Mar 27, 14:25:48 GMT+0
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..

Duration: 49 minutes

Affected Components: SCNX Bot-Manager, SCNX Backend

Mar 26, 15:28:04 GMT+0
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. .

Mar 26, 15:28:55 GMT+0
Investigating - 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. .

Mar 26, 15:39:05 GMT+0
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..

Mar 26, 15:43:53 GMT+0
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..

Mar 26, 15:55:35 GMT+0
Monitoring - 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..

Mar 26, 16:17:07 GMT+0
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>.

Duration: 5 hours and 40 minutes

Affected Components: Discord API

Mar 25, 19:23:51 GMT+0
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>.

Mar 26, 01:03:57 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 21 minutes

Affected Components: SCNX Backend

Mar 6, 15:25:35 GMT+0
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 6, 15:33:23 GMT+0
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..

Mar 6, 15:50:18 GMT+0
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!.

Mar 6, 16:46:32 GMT+0
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!.

Mar 6, 16:53:46 GMT+0
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!.

Duration: 1 hour and 57 minutes

Affected Components: Bot-Host #36, Bot-Host #37, Bot-Host #35, Bot-Host #28, Bot-Host #23

Feb 23, 14:42:39 GMT+0
Investigating - We’re currently dealing with an outage affecting some of our non-premium servers. If your server or hosted bot is on one of these affected nodes, you might be experiencing timeouts or finding it completely unreachable. The other non-premium servers and all premium servers remains fully operational. To be transparent, the root cause of this is a major, ongoing infrastructure issue over at our hosting provider. Please know our team is doing everything we can to get this sorted out for those of you affected. We are continuously trying to get in contact with their support and engineering teams to get an ETA for a fix. Unfortunately, because their systems are so severely overloaded right now, their queues are backed up and they are currently unresponsive. We aren't just sitting on our hands while we wait. Our team is actively monitoring the routing and looking into any possible workarounds on our end to get that any unreachable infrastructure back online. We are fully staffed and ready to get everything operational again the exact second the provider fixes their network. We know this downtime is incredibly frustrating, and we really appreciate your patience while we push the host to get this resolved. We'll update this page the moment we finally get a response from them..

Feb 23, 15:03:37 GMT+0
Identified - 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..

Feb 23, 16:40:08 GMT+0
Resolved - 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!.

Duration: 2 hours and 31 minutes

Affected Components: SCNX Bot-Manager

Feb 18, 13:25:54 GMT+0
Identified - Hi everyone, Thanks to a quick report from our community, we've identified a critical bug in the current beta version. When executing a "Lockdown", there is an issue where your lockdown data might not be saved properly. Unfortunately, this results in permanent data loss, e.g. channel permissions being lost and having to reconfigure them manually. **To prevent this from happening to anyone else, please avoid using the Lockdown feature entirely until the next patch is released!** The good news: We have already found and fixed the underlying issue. The process has been rebuilt so that the lockdown will only trigger _after_ the system has successfully confirmed the data save. A patch is on the way and will hopefully be released **later today**. We will ping you here as soon as the update is live and the feature is safe to use again. Thank you for your patience, and a massive thank you to everyone helping us find and squash these bugs during the beta phase. Your support means the world to us! 💛.

Feb 18, 15:57:02 GMT+0
Resolved - This has been fixed in the **BETA-v3.22.1-6** version: <https://scnx.app/de/changelogs/beta-v3.22.1-6> Before using the lockdown feature, ensure that you have upgraded your bot by restarting it in the dashboard..

Duration: 1 hour and 30 minutes

Affected Components: Bot-Host #26

Jan 26, 16:00:00 GMT+0
Identified - Our hosting provider has notified us of planned maintenance on the underlying host system for Bot-Host#26. This is a "live maintenance" operation, and the provider expects the works to be completed without interrupting the availability of your bots. However, they have advised that in rare cases, manual intervention may be required, which could result in a brief downtime of approximately 10 minutes. Impact: * Only bots hosted on Bot-Host#26 are affected. * We expect full uptime, but please be aware of the slight risk of a \~10 minute disconnection during the maintenance window. * We're still not allowing customers to switch Bot-Hosts themselves at this time. If you are a premium customer, please contact our [customer support](https://scnx.app/help) to get switched BEFORE the maintenance starts..

Jan 26, 16:00:01 GMT+0
Identified - Maintenance is now in progress.

Jan 26, 17:30:00 GMT+0
Completed - Maintenance has completed successfully.

Duration: 2 days, 19 hours and 41 minutes

Affected Components: Bot-Host #4

Jan 11, 15:10:00 GMT+0
Identified - To ensure efficient and continuous hosting operations, we are performing several hardware upgrades for several of our servers in coordination with our hosting provider. All servers and bots hosted on them will remain online during this maintenance work, except for a short downtime (the "upgrade window"), usually about 5-20 minutes, sometime during the specified maintenance window. During this time, changing the bot host is not possible due to network stability reasons. Customers with a Professional plan who wish to switch to a Premium hosting server please contact our customer support. We will update this maintenance as soon as the upgrade window described above has been completed for the respective bot host. After the upgrade window has passed, there will be no more downtime for this bot host. We thank you for your understanding..

Jan 11, 15:10:00 GMT+0
Identified - To ensure efficient and continuous hosting operations, we are performing several hardware upgrades for several of our servers in coordination with our hosting provider. All servers and bots hosted on them will remain online during this maintenance work, except for a short downtime (the "upgrade window"), usually about 5-20 minutes, sometime during the specified maintenance window. During this time, changing the bot host is not possible due to network stability reasons. Customers with a Professional plan who wish to switch to a Premium hosting server please contact our customer support. We will update this maintenance as soon as the upgrade window described above has been completed for the respective bot host. After the upgrade window has passed, there will be no more downtime for this bot host. We thank you for your understanding..

Jan 11, 15:25:07 GMT+0
Identified - The hardware upgrade has been completed successfully on Bot-Host #15\. No additional downtime will occur for bots hosted on Bot-Host #15..

Jan 11, 15:25:07 GMT+0
Identified - The hardware upgrade has been completed successfully on Bot-Host #15\. No additional downtime will occur for bots hosted on Bot-Host #6..

Jan 11, 15:44:36 GMT+0
Identified - The hardware upgrade has been completed successfully on Bot-Host #8\. No additional downtime will occur for bots hosted on Bot-Host #8..

Jan 11, 15:46:35 GMT+0
Identified - The hardware upgrade has been completed successfully on Bot-Host #14\. No additional downtime will occur for bots hosted on Bot-Host #14..

Jan 11, 15:52:14 GMT+0
Identified - The hardware upgrade has been completed successfully on Bot-Host #12\. No additional downtime will occur for bots hosted on Bot-Host #12..

Jan 11, 15:52:52 GMT+0
Identified - The hardware upgrade has been completed successfully on Bot-Host #13\. No additional downtime will occur for bots hosted on Bot-Host #13..

Jan 11, 15:53:30 GMT+0
Identified - The hardware upgrade has been completed successfully on Bot-Host #19\. No additional downtime will occur for bots hosted on Bot-Host #19..

Jan 11, 15:56:24 GMT+0
Identified - The hardware upgrade has been completed successfully on Bot-Host #11\. No additional downtime will occur for bots hosted on Bot-Host #11..

Jan 11, 21:57:57 GMT+0
Identified - The hardware upgrade has been completed successfully on Bot-Host #16\. No additional downtime will occur for bots hosted on Bot-Host #16..

Jan 11, 22:05:53 GMT+0
Identified - While we wait on the last two bot hosts to complete the upgrade, we've made new slots available for bot creation. As a reminder, only Bot-Host #18 and Bot-Host #4 are waiting for the upgrade to complete, at least one of which requires more manual effort than estimated, leading to slight delays. From the experience of the last upgrades, we can confirm that average downtime is less than 5 minutes, excluding bot startup..

Jan 13, 11:46:00 GMT+0
Identified - The hardware upgrade has been completed successfully on Bot-Host #18\. No additional downtime will occur for bots hosted on Bot-Host #18..

Jan 14, 11:06:27 GMT+0
Completed - Maintenance has completed successfully..

Duration: 1 day, 1 hour and 51 minutes

Jan 10, 19:35:39 GMT+0
Investigating - We are currently investigating issues with bots hosted on Server 17, 20 and 24 being unable to connect to Discord and other parts of SCNX infrastructure. They might still appear online on SCNX and might work on Discord, but they respond slowly, or the dashboard isn't loading. We're working on starting up a new Bot-Host and migrating all bots as soon as possible. If you are affected and don't want to wait for an automatic migration, please ping @SCDerox on our [Discord](https://scootk.it/dc-en) with your Server-ID. .

Jan 11, 21:24:19 GMT+0
Monitoring - Remaining data from Bot-Host #20 and Bot-Host #24 have been migrated, and we're in the process of decommissioning the Bot-Hosts for now. It remains unclear whether we will be able to resume operations on that bot host in the future - for now, all bots previously hosted on Bot-Host #20 and Bot-Host #24 has been migrated to Bot-Host #38..

Jan 11, 21:26:57 GMT+0
Resolved - Since all data has been migrated, we're marking this incident resolved. The total downtime for bots was less than 5 hours, depending on when they were moved automatically. We apologize for the inconvenience caused and are working on ensuring that such issues can be mitigated more effectively in the future. For the affected bot hosts 20, 24 and 17, we're talking to the hosting provider to assess their continued suitability for our operations..

Jan 11, 21:33:03 GMT+0
Postmortem - ### **Executive Summary** On January 10, 2026, SCNX experienced a major outage affecting Bot-Hosts #17, #20, and #24\. The incident resulted in connectivity failures, preventing hosted bots from connecting to Discord and internal SCNX infrastructure. To resolve the issue, our engineering team provisioned a new server (Bot-Host #38) and migrated all affected workloads. The incident was marked fully resolved on January 11, 2026, following the successful migration of residual data. ### **Root Cause Analysis** The disruption was caused by a networking issue originating from the hosting provider for the affected servers. This network failure severed the connection between the bot hosts, Discord’s API, and other parts of the SCNX ecosystem. Due to the severity and nature of the networking problems, it remains unclear if operations can resume on the affected hardware in the future. ### **Impact** * **Affected Services:** Bots hosted on SCNX Bot-Hosts #17, #20, and #24. * **User Experience:** * Bots were unable to connect to Discord, resulting in downtime. * In some cases, bots appeared online but suffered from slow response times or failed to load the dashboard. * **Downtime:** The total downtime for individual bots was limited to less than 5 hours, depending on when the specific bot was automatically migrated to the new host. ### **Timeline of Events** _All times are in the time zone reported in the system logs._ **January 10, 2026** * **8:35 PM:** The team begins investigating reports of bots on Servers 17, 20, and 24 being unable to connect to Discord. * **9:58 PM:** Bot-Host #38 is provisioned as a temporary host to ensure service quality. Automatic migration of affected bots begins. * **10:58 PM:** Migration for all bots from Server 24 is completed. * **11:06 PM:** Migration for all bots from Server 20 is completed. * **11:20 PM:** All active bots are successfully moved to Bot-Host #38 and confirmed to be running without issues. **January 11, 2026** * **4:09 PM:** Work begins on discontinuing the affected hosts while a permanent solution is negotiated with the provider. * **6:50 PM:** Residual data from Bot-Host #17 is migrated, and the decommissioning process begins. * **10:24 PM:** Residual data from Bot-Hosts #20 and #24 is migrated, and the decommissioning process begins. * **10:26 PM:** Incident is marked as **Resolved**. ### **Resolution and Next Steps** Service was restored by migrating all active bots to a new node, Bot-Host #38\. Following the restoration of service, all remaining data was migrated off the affected infrastructure. To prevent recurrence: 1. **Infrastructure Decommissioning:** Bot-Hosts #17, #20, and #24 are currently being decommissioned as we assess the situation. 2. **Provider Review:** We are in active discussions with the hosting provider to assess their continued suitability for our operations. 3. **Mitigation Improvement:** We are reviewing our internal processes to ensure future connectivity issues can be mitigated even more effectively. We apologize for the inconvenience caused and appreciate your patience during this migration..

Jan 10, 20:58:59 GMT+0
Identified - We've added Bot-Host 38 as a temporary Bot-Host to move bots to to ensure hosting quality. We're working on moving affected bots automatically, but if you want your bot moved faster, please ping @scderox on our Discord. Likewise, we apologize for the issues and are working hard to get them fixed..

Jan 10, 21:58:15 GMT+0
Identified - All bots from Server 24 have been moved to our new Bot-Host and are now running without issues..

Jan 10, 22:06:33 GMT+0
Identified - All bots from Server 20 have been moved to our new Bot-Host and are now running without issues..

Jan 10, 22:20:03 GMT+0
Monitoring - We have moved all bots to the new Bot-Host #38, where they should be running without issues. We're working on restoring full access..

Jan 11, 15:09:38 GMT+0
Monitoring - We're currently working on discontinuing the affected Bot-Hosts for now, while we work with the provider to either find a solution for the networking problem or deactivate the servers for now. If your bot is experiencing issues, please contact our Customer Support, we will help you get it running as soon as possible..

Jan 11, 17:50:36 GMT+0
Monitoring - Remaining data from Bot-Host #17 has been migrated, and we're in the process of decommissioning the Bot-Host for now. It remains unclear whether we will be able to resume operations on that bot host in the future - for now, all bots previously hosted on Bot-Host #17 has been migrated to Bot-Host #38\. .

Duration: 13 minutes

Affected Components: SCNX Documentation

Jan 7, 08:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Jan 6, 22:18:36 GMT+0
Identified - Maintenance is now in progress..

Jan 6, 22:23:39 GMT+0
Identified - Maintenance is now in progress..

Jan 6, 22:31:46 GMT+0
Completed - Maintenance has completed successfully..

Duration: 12 days and 31 minutes

Affected Components: ScootKit Support System, DingBot - Discord Customer Suppot

Dec 19, 08:00:00 GMT+0
Identified - During the holiday season through **January 2nd**, our team will have limited availability. While we are still here for you via [**scnx.app/help**](https://scnx.app/help) and our [**Discord Server**](https://scootk.it/dc-de), please expect slightly longer response times during this period..

Dec 22, 08:00:00 GMT+0
Identified - During the holiday season through **January 2nd**, our team will have limited availability. While we are still here for you via [**scnx.app/help**](https://scnx.app/help) and our [**Discord Server**](https://scootk.it/dc-de), please expect slightly longer response times during this period. The SCNX Dashboard, hosted services, and other services are available during the holiday season without any interruptions or scheduled maintenance. We wish you and your loved ones a very happy holiday season and a relaxing break! Happy holidays, Your ScootKit Team.

Jan 3, 08:30:43 GMT+0
Completed - Our support availability is back to normal...

Duration: 7 hours and 55 minutes

Affected Components: SCNX Image CDN, scootk.it URL Shortener, ScootKit Issue Reporting, , SCNX Frontend, ScootKit Website, ScootKit Mail, ScootKit Discord Support System ("DingBot"), ScootKit Analytics, ScootKit Translations, ScootKit Support System, @SCNX Bot, SCNX Image Generation API, SCNX Bot-Manager, SCNX Backend, DingBot - Discord Customer Suppot, , SCNX RSS Hub, SCNX Documentation, SCNX → ScootKit →

Nov 19, 07:51:41 GMT+0
Postmortem - Cloudflare has published a full blog post detailing how this outage has occurred: https://blog.cloudflare.com/18-november-2025-outage/.

Nov 18, 14:52:51 GMT+0
Monitoring - Cloudflare believes that the issue has been resolved and everything should be working now. Find details here: <https://www.cloudflarestatus.com/incidents/8gmgl950y3h7>. We are still monitoring for issues on our side before we close this incident..

Nov 18, 10:20:00 GMT+0
Investigating - We use Cloudflare, a network infrastructure company, to offer our services around the world. Unfortunately, Cloudflare seems to be experiencing issues leading to some requests failing with error code 500. Cloudflare is working on a solution - during this time, our dashboard and other services may not be fully reachable. Hosted Bots are not affected..

Nov 18, 12:15:12 GMT+0
Identified - Cloudflare is continuing to work on a fix for this incident. Details here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7.

Nov 18, 18:15:02 GMT+0
Resolved - This incident has been resolved. Once again, this issue was caused by Cloudflare and we apologize for the issues. You can find more details here: <https://www.cloudflarestatus.com/incidents/8gmgl950y3h7>.

Duration: 15 hours and 3 minutes

Affected Components: DingBot - Discord Customer Suppot

Nov 3, 20:41:00 GMT+0
Identified - We are currently receiving an above-average amount of inquiries, which can result in an increased waiting time. We would like to apologize for this and thank you for your patience..

Nov 4, 11:43:49 GMT+0
Resolved - This incident has been resolved..

Duration: 25 days, 5 hours and 30 minutes

Affected Components: SCNX Backend

Oct 9, 13:30:34 GMT+0
Investigating - Due to recent Verification of Payee (VoP) regulatory changes starting on October 9, 2025, banks are required to add an additional verification step for customers wishing to send SEPA credit payments. When using sepa transfer payments on SCNX, this change may affect your ability to pay for your subscription or purchase. Due to an ongoing issue with our partner Stripe, some verification warnings may be incorrect. They are currently investigating the issue and we will update you once we have additional information to share. While this issue continues, we recommend that our customers skip any payee verification warning after manually verifying that all details of the transaction are correct. You can find the correct payment information in your confirmation email and in the dashboard. We're sorry for any trouble this issue may have caused. Please let us know if you have any additional questions about the issue by contacting our billing team on scnx.app/help..

Oct 17, 13:36:04 GMT+0
Resolved - We have received confirmation that VoP is now fully working again. If you are still experiencing issues, please double check your dashboard for the payment instructions. Please note that instead of "SCNX by ScootKit", the account holder for the transfer will now be "ScootKit UG (haftungsbeschränkt)" (the full legal name instead of the brand name), so please update your transfer if required. Depending on your bank, you might still be pointed to a slightly different bank account holder without special characters in the name - in such cases, we recommend going with the bank's suggestion to avoid issues (see screenshot of a possible pop-up)..

Duration: 1 hour and 11 minutes

Affected Components: @SCNX Bot

Sep 27, 10:20:06 GMT+0
Resolved - We are pleased to confirm that the incident affecting the `@SCNX-Bot` is now fully resolved, and all services have returned to normal operation as of 12:20 PM CEST. Earlier this morning, our monitoring systems detected a disruption that was impacting some of the backend features of the `@SCNX-Bot`. Our engineering team immediately investigated and traced the root cause to a performance degradation in a database cluster dedicated to the bot's administrative functions. This resulted in the temporary unavailability of tools such as backups and analytics. We want to emphasize that the impact was strictly limited to these supplementary administrative features. All critical, core functionalities, including the operation of all custom bots and customer-facing hosted experiences, were completely unaffected and remained 100% operational throughout this period. Our team was able to resolve the database bottleneck by deploying an optimization, which allowed services to recover quickly without broader impact. To prevent a recurrence, we are already implementing more sensitive alerting on our database metrics and are conducting a full review to further strengthen our failover procedures. We sincerely apologize for any inconvenience the temporary loss of these administrative tools may have caused. While we have confirmed a full recovery, please do not hesitate to contact our [customer support team](https://scnx.app/help) if you continue to experience any persistent issues. We appreciate your patience and understanding..

Sep 27, 09:54:50 GMT+0
Monitoring - We have implemented a fix for the `@SCNX-Bot` ahead of schedule. Our team was able to resolve the underlying problem without the need for the planned infrastructure migration. All services for the `@SCNX-Bot`, including backups and analytics, have been restored and should now be operating normally. Our team will continue to monitor the system closely to ensure the stability of the fix. We will post a final "Resolved" message once we are confident the issue is fully behind us. If you continue to experience any issues, please contact our [support team](https://scnx.app/help)..

Sep 27, 09:08:48 GMT+0
Investigating - We are aware of an ongoing issue preventing access to several features of the `@SCNX-Bot`, including backups and analytics. We understand this may disrupt your workflow and we apologize for the inconvenience. Please be assured that all custom bots and hosted experiences are functioning normally and are not impacted..

Sep 27, 09:24:44 GMT+0
Identified - We have identified the root cause of the issue affecting the `@SCNX-Bot`. To restore full functionality, we are currently performing emergency maintenance which involves migrating the bot's infrastructure. This is a necessary step to ensure service stability. During this maintenance period, features like backups and analytics for the `@SCNX-Bot` will remain unavailable. Custom bots and hosted experiences continue to operate normally. We appreciate your patience as our team works to complete this migration. Our next update will be posted by **12:30 PM CEST**..

Duration: 16 hours and 57 minutes

Affected Components: ScootKit Discord Support System ("DingBot"), ScootKit Website, SCNX Frontend, SCNX Image CDN, ScootKit Analytics, scootk.it URL Shortener, SCNX Backend, ScootKit Support System, SCNX Image Generation API, SCNX Bot-Manager, ScootKit Translations, DingBot - Discord Customer Suppot

Jul 25, 11:14:24 GMT+0
Resolved - This incident has been resolved..

Jul 24, 21:08:45 GMT+0
Identified - We have completed most of the emergency migration steps and are now slowly restoring service to affected components. Follow this page for update. Thanks to our emergency protocols, our current estimated time of full recovery is within 1-2 hours. At this time, access to DingBot (customer service on our Discord) and our website have been restored. .

Jul 24, 23:46:03 GMT+0
Monitoring - Yesterday, our services experienced an outage that began at 20:16\. We are pleased to report that all systems have now been restored as of 1:15 today, and we have confirmed that no customer data was lost or compromised**.** No SCNX-hosted bots were affected by this outage. The outage was triggered by a hardware failure at one of our third-party infrastructure providers. Our investigation revealed that this failure, combined with a lack of timely support from the provider, did not meet our standards for reliability and service. In response, we have accelerated our long-term infrastructure strategy by migrating affected services to our high-availability environment with a new primary hosting partner. This move was completed successfully and will provide enhanced stability and performance for the future. We are currently monitoring all systems closely to ensure continued stability. While all services are operating normally, if you notice any unusual behavior, please do not hesitate to contact our [customer support](https://scnx.app/help). We sincerely apologize for the disruption and frustration this outage caused. We are committed to providing a reliable service, and we are confident that the steps taken today will ensure a more resilient platform going forward. Thank you for your patience and understanding..

Jul 24, 19:37:09 GMT+0
Identified - It seems like a technical issue at our hosting provider caused significant issues to our key points in our infrastructure. We're migrating affected servers to a different hosting provider which might take a while. We apologize for the issues and are committed to get things running again as soon as possible. .

Jul 24, 18:16:54 GMT+0
Investigating - We are currently investigating an issue with connections to an important part of our infrastructure leading to temporary issues. Hosted bots are not affected..

Jul 24, 22:05:21 GMT+0
Identified - We have restored most core components, and SCNX can be used again. We're still working on restoring remaining components and monitoring performance..

Duration: 3 hours and 47 minutes

Affected Components: SCNX Frontend, SCNX Backend

Jun 16, 14:47:00 GMT+0
Completed - Maintenance has completed successfully. The actual downtime started at 13:04 and ended at 14:05. Times in CEST (GMT+2)..

Jun 16, 11:00:01 GMT+0
Identified - Maintenance is now in progress.

Jun 16, 11:00:00 GMT+0
Identified - Due to a defect in the hardware, some key infrastructure nodes will be temporarily offline due to a replacement of the motherboard in the servers. This will lead to a downtime of approximately one hour during the specified time interval. During this time, the SCNX Dashboard won't be reachable, but hosted bots are not affected..

Affected Components: SCNX Backend

Jun 6, 18:29:46 GMT+0
Investigating - SCNX Backend is down at the moment. This incident was automatically created by Instatus monitoring..

Jun 6, 18:31:37 GMT+0
Resolved - SCNX Backend is back up. This incident was automatically resolved by Instatus monitoring..

Affected Components: SCNX Backend

May 29, 22:49:11 GMT+0
Resolved - SCNX Backend is back up. This incident was automatically resolved by Instatus monitoring..

May 29, 22:45:52 GMT+0
Investigating - SCNX Backend is down at the moment. This incident was automatically created by Instatus monitoring..

Duration: 21 hours and 17 minutes

Affected Components: SCNX Bot-Manager

Apr 29, 18:26:08 GMT+0
Identified - Paste contents have been restored..

Apr 28, 21:30:01 GMT+0
Identified - Our hosting provider has reported an issue with parts of our infrastructure that are responsible for providing the image generation feature and the paste features. Because of this, applications and ticket logs can't be stored, and image generation will time out. Our hosting provider is responsible for this issue, and they are working on getting this fixed as soon as possible. .

Apr 29, 18:47:14 GMT+0
Resolved - This has been resolved. If you are still running into issues, please don't hesitate to contact us on [scnx.app/help](https://scnx.app/help) or on our [Discord](https://scootk.it/dc)..

Apr 29, 18:39:45 GMT+0
Monitoring - All bots from Server 1 have been moved to Server 14 and need to be manually started again. Server 1 has been removed. We apologize for this issue. If your bot has been affected, and you are using a paid plan, please request compensation for the lost time here: <http://scnx.app/user/downtime-refund>. If you have contacted us via E-Mail in the last 48 hours, please check if you have received an automatic response. If not, please resend the email so we can get to it faster. .

Apr 29, 10:15:37 GMT+0
Identified - These issues should be resolved, but Weblate and Bot-Host #1 remain offline. Additionally, past logs and paste content might be temporarily unavailable, as we work on a solution..

Affected Components: SCNX Backend

Apr 27, 00:41:52 GMT+0
Investigating - SCNX Backend is down at the moment. This incident was automatically created by Instatus monitoring..

Apr 27, 07:39:18 GMT+0
Resolved - SCNX Backend is back up. This incident was automatically resolved by Instatus monitoring..

Duration: 3 days, 22 hours and 36 minutes

Affected Components: SCNX Image CDN

Mar 28, 13:47:06 GMT+0
Investigating - We are currently investigating a high amount of image upload failures..

Mar 28, 13:47:45 GMT+0
Identified - Our investigation shows that this issue lies with our hosting provider, we're working with them to resolve this issue as fast as possible..

Apr 1, 12:22:41 GMT+0
Resolved - This issue has been resolved and uploading is possible again. We apologize for the inconvenience..

Mar 29, 21:59:42 GMT+0
Identified - This issue is still being worked on and has been passed to the development team at our hosting provider - unfortunately, they only work on work days, so we expect the next update to be posted on Monday. We apologize for the issues and want to stress that issues like this lay outside our control..

Duration: 7 hours

Affected Components: SCNX Image Generation API, SCNX Frontend

Mar 10, 19:00:00 GMT+0
Completed - Maintenance has completed successfully.

Mar 10, 12:00:00 GMT+0
Identified - Our hosting provider is migrating images to a new physical location. During this time, you won't be able to access, upload or create images on SCNX. .

Mar 10, 12:00:01 GMT+0
Identified - Maintenance is now in progress.

Duration: 59 minutes

Affected Components: SCNX Bot-Manager

Feb 24, 14:50:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Feb 24, 15:21:42 GMT+0
Identified - The Bot-Manager is reachable again, but temporary outages might occur as we're finishing the maintenance. .

Feb 24, 14:50:01 GMT+0
Identified - Maintenance is now in progress.

Feb 24, 15:49:20 GMT+0
Completed - We've concluded the maintenance process..

Affected Components: SCNX Backend

Feb 19, 15:54:15 GMT+0
Resolved - SCNX Backend is back up. This incident was automatically resolved by Instatus monitoring..

Feb 19, 15:39:54 GMT+0
Investigating - SCNX Backend is down at the moment. This incident was automatically created by Instatus monitoring..

Affected Components: Bot-Host #16

Feb 12, 23:11:04 GMT+0
Investigating - Bot-Host #16 is down at the moment. This incident was automatically created by Instatus monitoring..

Feb 12, 23:13:58 GMT+0
Resolved - Bot-Host #16 is back up. This incident was automatically resolved by Instatus monitoring..

Affected Components: Bot-Host #21

Feb 12, 23:04:16 GMT+0
Investigating - Bot-Host #21 is down at the moment. This incident was automatically created by Instatus monitoring..

Feb 12, 23:15:31 GMT+0
Resolved - Bot-Host #21 is back up. This incident was automatically resolved by Instatus monitoring..

Affected Components: Bot-Host #22

Feb 12, 23:03:21 GMT+0
Investigating - Bot-Host #22 is down at the moment. This incident was automatically created by Instatus monitoring..

Feb 12, 23:09:32 GMT+0
Resolved - Bot-Host #22 is back up. This incident was automatically resolved by Instatus monitoring..

Affected Components: Bot-Host #21

Feb 12, 00:36:03 GMT+0
Resolved - Bot-Host #21 is back up. This incident was automatically resolved by Instatus monitoring..

Feb 12, 00:22:42 GMT+0
Investigating - Bot-Host #21 is down at the moment. This incident was automatically created by Instatus monitoring..

Affected Components: Bot-Host #21

Feb 11, 15:56:40 GMT+0
Investigating - Bot-Host #21 is down at the moment. This incident was automatically created by Instatus monitoring..

Feb 11, 15:58:37 GMT+0
Resolved - Bot-Host #21 is back up. This incident was automatically resolved by Instatus monitoring..

Affected Components: Bot-Host #22

Jan 29, 23:20:29 GMT+0
Resolved - Bot-Host #22 is back up. This incident was automatically resolved by Instatus monitoring..

Jan 29, 23:19:07 GMT+0
Investigating - Bot-Host #22 is down at the moment. This incident was automatically created by Instatus monitoring..

Duration: 42 minutes

Affected Components: SCNX Backend

Jan 10, 13:57:13 GMT+0
Completed - Maintenance has completed successfully..

Jan 10, 13:15:00 GMT+0
Identified - To ensure high availability our services, we're conducting a temporary maintenance on the SCNX Backend infrastructure, leading to a small downtime. No bots are affected..

Jan 10, 13:15:01 GMT+0
Identified - Maintenance is now in progress.

Duration: 12 hours and 10 minutes

Affected Components: SCNX Backend, SCNX Frontend

Nov 16, 09:24:54 GMT+0
Completed - Maintenance has completed successfully..

Nov 15, 21:15:01 GMT+0
Identified - Maintenance is now in progress.

Nov 15, 21:15:00 GMT+0
Identified - The legal operator of SCNX is changing. We're conducting a maintenance to implement changes and to update required systems. Please read our FAQ for details: <https://docs.scnx.xyz/docs/scnx/migration-guide/>.

Duration: 14 minutes

Affected Components: SCNX Image Generation API, ScootKit Analytics, ScootKit Mail, ScootKit Translations, ScootKit Website

Aug 28, 16:13:19 GMT+0
Completed - The update has concluded, all systems are now reachable again..

Aug 28, 15:58:57 GMT+0
Identified - Due to an issue regarding URL parsing in certain legacy PHP applications leading to Open Redirect possibilities in certain legacy applications (such as paste.scootkit.net), we'll be updating a core component on one of our core production machines. Even though most of our services are not affected, the update of the core component will lead to some downtime. .

Duration: 7 days, 17 hours and 6 minutes

Affected Components: ScootKit Discord Support System ("DingBot"), ScootKit Support System

Aug 4, 08:44:00 GMT+0
Identified - We're back: You can contact us again on Discord by filling a ticket, and our Discords are no longer in read-only mode 🎉 Please note that we still have limited customer service availability for the rest of this month, read more here: <https://blog.scootkit.net/were-on-summer-break/>..

Aug 28, 09:10:32 GMT+0
Completed - We're so back 🥳.

Jul 20, 16:04:37 GMT+0
Identified - Currently, our customer service is operating in **Limited availability** mode. Visit <https://blog.scootkit.net/were-on-summer-break/> to learn more..

Jul 20, 16:00:20 GMT+0
Identified - During our summer break, our customer services will have higher wait- and processing times. Our customer service can't be reached between July 28 and August 3, tickets opened during that week will be answered after this time period..

Jul 27, 16:31:50 GMT+0
Identified - As explained in our blog post (<https://blog.scootkit.net/were-on-summer-break/>), our customer service won't be available until August 4\. We've disabled the ability to open new tickets a few hours ago and will lock both of our Discord servers later today. We'll likely be back on August 3\. or 4. You can still contact billing / legal support as usual, but requests won't be answered until August 4\. Certain legal requests will still be answered as required by law. .

Duration: 3 hours and 5 minutes

Affected Components: Bot-Host #18

May 30, 21:08:27 GMT+0
Completed - Bot-Host #18 has been set up and can now be used. .

May 30, 18:03:00 GMT+0
Identified - We're setting up Bot-Host #18\. The Bot-Host can't be used during this time, but will be available after the initial setup has concluded..