Some systems are under maintenance.

22 Oct 2026, 12:45 UTC The update of the systems is proceeding as planned. Concerns about the effectiveness of the security release have largely been resolved. A PHP core developer has confirmed an additional vulnerability, but it is unrelated to the previously announced issues and is not rated as critical. Most internal systems and other public services are back in operation. As no vendor patches are available yet for the regular status page, status updates will continue to be published on this page for the time being. The customer management portal and VPS management will remain offline for now while the situation continues to be monitored. A return to normal operation is planned for Sunday, 25 October 2026.

21 Oct 2026, 15:45 UTC There are indications that the published security release may not fully resolve the vulnerabilities. Until the situation has been clarified, all affected systems, including internal services and the customer management portal, will remain out of operation as a precaution. Further updates will be posted here.

21 Oct 2026, 15:00 UTC The update of the affected systems is proceeding as planned. Parts of the internal infrastructure are already back in operation. The security updates for the customer management portal have been applied. It will be released once the outstanding fixes for the underlying backend components are in place.

20 Oct 2026 The PHP-based public services were shut down as a precaution. VPS are not affected.

The PHP security team has published an unscheduled security release for two critical vulnerabilities, each rated CVSS 9.2. Read the announcement

To protect customer data, the PHP-based public services have been proactively shut down until the patches have been applied and verified. The VPS themselves are not affected and remain online. Only the VPS management interface is temporarily unavailable. Services will then be restored step by step. No definite time can be given at this point.

Appropriate action on customer-managed VPS systems is recommended as well.

In case of emergency: support@eth-services.de

The outage was caused due to human error pulling incorrect fibers. After intervention from NOC and local technician, the port is already in service again.

Original RFO:

circuit is down not due to a miscommunication on the change (GIN-CHG00XXXX). Unfortunately due to another migration tonight the local hands incorrectly pulled the incorrect fibers. I talked to the tech that was working with the migration and this has been corrected at this time.

We are currently observing an outage affecting carrier NTT (AS2914). We were previously informed of a scheduled maintenance planned for tomorrow. However, after speaking with the NTT NOC, we have learned that there is also an ongoing maintenance today. This maintenance was not expected to impact our service and therefore no notification was sent.

The NTT NOC is currently investigating the issue.

Sparkle has implemented various changes that resolve the situation. BGP has been enabled again, and the situation is stable. We will monitor the situation carefully and intervene when necessary.

The latest update remains in place. Sparkle NOC applied various changes, which remain unsuccessful. The carrier remains drained until restoration is in place. No customer impact is expected at this point.

After further communication, Sparkle installed another faulty configuration change, resulting in blackholing of egress traffic. Currently, BGP is disabled and traffic is flowing via alternative paths to mitigate the impact.

Customers traversing the Sparkle backbone may have experienced packet loss between 10:30 UTC and 12:30 UTC.

We are in constant contact with the Sparkle NOC to address the issue, and we apologize for the inconvenience caused.

Sparkle has reverted the faulty changes and sessions have been enabled again.

We are currently observing a partial null route of traffic via Carrier Sparkle due to a false configuration change on Sparkle’s side. BGP has been drained, and the impact is mitigated for the moment. We will get in touch with the Sparkle NOC for a permanent solution.