Past Incidents

We have fixed the whole issue on our network level and on all connected devices.

We have also filed a report with the responsible data protection authority, and after further measures we were unable to detect any misuse of data to third parties.

We have resumed our activities from 08:00 today and apologise for any inconvenience caused.

We will continue to closely monitor all network and email activity for another 72 hours. If no further problems occur, we will close this incident.

The Trojan could not cause any real damage due to the quick reaction of the employee. We were able to remove it very easily from our network layer.

We are now starting the isolation of the network and searching further files / folders and connections to the outside. Currently, we do not assume a data protection-relevant case, but we will still make a report today. The quick capping of the external connection could not harm relevant information.

All connected devices will be searched again from 4 p.m. onwards, provided that no further cases are found - we will confirm this case. However, we will not do any more work today due to the high security risk.

More information in a few hours.

In order to settle any damage, we have stopped the external connection of our office. We have found the cause, it seems to be an email - as requested after a job. After opening the attached documents - despite virus checking - a Trojan seemed to have spread to our network level. After further investigation, we were able to discover the Trojan and are now eliminating it.

All services run optionally.

Current bills for the month: November 2022 must be regenerated by us. In addition, current account balances are incorrect, this will be synchronised with the accounting software after running our cron job.

The Reseller API will also be available again shortly. Some small details will be revised at the same time so that we can publish a new version directly.

There are currently two other errors on the homepage that are connected to our database. These will be fixed within the next few days, as they do not have a high priority.

The partner interface will receive a minimalist update from the backend at the same time, regarding invoices and TeamSpeak billing. No change to be seen at this point.

There was an outage that hit our entire web infrastructure as well as our database host.

We have already moved a large part of our web infrastructure to AWS in Frankfurt. We have now set up our database host redundantly.

The partner interface is available again. However, we are missing some database entries, which we are currently reconstructing with the help of our backups and accounting software. Our homepage is also accessible again; the error was in the database connection. In the meantime, we have been able to stabilise this again. Unfortunately, some database entries are missing here as well, but most of them are already available.

We will take further measures to prevent or minimise such an incident in the future. Further observations will be made and carried out.