ScootKit - Notice history

All systems operational

Operational

SCNX Frontend - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

SCNX Backend - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

SCNX Bot-Manager - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

SCNX Image Generation API - Operational

SCNX Documentation - Operational

SCNX RSS Hub - Operational

SCNX Image CDN - Operational

@SCNX Bot - Operational

100% - uptime
Sep 2025 · 99.831%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025
Operational

ScootKit Website - Operational

100% - uptime
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025

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
Sep 2025 · 100.00%Oct · 100.00%Nov · 100.00%
Sep 2025
Oct 2025
Nov 2025
Operational

Discord API - Operational

Stripe API - Operational

OpenAI API - Operational

Cloudflare Pages - Operational

Cloudflare CDN - Operational

Notice history

Oct 2025

Verification of Payee Warning for incoming SEPA bank transfer payments
  • Resolved
    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).

  • Investigating
    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.

Sep 2025

Issues with the @SCNX-Bot
  • Resolved
    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 if you continue to experience any persistent issues. We appreciate your patience and understanding.

  • Monitoring
    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.

  • Identified
    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.

  • Investigating
    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 2025 to Nov 2025

Next