ScootKit - Temporary connection issues – Incident details

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.