Is Hedera Down Right Now? Check if there is a current outage ongoing.

Completed: The Hedera testnet upgrade to v0.62.6 has been completed successfully! https://docs.hedera.com/hedera/networks/release-notes/services#release-v0.62

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

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

Hedera will be upgrading the Hedera testnet to v0.62.6 on Tuesday, June 3 2025 at 17:00 UTC. The upgrade will take approximately 40 minutes to complete, users should expect some disruption to network services during this time.

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

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

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

We will be undergoing scheduled maintenance during this time.

Hedera will be upgrading Hedera mainnet to v0.61 on Friday, May 30 2025 at 17:00 UTC. The upgrade will take approximately 40 minutes to complete, users should expect some disruption to network services during this time.

The scheduled maintenance has been completed.

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

The EDF node (node 18) will be undergoing scheduled maintenance. This is a continuation of the earlier maintenance window for the same node.

Mainnet 0.61 upgrade scheduled for Wednesday, May 28 2025 at 17:00 UTC has been canceled.

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

Testnet v0.62 upgrade scheduled for Thursday, May 29 2029 at 17:00 UTC has been canceled.

Hedera will be upgrading the Hedera testnet to v0.62 on Thursday, May 29 2029 at 17:00 UTC. The upgrade will take approximately 40 minutes to complete, users should expect some disruption to network services during this time.

This incident has been resolved.

The mainnet uploaders are currently processing a backlog of data that accumulated during the upgrade. Transactions are still being processed as expected.

Maintenance on the mainnet uploaders is in progress and will be completed momentarily.

This issue has been resolved with the release of Hedera Services v0.58 on February 19, 2025. Values shown for staking rewards accrued for an account will be accurate after the next time it collects staking rewards.

We have identified an issue with how the staking rewards are being exported to mirror nodes, which may cause staking rewards to appear as zero. However, rewards are still being accrued and distributed as expected. This issue will be fixed on mainnet with the release of Hedera Services v0.58.

We have identified an issue with exporting the staking reward rate to mirror nodes and we're working on a fix. Staking rewards are still being distributed.

We are currently investigating an issue with staking reward distribution.

This incident has been resolved

A fix has been implemented and we are monitoring the results

We are investigating an issue with address books in the previewnet

We have resolved the incident and the mirrornode is behaving as expected.

We have identified the problem, applied a work-around, and are working on a resolution.

Hedera is observing increased errors downloading fee schedules on the mirrornode. We are investigating the cause and working to mitigate the impact on applications.

The issue is now resolved on Mainnet. The `MAX_ENTITIES_IN_PRICE_REGIME_HAVE_BEEN_CREATED` error was caused by the increased network usage and adoption we’re seeing from multiple applications. Although the network capacity was increased recently with the “Data on Disk” improvements, the token associations limit was not adjusted to match this increased capacity. The limit has been updated to accurately reflect the expanded network capacity.

A fix has been rolled out and we are monitoring its impact

The issue has been identified and a fix is being implemented.

token associate operations on mainnet are showing low rates of success.

The incident has been resolved. A postmortem report will be added to this incident as it becomes available

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

The Hedera testnet had an incident yesterday which resulted in approximately five hours of downtime \(for testnet only\). The issue arose in the centralized management of testnet. It was fixed, and testnet is now running correctly. No data was lost or corrupted. This was not caused by any code bugs, and does not affect mainnet. Engineering and DevOps will be conducting a root cause analysis around this issue to better understand how to prevent these issues from occurring in the future.

This incident has been resolved

We have identified that the Hedera testnet is down for all users and are working on a resolution

We are currently investigating a possible issue with the Hedera testnet

This incident has been resolved.

We are continuing to monitor for further issues

A fix has been implemented and we are monitoring the results

We have identified the issue and are working on a fix

We are currently investigating an issue minting NFTs in testnet

The Hedera Testnet has been upgraded to v0.36.1 successfully

A fix has been implemented and we are monitoring the results.

We have identified a fix and are proceeding to update Hedera testnet to v0.36.1

We have identified the issue and plan to do an emergency release in the next few hours

We are investigating an issue in Hedera Testnet with smart contracts created prior to the network upgrade

Backfill of the GCP bucket has been completed. Both the GCP and AWS buckets for testnet mirror nodes are at parity.

A fix has been implemented and we are monitoring the results.

