Past Incidents

The problem was solved immediately by Remote Hands. Incident was labelled as resolved at around 21:06, according to our partner.

We have not noticed any further problems since then.

Obviously all pages have been put back into operation correctly. We could not detect any errors or inaccessibility.

For us, the incident is now over.

So far, we have been able to restore all the main pages and essential administrative bodies.

Within 48 hours, we will check all other sub-projects, sub-pages etc. and test their functionality.

The majority of our pages are available again.

We will gradually continue to make all pages available. It will certainly take up to 48 hours until everything is 100% operational again.

We are currently still waiting for the manual release of our Plesk licence by a cooperation partner.

As soon as this has been provided, we can restore the backup as planned.

We currently expect it to take a few hours, but hope that we can restore our websites by 02:00.

The recovery process has just been started.

We will check the progress at around nine o'clock and make further adjustments if necessary.

All backup processes are currently running and will hopefully be completed by Plesk.

Once the process has been completed, we will carry out the reinstallation.

So far we have not been able to detect any direct errors. After various Plesk repairs, restart attempts and creating new configuration files, it runs stably for a few minutes.

The error occurs again after approx. 3-10 minutes.

We have already contacted the direct Plesk support to get a solution as soon as possible.

If the support does not work or does not help, we will move the main pages to other servers in the coming night to ensure the availability of our pages. Until then, restrictions and partial outages must be expected.

We have not detected any errors so far. For this reason, we are closing the incident.

RPKI management is possible again by restarting the cluster.

We now synchronise the CAs and repositories again. The restoration of the announcement can take 5-45 minutes until all IP networks are functional again in the DFZ.

The problem has now been solved.

Message from the provider: The problem at the NTT site has been successfully resolved. The cause was a loop in the network, which we identified and rectified on site.

We could not detect any other influences. The incident can therefore be closed.

We were able to establish that functionality was possible again this morning at around 7am. Further observations are still ongoing.

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.