Past Incidents

Some time has passed and we have not been able to find anything else - the ISP has not yet given us any feedback either.

In the meantime, we have only noticed improvements in latency. We are monitoring for another 24 hours.

We are currently experiencing further cancellations. Contact is being made with our network provider.

The problem was identified and solved immediately. We will continue to monitor the systems for a further 12 hours.

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.