This update is meant for testnet mirrornode operators using the GCP bucket. In an effort to address technical debt from the last testnet reset, we cycled a credential on GCP. Unfortunately, we inadvertently deactivated a key, which led to the temporary disabling of uploaders. We have since re-enabled the uploaders. However, backfilling the record stream is taking longer than expected, and estimate it will be fully resolved within the next 4-5 days. During this period testnet mirrornode operators relying solely on the GCP bucket may experience halted operations. As a temporary workaround, we recommend using the AWS bucket in the meantime. Please note that this issue does not impact the Hedera-managed testnet mirrornode; it only affects operators running their own mirrornodes. We apologize for any inconvenience this may cause and appreciate your patience as we work to resolve this issue. We will provide updates on the status page as the situation progresses.

This incident has now been resolved

We are currently investigating an issue with the testnet mirrornode

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are currently investigating an issue with the Hedera Testnet mirrornode

The Hedera mainnet has been upgraded to patch the vulnerability and mainnet is now running and available. Details on the attack will soon be made available.

Today, attackers exploited the Smart Contract Service code of the Hedera mainnet to transfer Hedera Token Service tokens held by victims’ accounts to their own account. The attacker targeted accounts used as liquidity pools at multiple DEXes that use Uniswap v2-derived contract code ported over to use the Hedera Token Service, including Pangolin, SaucerSwap, and HeliSwap. When the attackers moved tokens obtained through these attacks over the Hashport bridge, the bridge operators detected the activity and took swift action to disable it. The Hedera community, including Swirlds Labs, The HBAR Foundation, Limechain, Pangolin, SaucerSwap, and HeliSwap teams, worked together to investigate the attack. To prevent the attacker from being able to steal more tokens, Hedera turned off mainnet proxies, which removed user access to the mainnet. The team has identified the root cause of the issue and are working on a solution. Once the solution is ready, Hedera Council members will sign transactions to approve the deployment of the code on mainnet to remove this vulnerability, at which point the mainnet proxies will be turned back on, allowing normal activity to resume.

We are continuing to investigate this issue.

Out of an abundance of caution & safety for retail users, Hedera is turning off network proxies on mainnet, effectively making it inaccessible. Hedera core will continue to work through the smart contract irregularity. Subscribe to status.hedera.com for the latest info.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results

Hedera has observed an issue where, in rare cases, submitting a ContractCall transaction that swaps >50% of an account’s HBAR balance may fail. If triggered, an “insufficient balance” error will display, even when there is a sufficient residual balance in the account. User assets are unaffected, and this issue does not impact other Hedera network services. The Hedera mainnet continues to operate as expected. Hedera core engineering has identified the root cause of this issue and is working towards releasing a fix. Please visit https://status.hedera.com or follow Hedera Status on Twitter (https://twitter.com/hashgraph) for ongoing updates.

This incident has been resolved.

Hedera is observing an incident with mirrornode processing transactions. We are investigating the cause and working to mitigate the impact on applications.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Hedera is observing an incident with mirrornode processing transactions. We are investigating the cause and working to mitigate the impact on applications.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Hedera testnet is observing a network outage across all nodes. We are investigating the cause and working to mitigate the impact on applications.

Hedera core engineering has confirmed that the mirrornode is now functional; mainnet transactions which occurred during the period of mirrornode downtime are now queryable. Mirrornode operators are advised to upgrade to version v0.66.4.

Hedera core engineering has deployed the v0.66.4 software update to mirrornode and is continuing to monitor.

We are continuing to work on a fix for this issue.

The transaction processing issue in mirrornode has been identified and we are working on a fix to deploy. Event streams, account balances, and recordstreams are still being uploaded and transactions are still being processed by consensus nodes, but they are not able to be processed by mirrornodes.

We are continuing to investigate this issue.

Hedera is observing an incident with mirrornode processing transactions. We are investigating the cause and working to mitigate the impact on applications.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been applied and we are monitoring the results.

We are continuing to investigate this issue.

The stable testnet is currently experiencing increased latency. We are investigating the issue.

The Hedera testnet has been upgraded to v0.22.2 and normal operation has been restored. We were able to fix an issue with the gossip protocol which was causing increased latency. No data or user accounts have been affected

A fix has been implemented and we are monitoring the results.

The stable testnet is currently experiencing increased latency. We are investigating the issue.

The patch to testnet has been applied and the network is back to healthy. Thank you for your patience.

We have developed a patch for the auto-account creation issue and will be deploying shortly. We will briefly freeze the testnet to apply the update.

