ScootKit - Notice history

All bots hosted on Bot-Host #3 have automatically resumed their previous state, and Bot-Host #3 should be reachable as well. We apologize for this issue caused by a disruption in the data center of our hosting provider.

Our hosting provider has advised as that the host should be reachable again. Hosted bots are resuming their previous state and will be available in the following minutes. We're continuing to monitor the situation.

Our hosting provider has confirmed that this issue has been caused by disruption in their Dusseldorf data center. They are working on resolving this issue as fast as possible. We apologize for this inconvenience and are in contact with our provider to provide updates asap.

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.

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.

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.

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

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.