ScootKit - Notice history

All systems operational

Operational

SCNX Frontend - Operational

100.00% uptime
Aug 2026 · 100.00%Sep · 100.00%Oct · 100.00%

Previous page

Next page

Aug 2026
Sep 2026
Oct 2026

SCNX Backend - Operational

99.929% uptime
Aug 2026 · 99.792%Sep · 100.00%Oct · 100.00%

Previous page

Next page

Aug 2026
Sep 2026
Oct 2026

SCNX Bot-Manager - Operational

100.00% uptime
Aug 2026 · 100.00%Sep · 100.00%Oct · 100.00%

Previous page

Next page

Aug 2026
Sep 2026
Oct 2026

SCNX Image Generation API - Operational

SCNX Documentation - Operational

SCNX Image CDN - Operational

@SCNX Bot - Operational

99.058% uptime
Aug 2026 · 99.476%Sep · 100.00%Oct · 97.758%

Previous page

Next page

Aug 2026
Sep 2026
Oct 2026

Support Bot Log Hosting & Customer Dashboard (modmail.net) - Operational

100.00% uptime
Aug 2026 · 100.00%Sep · 100.00%Oct · 100.00%

Previous page

Next page

Aug 2026
Sep 2026
Oct 2026
Operational

ScootKit Website - Operational

100.00% uptime
Aug 2026 · 100.00%Sep · 100.00%Oct · 100.00%

Previous page

Next page

Aug 2026
Sep 2026
Oct 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.00% uptime
Aug 2026 · 100.00%Sep · 100.00%Oct · 100.00%

Previous page

Next page

Aug 2026
Sep 2026
Oct 2026
Operational

Discord API - Operational

Stripe API - Operational

OpenAI API - Operational

Cloudflare CDN - Operational

Notice history

View current status

Oct 2026

Bot hosting outage on Instance 8, Instance 13, Instance 16
ResolvedMajor outage49 minutes
  • ResolvedUTC
    This incident has been resolved and all affected bots are back online. The outage lasted 1h 36m and was caused by an infrastructure failure at our upstream hosting provider. Bots reconnect automatically, so no action is needed on your side. We're sorry for the disruption, and we monitor our providers continuously to hold them to the standard you expect from us.
  • InvestigatingUTC
    We are investigating an outage affecting bots hosted on Instance 8, Instance 13, Instance 16. The issue appears to originate at the upstream hosting provider's infrastructure, not within SCNX systems. Affected bots are currently offline on Discord. Our team is actively working on this and has escalated to the hosting provider with diagnostic data. We will post updates here as the situation develops.
Bot hosting outage on Instance 35
ResolvedMajor outage2 hours 5 minutes
  • ResolvedUTC
    This incident has been resolved and all affected bots are back online. The outage lasted 2h 14m and was caused by an infrastructure failure at our upstream hosting provider. Bots reconnect automatically, so no action is needed on your side. We're sorry for the disruption, and we monitor our providers continuously to hold them to the standard you expect from us.
  • UpdateUTC
    We've confirmed that the issue lies with our hosting provider and have contacted them. They have confirmed that they are investigating the outage and will get back to us shortly.
  • IdentifiedUTC
  • InvestigatingUTC
    We are investigating an outage affecting bots hosted on Instance 35. The issue appears to originate at the upstream hosting provider's infrastructure, not within SCNX systems. Affected bots are currently offline on Discord. Our team is actively working on this and has escalated to the hosting provider with diagnostic data. We will post updates here as the situation develops.
