All systems are operational

About This Site

Check for ongoing status updates. Here you can find all information about host systems, data centers, API interfaces and more. Always stay up to date.

Maintenance
Modification of pve03-07

We are making changes to the hardware for pve03-07, including various RAM and hard drive upgrades to increase capacity.

We expect a downtime of 30 minutes per host system.

Start of maintenance: 22/02/2025 01:00 a.m.

Expected end: approx. 06:30 a.m.

Updating the webhosting host systems

We have to update the webhosting host systems to the latest versions and install conditional security updates after two years of operation.

In order to prevent a future security risk, we restart the systems. The downtime per host system is 5-10 minutes.

Start of maintenance: 22/02/2025 05:00 a.m.

Expected end: approx. 07:00 a.m.

Modification of pve16-28

We are making hardware changes for pve16-28, including various RAM and hard drive upgrades to increase capacity. To do this, we will connect all host systems with 2x 40G, which requires changing the network cards for each host.

We anticipate 30 minutes of downtime per host system.

Start of the maintenance work: 22/02/2025 07:00 am.

Estimated end: approx. 12:30 pm.

Maintenance of the network infrastructure and expansion of capacities

On Sunday, 23 February 2025, we will be carrying out urgent network maintenance at the Digital Realty (fka. InterXion) site in Frankfurt.

We are replacing the existing core routers with newer models and expanding the network capacity to 2x 100G.

According to the current status, no downtime is to be expected. Nevertheless, there may be higher latencies and partial packet loss.

Start of maintenance: 23.02.2025 02:30 a.m.

Expected end: approx. 05:00 a.m.

Updating our telephone system

We are updating the procedure in our telephone hotline and making important adjustments that we have noticed in the past.

Our emergency hotline is still available for this maintenance and will direct you to a member of staff.

Start of the maintenance: 24.05.2025 15:00

Expected end: approx. 17:00

The hotline will not be available during this period. We can be reached at any time by e-mail, live chat or WhatsApp.

Past Incidents

Wednesday 26th February 2025

No incidents reported

Tuesday 25th February 2025

No incidents reported

Monday 24th February 2025

No incidents reported

Sunday 23rd February 2025

No incidents reported

Saturday 22nd February 2025

No incidents reported

Friday 21st February 2025

No incidents reported

Thursday 20th February 2025

No incidents reported

Wednesday 19th February 2025

No incidents reported

Tuesday 18th February 2025

No incidents reported

Monday 17th February 2025

No incidents reported

Sunday 16th February 2025

No incidents reported

Saturday 15th February 2025

Upstream (BGP Sessions) Error in the RPKI cluster

We have detected an error in the RPKI cluster, due to the error all RPKI certificates of our IP networks are invalid.

We are currently restoring the cluster. This may still take some time.

