Network outage EQ FR5 Xeon Cluster on 18 Apr 2026 08:58:48 (UTC+00:00)
Completed on 18 Apr 2026 10:03:35 (UTC+00:00)
There appears to be a network outage at the EQ FR5 Xeon Cluster site; only the Xeon KVM servers at this location are affected. The upstream provider has already been notified, and we are awaiting a response.
11:14:
Xeon1 to xeon20 are affected. Update from AS203446: It seems like the MX480 router in FR5 is down, Equinix will check the router.
11:39:
The downtime appears to have been resolved. Four systems were located in a rack that was experiencing power issues (Xeon 13, 14, 16). We are now restarting these systems, including all VMs. All other systems are accessible and only experienced connectivity issues.
Customer satisfaction is important to us. Therefore, we are offering compensation in the form of three days of runtime on the respective nodes that experienced issues. This runtime will be added to the services today.
There appears to be a network outage at the EQ FR5 Xeon Cluster site; only the Xeon KVM servers at this location are affected. The upstream provider has already been notified, and we are awaiting a response.
11:14:
Xeon1 to xeon20 are affected. Update from AS203446: It seems like the MX480 router in FR5 is down, Equinix will check the router.
11:39:
The downtime appears to have been resolved. Four systems were located in a rack that was experiencing power issues (Xeon 13, 14, 16). We are now restarting these systems, including all VMs. All other systems are accessible and only experienced connectivity issues.
Customer satisfaction is important to us. Therefore, we are offering compensation in the form of three days of runtime on the respective nodes that experienced issues. This runtime will be added to the services today.
Completed on 18 Apr 2026 10:02:15 (UTC+00:00)
There appears to be a network outage at the EQ FR5 Xeon Cluster site; only the Xeon KVM servers at this location are affected. The upstream provider has already been notified, and we are awaiting a response.
11:14:
Xeon1 to xeon20 are affected. Update from AS203446: It seems like the MX480 router in FR5 is down, Equinix will check the router.
Customer satisfaction is important to us. Therefore, we are offering compensation in the form of three days of runtime on the respective nodes that experienced issues. This runtime will be added to the services today.
There appears to be a network outage at the EQ FR5 Xeon Cluster site; only the Xeon KVM servers at this location are affected. The upstream provider has already been notified, and we are awaiting a response.
11:14:
Xeon1 to xeon20 are affected. Update from AS203446: It seems like the MX480 router in FR5 is down, Equinix will check the router.
Customer satisfaction is important to us. Therefore, we are offering compensation in the form of three days of runtime on the respective nodes that experienced issues. This runtime will be added to the services today.
Update on 18 Apr 2026 09:15:59 (UTC+00:00)
There appears to be a network outage at the EQ FR5 Xeon Cluster site; only the Xeon KVM servers at this location are affected. The upstream provider has already been notified, and we are awaiting a response.
11:14:
Xeon1 to xeon20 are affected. Update from AS203446: It seems like the MX480 router in FR5 is down, Equinix will check the router.
There appears to be a network outage at the EQ FR5 Xeon Cluster site; only the Xeon KVM servers at this location are affected. The upstream provider has already been notified, and we are awaiting a response.
11:14:
Xeon1 to xeon20 are affected. Update from AS203446: It seems like the MX480 router in FR5 is down, Equinix will check the router.
Investigating on 18 Apr 2026 08:58:48 (UTC+00:00)
There appears to be a network outage at the EQ FR5 Xeon Cluster site; only the Xeon KVM servers at this location are affected. The upstream provider has already been notified, and we are awaiting a response.
There appears to be a network outage at the EQ FR5 Xeon Cluster site; only the Xeon KVM servers at this location are affected. The upstream provider has already been notified, and we are awaiting a response.