Backups via the @SCNX Bot are unavailable
ResolvedMajor outage62 hours 52 minutes
  • ResolvedUTC

    This incident has been resolved. We'll add additional warnings and banners shortly.

    We've updated our docs since and added improved notices and bug fixes for the new backup system.

  • MonitoringUTC

    We've notified all Backups+ customers with additional details and options.

    With this change, we've completed the switch from the SCNX-Bot to the CustomBot Backups System. We'll continue rolling out NextGen to additional hosting locations so more users can use backups.

    Additionally, we'll be adding new warning banners and information in the dashboard to inform users about this change.

  • IdentifiedUTC

    Today, we published the v3.25.1 update in the stable branch.

    You will need to update your bot to use the Backups feature. If you had automatic backups enabled, you might need to re-enable that feature.

    If you are on a NextGen host, have updated your bot, and are still not seeing the new Backups interface, please try manually stopping and then starting your bot again.

    We'll shortly add additional warning banners and information in the dashboard to make this change more clear.

    We'll also separately reach out to customers who purchased Backups+ directly and inform them of the change.

  • InvestigatingUTC

    Due to recent changes on Discord, we are retiring backup functionality on the SCNX Bot and transitioning all server backups to CustomBot.

    SCNX Bot can no longer create new backups. Since analytics have also moved to your CustomBot, this means that you can finally kick the SCNX bot from your server.

    Requirements for CustomBot Backups

    To create backups using your CustomBot, please ensure:

    • NextGen Hosting: Your CustomBot is running on a hosting location marked NextGen in your server list (Learn how to switch hosting locations).

    • Bot Version: Your CustomBot is running version v3.25.1 or higher.

    Once your bot meets these requirements, you can access the new Backups Page, which introduces upgraded capabilities such as backing up open forum posts and more.

    Backups+ Subscribers

    • All Backups+ perks and features remain fully active when using CustomBot and now include additional features such as custom encryption keys.

    • Your Backups+ purchase has been automatically transferred.

    • We will reach out to Backups+ customers over the coming week with further details and additional options.

    Availability & Rollout

    Version v3.25.1 will be released to the stable branch shortly. If you want immediate access, you can switch your bot to the beta branch today.

Sep 2026

SEP19
We're conducting required database maintenance
CompletedMaintenance18 minutes
  • Completed09-19-2026 at 2:18 PMUTC

    Maintenance has been completed successfully. SCNX experienced maintenance downtime of approximately 5 minutes due to the migration. Thank you for your patience.

  • In progress09-19-2026 at 1:58 PMUTC

    Maintenance is now in progress.

  • Planned09-19-2026 at 11:36 AMUTC

    We have scheduled routine system maintenance for the period specified below.

    We are upgrading our core infrastructure and data replication systems to improve our system's performance, stability, and security.

    What this means for you: We do not expect any extended service outages, and you can continue using the platform as usual. However, you may experience brief, temporary slowdowns or momentary connection blips during this window. If you encounter an error, waiting a few seconds and refreshing your page should resolve it.

    Thank you for your patience while we complete these essential updates.

Bot hosting outage on Instance 39
ResolvedMajor outage26 minutes
  • ResolvedUTC
    This incident has been resolved and all affected bots are back online. The outage lasted 14 minutes and was caused by an infrastructure failure at our upstream hosting provider. Bots reconnect automatically, so no action is needed on your side. We're sorry for the disruption, and we monitor our providers continuously to hold them to the standard you expect from us.
  • UpdateUTC
    We're seeing recovery and bots are starting again, please be patient while the host system starts your bot automatically.
  • IdentifiedUTC
  • InvestigatingUTC
    We are investigating an outage affecting bots hosted on Instance 39. The issue appears to originate at the upstream hosting provider's infrastructure, not within SCNX systems. Affected bots are currently offline on Discord. Our team is actively working on this and has escalated to the hosting provider with diagnostic data. We will post updates here as the situation develops.
Discord is experiencing an outage
ResolvedMajor outage1 hour 31 minutes
  • ResolvedUTC
    This incident has been resolved.
  • IdentifiedUTC

    Due to an issue at Discord, bots on SCNX might be affected and might not work as expected.

    Details at Discord: https://discordstatus.com/incidents/btdsd2y407t5

Bot hosting outage on Instance 14, Instance 31
ResolvedMajor outage11 minutes
  • ResolvedUTC
    This incident has been resolved and all affected bots are back online. The outage lasted 19 minutes and was caused by an infrastructure failure at our upstream hosting provider. Bots reconnect automatically, so no action is needed on your side. We're sorry for the disruption, and we monitor our providers continuously to hold them to the standard you expect from us.
  • InvestigatingUTC
    We are investigating an outage affecting bots hosted on Instance 14, Instance 31. The issue appears to originate at the upstream hosting provider's infrastructure, not within SCNX systems. Affected bots are currently offline on Discord. Our team is actively working on this and has escalated to the hosting provider with diagnostic data. We will post updates here as the situation develops.

