ScootKit - Notice history

Experiencing partially degraded performance

SCNX

Operational

SCNX Frontend - Operational

100% - uptime
May 2024 · 100.00%Jun · 100.00%Jul · 100.00%
May 2024
Jun 2024
Jul 2024

SCNX Backend - Operational

100% - uptime
May 2024 · 100.00%Jun · 100.00%Jul · 100.00%
May 2024
Jun 2024
Jul 2024

SCNX Bot-Manager - Operational

100% - uptime
May 2024 · 100.00%Jun · 100.00%Jul · 100.00%
May 2024
Jun 2024
Jul 2024

SCNX Image Generation API - Operational

SCNX Documentation - Operational

SCNX RSS Hub - Operational

ScootKit

Degraded performance

ScootKit Website - Operational

100% - uptime
May 2024 · 100.00%Jun · 99.576%Jul · 100.00%
May 2024
Jun 2024
Jul 2024

ScootKit Discord Support System ("DingBot") - Degraded performance

ScootKit Support System - Degraded performance

ScootKit Analytics - Operational

ScootKit Mail - Operational

scootk.it URL Shortener - Operational

ScootKit Issue Reporting - Operational

ScootKit Translations - Operational

Third Parties

Operational

Discord API - Operational

Stripe API - Operational

OpenAI API - Operational

Cloudflare Pages - Operational

Cloudflare CDN - Operational

Notice history

Jul 2024

We're taking a summer break: Limited customer services availability
Scheduled for 07-20-2024 at 4:00 PM – 08-28-2024 at 10:00 AM about 1 month
  • In progress
    07-20-2024 at 4:04 PM
    In progress
    07-20-2024 at 4:04 PM

    Currently, our customer service is operating in Limited availability mode. Visit https://blog.scootkit.net/were-on-summer-break/ to learn more.

  • Planned
    07-20-2024 at 4:00 PM
    Planned
    07-20-2024 at 4:00 PM

    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.

Jun 2024

Bot-Host #10 and some ScootKit services unreachable
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified
    We are continuing to work on a fix for this incident.
  • Resolved
    Resolved

    Our data shows that affected services are reachable again, we apologize for any inconvenience caused. This downtime was a result of an issue at our hosting provider.

  • Identified
    Identified

    It seems like Bot-Host #10 and the affected services have issues again. We're in contact with our hosting provider, and they are working on resolving this. Once again, we apologize for this inconvenience.

  • Resolved
    Resolved

    After additional checks and monitoring, we can confirm that both Bot-Host #10 and other affected ScootKit services are running without issues. This incident was caused by an issue at our hosting provider, and we apologize for any inconvenience caused.

  • Monitoring
    Monitoring

    We've received notice that the server is reachable again. We're still monitoring the situation, but all ScootKit services and Bot-Host #10 should be reachable again.

  • Identified
    Identified

    It seems like this issue is caused by an issue at our hosting provider. We're in contact with them, and they are working on resolving this issue as fast as possible. We apologize for any inconvenience caused.

  • Investigating
    Investigating

    Automated monitoring detected that a server hosting Bot-Host #10 and some other ScootKit Services, including DingBot (our Discord support system) can't be reached right now. Our team has been notified and we're investigating this incident.

May 2024

Connection to Bot-Host #17 unstable
  • Postmortem
    Postmortem

    A small typo in a DNS record created due to the manual setup steps of another bot-host made this server unreachable for a prolonged period of time. Our processes after the initial report of the downtime focused on identifying the issue on our hosting infrastructure, instead of reviewing recently taken actions which could have highlighted configuration changes in our DNS configuration. The processes have been made optimized for this case and call for a proper review of recent changes to infrastructure in addition to the already existing issue identification steps.

  • Resolved
    Resolved

    This issue has been resolved, Bot-Host #17 is reachable again. Please note that hosted bots were not affected.

    This incident was caused by a misconfiguration of DNS records, made in error when setting up infrastructure for another Bot-Host. We apologize for the inconvenience caused.

    As no bots were offline, this incident is ineligible for our voluntary refund policy.

  • Monitoring
    Monitoring

    We've rolled out a fix for this issue and are monitoring results. Affected customers should be able to access their bots again. Hosted bots were not affected in this incident.

  • Identified
    Identified

    We've identified a potential misconfiguration that might cause this issue. We're rolling out a fix.

  • Investigating
    Update

    We've identified that connectivity issues are limited to Bot-Host #17 - Bots hosted on Bot-Host #17 are not affected.

    We're continuing to investigate the root cause of this issue.

  • Investigating
    Investigating

    We've received reports of an increased number of connections to Bot-Hosts failing. We're investigating.

May 2024 to Jul 2024

Next