Systeemstatus

We have experienced a temporary network disruption affecting connectivity to some of our services. The issue has been identified, and connectivity is expected to return to normal within the next few minutes, if not seconds. As a precaution, one subnet will remain offline until our upstream provider resolves the underlying issues that contributed to the disruption. If your server remains unresponsive after connectivity has been restored, we recommend performing a reboot. We apologize for the inconvenience and appreciate your understanding.

The issue has now been resolved. Our upstream provider identified problems affecting part of their network equipment and has completed the necessary corrective work. Connectivity is currently stable, and we are continuing to monitor the infrastructure closely to ensure the issue does not recur. We apologize for the disruption and thank you for your patience.

The root cause of the connectivity degradation has now been identified and is related to our upstream provider's infrastructure. Their network team is actively working on the issue and implementing the necessary fixes to restore full stability. We are continuing to monitor the situation closely from our side and remain in direct contact with the upstream provider while the work is ongoing.

We have observed another brief recurrence of the network connectivity degradation previously reported. Connectivity has returned to normal, and our team is continuing to investigate the issue together with our upstream provider. We are actively monitoring the affected infrastructure and reviewing the switching and port-channel behavior to identify the exact cause and prevent further occurrences. We apologize for the inconvenience and will provide further updates as soon as we have additional information.

We observed a brief network connectivity degradation affecting part of our infrastructure at approximately 22:50 CEST. The disruption lasted a few minutes and connectivity has since returned to normal. Our upstream provider identified abnormal port-channel flapping on part of the switching infrastructure, which caused traffic to be automatically rebalanced across the remaining links. We are continuing to monitor the network together with our upstream provider to ensure stability and determine the exact root cause. We apologize for the inconvenience.

IPv4 Routing Issue – Affected Subnets Identified We have identified the cause of the routing issues affecting the following IPv4 ranges: - 92.112.124.0/22 - 143.20.79.0/24 The affected IP ranges are provided through an external IP resource provider and are no longer being made available to our network. This resulted in partial routing and reachability issues from certain countries, ISPs, and networks. To permanently resolve the issue, we are now automatically replacing affected IPv4 addresses with addresses from healthy subnets. Customers do not need to request the change manually. VPS data, disks, operating systems, and configurations will remain unchanged — only the public IPv4 address will change. The new IPv4 address will appear in the control panel once the replacement is completed. Customers affected by this incident will also receive 2 additional days of service as compensation. We apologize for the disruption and are working to complete all remaining IP replacements as quickly as possible.

We are currently investigating a routing issue affecting a specific subnet. Some customers may experience connectivity or routing problems. Our network team is actively investigating the issue. If you are currently affected, switching to a different subnet resolves the problem immediately. Please contact our support team if you need assistance with the change. We will provide further updates as soon as more information becomes available.

We are aware of the issues affecting the D-node. The cause has been identified, and the issue should now be resolved. We will continue to monitor the service to ensure everything is operating normally. questo riguardo questa mattina