We will let you know if there are any changes.

  • 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.

  • Friday 14th February 2025

    No incidents reported

    Thursday 13th February 2025

    No incidents reported

    Wednesday 12th February 2025

    No incidents reported

    Tuesday 11th February 2025

    No incidents reported

    Monday 10th February 2025

    No incidents reported

    Sunday 9th February 2025

    No incidents reported

    Saturday 8th February 2025

    No incidents reported

    Friday 7th February 2025

    No incidents reported

    Thursday 6th February 2025

    TeamSpeak-Instances / -Servers Packet loss in NTT

    We have currently detected packet loss at NTT. The technicians are already solving the problem.

  • 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.

  • Wednesday 5th February 2025

    No incidents reported

    Tuesday 4th February 2025

    No incidents reported

    Monday 3rd February 2025

    No incidents reported

    Sunday 2nd February 2025

    No incidents reported

    Saturday 1st February 2025

    No incidents reported

    Friday 31st January 2025

    No incidents reported

    Thursday 30th January 2025

    Mailservices (Exchange) Microsoft 365 authentication problems

    We have experienced various connection problems with Microsoft 365 in terms of authentication.

    As a result, we are unable to access emails, OneDrives and all other common products in the 365 environment. We are currently working with our CSP partner to find a solution, we may have to wait up to 72 hours - at least that's what the CSP partner and Microsoft support told us. Licences are all available, but it is currently impossible to use them.

    We are available at all times via our live chat and our social media platforms. Live chat: www.schleyer-edv.de WhatsApp: +49 209 513 070 50 / +49 1590 656 74 91

    We will update the status in case of news.

  • 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.

  • Wednesday 29th January 2025

    No incidents reported

    Tuesday 28th January 2025

    No incidents reported

    Monday 27th January 2025

    No incidents reported

    Sunday 26th January 2025

    No incidents reported

    Saturday 25th January 2025

    No incidents reported

    Friday 24th January 2025

    No incidents reported

    Thursday 23rd January 2025

    No incidents reported

    Wednesday 22nd January 2025

    No incidents reported

    Tuesday 21st January 2025

    No incidents reported

    Monday 20th January 2025

    No incidents reported

    Sunday 19th January 2025

    No incidents reported

    Saturday 18th January 2025

    No incidents reported

    Friday 17th January 2025

    No incidents reported

    Thursday 16th January 2025

    No incidents reported

    Wednesday 15th January 2025

    No incidents reported

    Tuesday 14th January 2025

    No incidents reported

    Monday 13th January 2025

    No incidents reported

    Sunday 12th January 2025

    No incidents reported

    Saturday 11th January 2025

    No incidents reported

    Friday 10th January 2025

    TeamSpeak-Instances / -Servers Package loss in FRA

    The ISP, we and our customers have noticed a partial packet loss on the TeamSpeak instances in Frankfurt.

    The problem is already being monitored and analysed by the ISP. We currently have no further information.

  • 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.

  • Thursday 9th January 2025

    Schleyer-EDV Persistent problems with our Plesk server

    We have noticed for some time that Plesk has some problems that obviously cannot be solved.

    Accordingly, we will carry out a new installation next weekend. During this time, our websites and administrative interfaces will not be accessible.

    The process does not affect the operation of our services.

  • 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.

  • Wednesday 8th January 2025

    No incidents reported

    Tuesday 7th January 2025

    No incidents reported

    Monday 6th January 2025

    No incidents reported

    Sunday 5th January 2025

    No incidents reported

    Saturday 4th January 2025

    No incidents reported

    Friday 3rd January 2025

    No incidents reported

    Thursday 2nd January 2025

    No incidents reported

    Wednesday 1st January 2025

    No incidents reported

    Tuesday 31st December 2024

    No incidents reported

    Monday 30th December 2024

    No incidents reported

    Sunday 29th December 2024

    No incidents reported

    Saturday 28th December 2024

    myLoc Datacenter (DUS) Failure of our infrastructure in Düsseldorf

    We detected a failure in our infrastructure at 13:57. As we also announced maintenance work from 12:00 noon, we did not assume that this was really serious. After enquiring whether our partners in the data centre would start the necessary work, we were told no a long time later. While we waited for an answer from our partner, we analysed the incident to prevent damage, for example.

    We could not find the direct fault, so we assumed something more serious. After a restart didn't make sense either, we continued to analyse the system. After some time, at around 16:10, we were able to reduce the error to the GRUB boot loader - which had obviously been damaged by the ZFS. In principle, we did not assume that this was the case, as the affected host system was a few days old.

    After a few more hours had passed, the necessary work was carried out by our partner at around 6.30 pm - which also only took about 15 minutes. We continued to analyse in order to fix the problem - which looked difficult after a few more hours in collaboration with various partners. At around 8.30pm we decided to look for a new host system - which we had originally planned to use earlier - and make enquiries. The host system was provisioned at around 10 p.m. - we then took the ZFS apart to find data remnants and compare them with our PBS backups. However, as all the data was still intact on the hard drives, the only option was to transfer the data. Which was done quite quickly.

    However, as the individual virtual server configuration files no longer existed, we had to recreate some of them using our PBS. This went quite quickly and smoothly. At around 02:05, all services were running smoothly again.

    We are taking further internal measures to minimise such cases in the future. Every affected customer will receive compensation from us; in the case of pre-paid products, a four-day credit for the duration of the service; contract and business customers will each receive a €30.00 credit on their next bill.

    As this incident took place between the public holidays and in the middle of the holiday season, we were understaffed and could not act as quickly as we normally do. We would like to apologise wholeheartedly for this.

    We will continue to closely monitor the host systems for a further 48 hours to prevent any incidents.