Past Incidents

The replacement was completed around 6 pm and switched from the redundancy on the main core.

We have not noticed any further problems so far.

We have received information that the cause can be traced back to a defective module. An employee is already on his way to the data centre to replace it.

The replacement should not pose a problem during operation and we therefore do not expect it to be affected. The process will probably be carried out within the next 20 minutes to an hour and a half.

We will continue to keep you up to date.

We have just reinstalled the Plesk instance.

Why so late? We had made countless adjustments over the past weeks and days. Apparently, however, the server was misused for various illegal purposes, e.g. to run scans and logging services. And to distribute minimal TCP packets to various destinations. The search has taken some time, up to now we have recorded around 37 abuse reports. In addition, some errors were detected in all Plesk configurations in the early evening, which were no longer able to operate our web services.

Now that the server has been reinstalled and additional security services have been put into operation, we are continuing to monitor the situation closely and are constantly endeavouring to make further changes to our infrastructure for the future. In doing so, it plays an enormous role to phase out the solution: Plesk for our internal purposes.

The incident is over for the first time. Should we discover further problems or errors, we will initiate a new one.

We have just reinstalled the Plesk instance.

Why so late? We had made countless adjustments over the past weeks and days. Apparently, however, the server was misused for various illegal purposes, e.g. to run scans and logging services. And to distribute minimal TCP packets to various destinations. The search has taken some time, up to now we have recorded around 37 abuse reports. In addition, some errors were detected in all Plesk configurations in the early evening, which were no longer able to operate our web services.

Now that the server has been reinstalled and additional security services have been put into operation, we are continuing to monitor the situation closely and are constantly endeavouring to make further changes to our infrastructure for the future. In doing so, it plays an enormous role to phase out the solution: Plesk for our internal purposes.

The incident is over for the first time. Should we discover further problems or errors, we will initiate a new one.

We were able to narrow down the problem using a network loop.

Despite the existing possibility, we still assume a Plesk error and will endeavour to reinstall the entire Plesk instance in the coming night.

The instance is currently running without any major problems.

We were unable to detect any further abnormalities over 24 hours. It was therefore due to the incorrectly set MAC addresses.

We would like to apologise to you for this error, such things should not happen.

The problem has been found. We were able to trace it back to individual MAC addresses that were set the same in the respective interface.

We regenerated and reassigned the MACs. We also restarted the affected VMs. Observations are still being made.

The network was stable again at around 02:27. All pings and tests are in the normal range and services are no longer affected.

We continue to monitor our part. An RCA / post mortem from our partner will follow.

It seems to be more long-lasting. So far there is no ETA, statement or similar.

We are continuing to monitor excessively and are waiting for further results. Pings and various tests are going through, but not fully but only partially with a latency of over 250ms.

The connections have been partially working since 22:07. Fundamentally, there is no recognisable stability.

We are still waiting for a statement and a solution to the problem.