Status History
October 17, 2023
Resolved
Testnet Reset
We are resetting the network. The new network ID will be "testnet-2".
October 17, 2023 - 15:21
Testnet reset is in progress
October 17, 2023 - 16:10
Testnet is running again. Creating the EVM chain is in progress.
October 17, 2023 - 17:45
Testnet EVM is operational again.
October 4, 2023
Resolved
Mainnet network upgrade in progress
We are currently conducting the Stardust protocol upgrade on Mainnet. For more information about Stardust, please see https://blog.iota.org/iota-stardust-upgrade/. This process may take up to 4 hours. Please monitor this page or @iota on X/Twitter for updates.
October 4, 2023 - 06:00
The Stardust upgrade has begun.
October 4, 2023 - 09:59
We have completed the Stardust protocol upgrade.
September 28, 2023
Resolved
Shimmer Testnet EVM Service Degradation
We are currently investigating an issue in the Testnet EVM service. At the moment, it is non-operational.
September 28, 2023 - 23:34
The DevOps team is investigating the issue.
September 29, 2023 - 08:15
We have deployed a fix and Testnet EVM is operational again.
March 7, 2023
Resolved
Shimmer Testnet API Service Degradation
API services in the testnet are experiencing issues. The network remains operational and the Mainnet and Shimmer network are unaffected.
March 7, 2023 - 09:15
We have identified an issue in the testnet and are working on a fix.
March 7, 2023 - 12:30
Due to a bug in our core libraries a transaction was issued on the Public Testnet which should have been syntactically invalid. While this did not cause a network crash it caused disruptions in our Public Testnet API endpoints, specifically our indexers. In order to alleviate the problem we have deployed Hornet v2.0.0-rc.5 onto the Shimmer network and Public Testnet. Note: the Shimmer network did not encounter such invalid transaction and has been running without any problems.
We recommend node operators to upgrade to Hornet v2.0.0-rc.5 as otherwise the node will desync if not updated. Additionally, we changed the network id of the Public Testnet to testnet-1, therefore node operators on the Public Testnet need to adjust their config, delete the existing database and snapshots and boot up Hornet v2.0.0-rc.5 with this adjusted global snapshot https://files.testnet.shimmer.network/snapshots/latest-full_snapshot.bin. Note that the binary and deb packages have been removed from the Hornet releases as we recommend to use the Docker setup.
We recommend node operators to upgrade to Hornet v2.0.0-rc.5 as otherwise the node will desync if not updated. Additionally, we changed the network id of the Public Testnet to testnet-1, therefore node operators on the Public Testnet need to adjust their config, delete the existing database and snapshots and boot up Hornet v2.0.0-rc.5 with this adjusted global snapshot https://files.testnet.shimmer.network/snapshots/latest-full_snapshot.bin. Note that the binary and deb packages have been removed from the Hornet releases as we recommend to use the Docker setup.
December 29, 2021
Resolved
No more milestones on Mainnet
We are currently investigating an issue where no more milestones are being issued. We'll keep you updated here for further information. Your current staking rewards are not lost. The staking period will be extended so that the full 90 day staking period will occur.
December 29, 2021 - 06:59
The DevOps team is investigating the issue.
December 29, 2021 - 08:00
We have identified the issue and are working on a fix.
December 29, 2021 - 11:01
The Coordinator has been restarted and milestones are now being issued. Community nodes will need to update to Hornet 1.1.3 or make the configuration change shown in the release notes: https://github.com/gohornet/hornet/releases/tag/v1.1.3