Hedera upgrade completed—why is the status page still showing a yellow light?
At 17:35 UTC on September 29, the official team confirmed that the mainnet upgrade to v0.77.2 has been completed. During this check, the overall network and the mainnet mirror interfaces look normal, but one independent node is still marked as having a partial issue.
These two status descriptions are not referring to the same layer: an abnormality at a single node can’t be directly equated with a full network shutdown, and completing the upgrade doesn’t mean every component has zero problems. I will first determine whether the affected parts are the network, the node, or the query interface, then cross-check the event update time—rather than only taking the top warning on the page.
For users who关注 $HBAR , when reading the upgrade messages, look one layer deeper into the component status to tell the difference between “overall usable” and “still awaiting fixes locally.” #Hedera network status
At 17:35 UTC on September 29, the official team confirmed that the mainnet upgrade to v0.77.2 has been completed. During this check, the overall network and the mainnet mirror interfaces look normal, but one independent node is still marked as having a partial issue.
These two status descriptions are not referring to the same layer: an abnormality at a single node can’t be directly equated with a full network shutdown, and completing the upgrade doesn’t mean every component has zero problems. I will first determine whether the affected parts are the network, the node, or the query interface, then cross-check the event update time—rather than only taking the top warning on the page.
For users who关注 $HBAR , when reading the upgrade messages, look one layer deeper into the component status to tell the difference between “overall usable” and “still awaiting fixes locally.” #Hedera network status