Since the migration, we have not been able to detect any further errors within 12 hours.

The only thing was a hardware defect on the core02, which was not noticed. This did not lead to an interruption in the network infrastructure.

We will continue to monitor our network closely.

We have now successfully migrated eight nodes, but the downtime was quite long due to unexpected errors on the part of Plesk.

It is conceivable that all nodes will be available again by 13:30.

We have now made further observations and found some small things that we still need to adjust. We are not talking about urgency here.

In the meantime, we have tried to make further adjustments at intervals of around 24 hours to enable future improvements in the event of core router failures at the switch between all core routers.

The incident is now completely closed for the time being. We will update further adjustments and configurations in further 24-hour intervals (usually 02:00 to 03:00).

The last 48 hours look much better compared to the days before. We only noticed one timeout on 30.06.24 at 12:12, which didn't last a minute.

It seems that all our configurations are now correct and running 100%, thanks also to our upstream who provided us with a session on newer hardware. However, we will continue to monitor for another 72 hours so that we can react to any problems within a few minutes and be on the safe side.

We have just completed our maintenance work for the implementation of VRRP.

In addition, a BGP session was moved to our upstream on a new router. We continue to keep our network under 24/7 observation in order to be able to react directly in the event of further outages, timeouts or other problems. We are working intensively on this issue in collaboration with our upstream in order to resolve past problems.

The problem is due to a faulty fuse on the switch. All traffic was redirected via DUS7 (myLoc) in order to ensure the continued availability of the network.

In this case, as well as the timeouts, we will continue to wait 24 hours until our maintenance appointment tomorrow (Saturday) and monitor it extremely closely. If our network does not stabilize within the next seven days from tomorrow and cannot be operated without timeouts, we will consider other solutions for the operation of our infrastructure and, if necessary, put a new location into operation or relocate.

Maintenance details at: https://status.schleyer-edv.de/#scheduled-26

We have discovered that we obviously have a misconfiguration on core01.de-dus01.

We are currently setting up a new Bird2 VM to redirect the traffic - so that we can set up both core routers again and then route the traffic via the core routers again.

In the meantime, there may be interruptions to the network infrastructure.

The network is accessible again without any problems, and we will of course continue to monitor it closely for another 24 hours.

Our vhost01.dus obviously has problems, which is why some services are still unavailable. We are in contact with the data center.

We were able to identify the problem more precisely. We are already working on a fix.

We are also waiting for a response from our upstream-provider.