Aug 2026

AUG15
We're upgrading Bot-Hosts
CompletedMaintenance2 hours 6 minutes
  • Completed08-15-2026 at 9:06 PMUTC
    Maintenance has completed successfully.
  • In progress08-15-2026 at 6:56 PMUTC
    Maintenance is now in progress.
  • Planned08-15-2026 at 6:56 PMUTC

    We are upgrading the hosts listed below to our next-gen hosting platform.

    Bots on these hosts restart once during the window. Most are back within a few minutes, larger hosts can take up to 20 minutes. Nothing changes for you: your configuration, data and settings all stay as they are.

    During the maintenance you won't be able to access or manage your bot in the dashboard, but for most of it your bot will still continue to work on Discord.

    What the upgrade brings:

    • Logs survive a restart. Restarting a bot no longer wipes its logs, so you can still see what happened before a crash.

    • Downtime alerts. Get notified on Discord, by email, on Telegram or in the dashboard when your bot goes down, with the steps to fix it and an all-clear when it recovers. Off by default, configurable per bot.

    • RAM and CPU graphs. See how much of its resources your bot actually uses over the last 24 hours, 7 days or 30 days.

    • More resources on higher plans. Your plan now determines your bot's memory, and an upgrade applies without a restart.

    • Automatic recovery. Short network or Discord problems no longer leave a bot offline until someone notices.

    • Improved stability and Ressource use. We've made significant improvements on the stability of hosted bots and the use of allocated ressources on individual hosting locations.

    Our team is working to minimize the hosting impact on your operations. We understand that downtime significantly affects your operations, but this maintenance is required to continue the safe and stable long-term hosting for your bot.

    We value your time and appreciate your kind patience during this required maintenance period.

Discord is experiencing an outage
ResolvedMajor outage15 minutes
  • ResolvedUTC
    This incident has been resolved.
  • InvestigatingUTC

    Due to an issue at Discord, bots on SCNX might be affected and might not work as expected.

    Details at Discord: https://discordstatus.com/incidents/pcg3nsfq6l2y

A Discord outage is affecting SCNX Bots
ResolvedMajor outage37 minutes
  • ResolvedUTC

    Discord has announced that this incident has been resolved.

  • IdentifiedUTC

    Due to an issue at Discord, bots on SCNX might be affected and might not work as expected.

    Details at Discord: https://discordstatus.com/

Bot hosting outage on Instance 38
ResolvedMajor outage5 hours 20 minutes
  • ResolvedUTC
    This incident has been resolved and all affected bots are back online. The outage lasted 0h 20m and was caused by an infrastructure failure at our upstream hosting provider. Bots reconnect automatically, so no action is needed on your side. We're sorry for the disruption, and we monitor our providers continuously to hold them to the standard you expect from us.
  • InvestigatingUTC
    We are investigating an outage affecting bots hosted on Instance 38. The issue appears to originate at the upstream hosting provider's infrastructure, not within SCNX systems. Affected bots are currently offline on Discord. Our team is actively working on this and has escalated to the hosting provider with diagnostic data. We will post updates here as the situation develops.
Increased numbers of login failures to SCNX
ResolvedMajor outage5 hours 25 minutes
  • ResolvedUTC

    This incident has been resolved; the last component (@SCNX-Bot) has recovered. The outage of the SCNX Dashboard and some other services (including DingBot, Membership, FeatureBoard) lasted less than 2 hours; the outage of SCNX Bot Services ("Backups" and "Analytics) lasted around five hours due to a migration between hosting locations. Bots did not fail due to this outage, except when bots required an SCNX Backend connection (e.g. when restarting or when using AI features). We apologize for the downtime and are investigating the root cause. If you have a paid plan, you can request a compensation: https://scnx.app/de/user/support/new?topic=cmnhok1np00kjtghxayiwcwmq.

  • MonitoringUTC

    We implemented a temporary fix and are working on getting things up again. Thank you for remaining patient during this time.

  • InvestigatingUTC

    We are currently investigating an incident that affects a number of users trying to log in into SCNX.

Previous

Aug 2026 to Oct 2026

Next

Imprint • Privacy Policy • "ScootKit" is a trademark, registered in Germany.