ScootKit - Notice history

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 if you continue to experience any persistent issues. We appreciate your patience and understanding.

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.

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.

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.

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.

We have restored most core components, and SCNX can be used again. We're still working on restoring remaining components and monitoring performance.

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.

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.