At 1:10 PM, Enreach officially confirmed that the outage has been resolved.

They are still monitoring to prevent this from happening again.

Enreach reports that the platform is stable and normal service has been restored. They are closely monitoring the platform to ensure there are no further issues.

We are fully operational and have confirmation from our network supplier that the previous fiber optic outage has been resolved.

Systems are stable. We continue to monitor.

The systems are recovering. We continue to closely monitor our data center.

Unfortunately, the malfunction appears to have manifested itself again.
Our experts have started research again.
Sorry for the inconvenience.

We see that the servers are or will be online again. We are investigating the cause of this interruption.

We receive a message from the provider that the disruptions have been resolved.

AMS-IX has announced that the problems have been resolved.

Update Enreach:

"AMS-IX has announced that the problems have been resolved. We see a significant improvement. Some of the data traffic has been returned, and we are monitoring this extensively before we proceed to fully restore the data traffic."

Enreach update:

"Because the outage occurs at the AMS-IX, one of the most important internet exchanges in the Netherlands, most ISPs in the Netherlands are affected. Our services can still be used, but during use you may experience brief instability or outages We continuously review the options to apply adjustments within our network to minimize the impact for you."

Update Enreach, problem has been identified:

"There are currently connectivity issues at the AMS-IX data center. Our products and services may be impacted. The potential impact is a reduced amount of available bandwidth, resulting in temporarily unavailable or unworkable products and services. Our engineers are working on solutions and are working closely with AMS-IX staff to resolve this issue."

We see that various problems have been resolved after issues in an external component. Rebooting this helped. We investigate the logging/dump to get to the root of the problem.

Problems have already been resolved for some customers, others are experiencing other issues such as problems starting the client applications. Research is still ongoing.