Mainnet Upgrade to v0.6.0
Completed
Upgrade of the Hedera mainnet to v0.6.0 was completed. (release notes: https://hedera.io/release-notes) New network providers replaced nodes 0, 3, 4, and 10. During the upgrade, issues with node 8 appeared, and this node was put into maintenance.
Posted Aug 06, 2020 - 19:26 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Aug 06, 2020 - 17:00 UTC
Scheduled
Hedera will be upgrading the mainnet to v0.6.0 (release notes: https://hedera.io/release-notes) on Thursday, Aug 6th, at 17:00 UTC. Nodes 0, 3, 4, and 10 will be replaced by new network providers. This will remove the remaining place holder nodes. This upgrade will take approx. 150 minutes to complete, during which time all network services will be offline.
Posted Aug 03, 2020 - 12:51 UTC
This scheduled maintenance affected: Mirror Node Mainnet APIs (v0.102.0) (Mirror Node REST API Mainnet), Hedera Mainnet (v0.47.4) | Network Uptime, and Hedera Mainnet (v0.47.4) | Individual Nodes (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 for Nomura | Vilnius, Lithuania, Node 5 (account 0.0.8) | Hosted by Google | Helsinki, Finland, Node 6 (account 0.0.9) | Hosted for Zain Group | Strasbourg, France, Node 7 (account 0.0.10) | Hosted for 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 30 (account 0.0.33) | Hosted for Mondelēz International | Singapore, Republic of Singapore).