Resolved -
Our investigation has been completed, and we have confirmed that the root cause was a hardware malfunction.
Since the affected equipment was removed, network traffic has been fully handled by our redundant architecture, and we have observed stable operation across the platform. Based on our investigation and continued monitoring, we consider this incident to be resolved and closed.
Jul 14, 12:10 CEST
Update -
At this stage, our investigations have not identified any configuration issue that would conclusively explain the incident. Based on the evidence gathered so far, we believe the most likely cause was a hardware malfunction. As a precautionary measure, the affected equipment has been permanently decommissioned and removed from our infrastructure.
Network traffic is now fully handled by our redundant architecture. We are continuing enhanced monitoring of our network links to confirm service stability and ensure the resilience of the infrastructure.
Our teams remain fully engaged and will continue to provide updates as soon as additional relevant information becomes available.
Jul 10, 15:35 CEST
Update -
Our engineering team is actively investigating the root cause of the component failure and working on further mitigation steps to improve system resilience.
We will continue to monitor the situation closely to ensure ongoing stability.
Jul 9, 13:34 CEST
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 8, 16:23 CEST
Update -
We are continuing to investigate this issue.
Jul 8, 15:59 CEST
Investigating -
You might face some errors/timeouts when trying to send an ATMP message.
Jul 8, 15:04 CEST