Resolved after 15 minutes, on January 23, 2026.
We have now regained direct access to the node via IPMI. As the server became unavailable during the outage, a hard reboot was required to restore access. Since the server had been running continuously for a prolonged period, the motherboard has initiated RAM training. This is expected behavior on DDR5-based systems and may take up to 15-20 minutes. We will provide an update as soon as the node is back up online.
Update timeline
- investigating Jan 23, 2026, 03:50 AM UTC
Unfortunately, due to an unexpected issue with the node's NIC, network connectivity became unavailable. As the IPMI console was also inaccessible, we had no alternative but to request Remote Hands support from the data center. The data center engineers are currently inspecting the server and will resolve the issue as soon as possible.
- investigating Jan 23, 2026, 04:06 AM UTC
We have now regained direct access to the node via IPMI. As the server became unavailable during the outage, a hard reboot was required to restore access. Since the server had been running continuously for a prolonged period, the motherboard has initiated RAM training. This is expected behavior on DDR5-based systems and may take up to 15-20 minutes. We will provide an update as soon as the node is back up online.
- resolved Jan 23, 2026, 04:16 AM UTC
The node is now back online, and the issue has been fully resolved.
Your product runs on more than SENKO
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services