Hedera Status - Mainnet Upgrade to v0.52.3

Mainnet Upgrade to v0.52.3

Scheduled Maintenance Report for Hedera

Completed

Completed: The Hedera mainnet upgrade to v0.52.3 has been completed successfully! https://docs.hedera.com/guides/docs/release-notes/services#v0.52

Posted Aug 28, 2024 - 17:19 UTC

Verifying

The Hedera testnet has been upgraded to v0.52.3. The network is now available for use while additional verification of the upgrade is being performed. You can view the release notes for v0.52.3. here: https://docs.hedera.com/guides/docs/release-notes/services#v0.52

Posted Aug 28, 2024 - 17:09 UTC

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Posted Aug 28, 2024 - 17:00 UTC

Scheduled

Hedera will be upgrading Hedera mainnet to v0.52.3 on Wednesday, August 28 2024 at 17:00 UTC. The upgrade will take approximately 40 minutes to complete, users should expect some disruption to network services during this time.

Posted Aug 27, 2024 - 23:47 UTC

This scheduled maintenance affected: Hedera Mainnet (v0.56.7) | Network Uptime, Hedera Testnet (v0.57.3) | Network Uptime, Hedera Testnet (v0.57.3) | Individual Nodes (Node 0 (account 0.0.3), Node 1 (account 0.0.4), Node 2 (account 0.0.5), Node 3 (account 0.0.6), Node 4 (account 0.0.7), Node 5 (account 0.0.8), Node 6 (account 0.0.9)), and Hedera Mainnet (v0.56.7) | Individual Nodes (Node 0 (account 0.0.3) | Hosted by LG | Seoul, South Korea, Node 1 (account 0.0.4) | Hosted by Swirlds | Iowa, USA, Node 2 (account 0.0.5) | Hosted by FIS | Florida, USA, Node 3 (account 0.0.6) | Hosted for Wipro | Singapore, Republic of Singapore, Node 4 (account 0.0.7) | Hosted by Nomura | Vilnius, Lithuania, Node 5 (account 0.0.8) | Hosted by Google | Helsinki, Finland, Node 6 (account 0.0.9) | Hosted by Zain Group | Kuwait City, Kuwait, Node 7 (account 0.0.10) | Hosted by Magalu | Naaldwijk, Netherlands, Node 8 (account 0.0.11) | Hosted by Boeing | Washington, USA, Node 9 (account 0.0.12) | Hosted by DLA Piper | Helsinki, Finland, Node 10 (account 0.0.13) | Hosted for Tata Communications | Oregon, USA, Node 11 (account 0.0.14) | Hosted by IBM | Texas, USA, Node 12 (account 0.0.15) | Hosted for Deutsche Telekom | Helsinki, Finland, Node 13 (account 0.0.16) | Hosted by UCL | London, UK, Node 14 (account 0.0.17) | Hosted for Avery Dennison | Pennsylvania, USA, Node 15 (account 0.0.18) | Hosted by Dentons | Singapore, Node 16 (account 0.0.19) | Hosted for Standard Bank | Johannesburg, South Africa, Node 17 (account 0.0.20) | Hosted by Australian Payments Plus | Sydney, Australia, Node 18 (account 0.0.21) | Hosted by EDF | Paris, France, Node 19 (account 0.0.22) | Hosted for Shinhan Bank | London, UK, Node 20 (account 0.0.23) | Hosted by Chainlink Labs | Michigan, USA, Node 21 (account 0.0.24) | Hosted by LSE | London, UK, Node 22 (account 0.0.25) | Hosted for IIT Madras | Naaldwijk, Netherlands, Node 24 (account 0.0.27) | Hosted for ServiceNow | Washington, USA, Node 25 (account 0.0.28) | Hosted by Ubisoft | Quebec, Canada, Node 26 (account 0.0.29) | Hosted by abrdn | London, UK, Node 27 (account 0.0.30) | Hosted for Dell | Frankfurt, Germany, Node 28 (account 0.0.31) | Hosted by COFRA Holding | Frankfurt, Germany, Node 29 (account 0.0.32) | Hosted for Hitachi | Delaware, USA, Node 30 (account 0.0.33) | Hosted for Mondelēz International | Singapore, Republic of Singapore, Node 31 (account 0.0.34) | Hosted by BitGo | Stockholm, Sweden).