Are a node’s connection records and its status marked as inactive always consistent? An AvalancheGo uptime tracker request indicates that these two types of tracking were improperly correlated. The proposed solution reduces the scope for errors by reorganizing how status is stored and adding regression tests. When viewing online information for node $AVAX , first check the metric definitions and the source of the actual status. The original text provides no statistics on production disconnection rates or reward losses, so a fix to one status-tracking issue cannot be extrapolated into a network-wide availability conclusion.