Input Output (IO) is investigating the cause of an apparent bug that disconnected the Cardano node, causing a brief outage.
IO reported that 50% of network nodes were disconnected and rebooted for unknown reasons on January 22nd. However, this issue did not affect edge nodes that act as gateways for end users to reach “worker nodes”.
“This affected relay nodes and block-producing nodes. Edge nodes appear to be unaffected.”
Cardano node interruption was a ‘temporary anomaly’
IO downplayed the severity of the disruption, saying the incident was a “temporary anomaly” affecting some nodes. Additionally, the developer said such contingencies were “taken into account in the design.” In other words, no surprises or serious disruptions occurred.
“This appears to have been caused by a transient anomaly causing one of two reactions on the node. Some disconnected from peers, others threw an exception and restarted. “
Block production was temporarily affected, temporarily causing the network to go out of sync, but such instances could occur during normal operation, such as during transitions between epochs, IO said. I’m here.
Rick McCrackenThe Digital Fortress stake pool’s lead SPO said the anomaly did not knock out the network. Even so, there was a brief window of “degradation” in which the network resumed normal operations after the affected nodes rebooted.
“There was a short period of deterioration. Most of the affected nodes have successfully recovered. No network restart was required.“
Input Output for further investigation
Comments posted by SPO Github post We’ve identified an issue with relay and producer nodes, but not all contributors experienced that issue. The problem was he resolved within 5 minutes with no action required on SPO’s part.
Despite the low impact of the anomaly, IO said it would investigate the incident further by looking for the root cause. In the meantime, keep track of your network’s performance.
“We are currently investigating the root cause of this anomalous behavior and are implementing additional logging measures alongside our regular monitoring procedures.”




