We have developed a patch for the auto-account creation issue and will be deploying shortly. We will briefly freeze the testnet to apply the update.

We have isolated an issue with auto-account creation on testnet with v0.21. We are temporarily disabling account creation on the testnet while we continue to investigate this issue and work to resolution

We are continuing to investigate this issue.

We are currently investigating issues with network functionality on the Hedera Testnet

Normal operation has been restored to the Hedera Testnet. Hedera acknowledges the extended outage may have impacted users and makes every effort to minimize downtime and inconveniences. Hedera has decided to start the testnet with a fresh state, including all testnet account IDs and transaction history. Please log in to your Hedera Portal Profile (https://portal.hedera.com) and retrieve your new Testnet account ID(s) — your public and private keys will remain the same. If you were accessing S3 or GCS buckets for testnet data, the bucket names have been updated to hedera-stable-testnet-streams-2020-08-27. Any documentation pointing to the previous buckets will need to be updated to reflect the new buckets.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Hedera is observing an incident across Testnet. We are investing the cause and working to mitigate the impact on applications.

We acknowledge the impact this might have caused. Hedera has resolved the issue, and services have resumed. During the outage, Hedera discovered a race-condition was the cause of the error. A new patch was deployed via a release candidate and has since fixed the error. For further information, please see the release notes. https://github.com/hashgraph/hedera-services/releases/tag/v0.7.0-rc2

A fix has been implemented and we are monitoring the results.

The issue has been identified. The Hedera team is working on a state restoration and plans to bring services back online by 8/26/2020. In the meantime, the Preview - Testnet is available for usage.

Hedera is observing a network-wide outage on testnet. We are investigating the cause and working to mitigate the impact on applications. The Hedera previewnet is still online.

The incident is mitigated. There was no network-wide outage during this incident. Testnet Node 0 (account 0.0.3) was taken offline and will resume operation on the next maintenance windows scheduled for Monday, August 24th, 2020 at 2100 UTC.

Testnet Node 0 (account 0.0.3) has suffered an error. This node is offline and will be brought back online during the next maintenance window.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

Hedera is observing an incident across Testnet. We are investing the cause and working to mitigate the impact on applications.

This incident has been resolved. Your Hedera Portal-generated testnet account IDs have been recreated; visit the Hedera Portal to retrieve your new keys and account IDs. Accounts generated by old keys have been purged. Although the testnet is back online, community explorers may not reflect testnet transactions yet.

The Hedera team is aware of a network-wide outage of the testnet and testnet mirror node APIs. They will remain offline until the identified issue has been resolved.

This incident has been resolved.

Secondary issue identified, working on a fix now.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently experiencing high CPU on the Mirror node HCS gRPC Testnet.

This incident has been resolved.

We are currently investigating an internal issue related to the public testnet. Network will be offline while we troubleshoot.

Node 10 (account 0.0.12) service has been restored to mainnet

Node 10 (account 0.0.12) (IP 35.204.86.32:50211) suffered a software misconfiguration during a patch window on November 21st, 2019. This node has been moved back into the staging network and will be brought back online in the next maintenance window.

Node 6 (account 0.0.8) service has been restored to mainnet

Node 6 (account 0.0.8) (IP 35.236.5.219:50211) has suffered a hardware related issue on January 4th, 2020. We plan to bring this node back online in the next maintenance window.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating an issue with the Testnet Mirror Node Rest API

This incident has been resolved.

The Hedera mainnet is back online and the configuration issues have been solved. No mainnet data has been compromised or lost. The testnet is still offline and undergoing maintenance.

The issue has been identified as a configuration error and a fix is being implemented.

Hedera is observing a network-wide outage across the mainnet and testnet. We are investigating the cause and working to mitigate the impact on applications.

The Hedera mainnet mirror node is back online.

Hedera is observing a network-wide outage across the mirror node network. We are investigating the cause and working to mitigate the impact on applications.

Hedera has resolved the issue and normal services have resumed.

A fix has been implemented and Hedera is monitoring the results.

The issue has been identified and a fix is being implemented.

Hedera is observing a network-wide outage across the testnet. We are investigating the cause and working to mitigate the impact on applications.

Hedera has resolved the issue and normal services have resumed.

A fix has been implemented and Hedera is monitoring the results.

Hedera is observing an outage across all testnet nodes. We are investigating the cause and working to mitigate the impact on applications.