История сбоев Hedera

We’re investigating an issue on the Hedera Testnet affecting smart contracts. The behaviour was first reported starting 31 July 2025. Deployments may succeed, but you may experience: - Contract bytecode not appearing on Hashscan - Read/function calls failing with a BAD_DATA error

The issue affecting Hedera Testnet Smart Contracts has now been resolved. The update resolving the issue has been released to Testnet in v0.64.2. https://status.hedera.com/incidents/fk8hvt7p3vhd If you are experiencing any unexpected behaviour, please raise this on the Hedera Discord: https://hedera.com/discord

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

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

This incident has been resolved.

We are investigating an issue with address books in the previewnet

A fix has been implemented and we are monitoring the results

This incident has been resolved

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

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

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

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

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

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

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.

We are currently investigating this issue.

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

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

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

We are currently investigating a possible issue with the Hedera testnet

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

This incident has been resolved

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.

We are currently investigating an issue minting NFTs in testnet

We have identified the issue and are working on a fix

A fix has been implemented and we are monitoring the results

We are continuing to monitor for further issues

This incident has been resolved.

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

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

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

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

The Hedera Testnet has been upgraded to v0.36.1 successfully

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.

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

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

We are currently investigating an issue with the testnet mirrornode

This incident has now been resolved

We are currently investigating an issue with the Hedera Testnet mirrornode

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

This incident has been resolved.

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.

We are continuing to investigate this issue.

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.

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.

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.

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.

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.

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.

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

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

This incident has been resolved.

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

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

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

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.

We are continuing to investigate 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 work on a fix for this issue.

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

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.

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

We are continuing to investigate this issue.

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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

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

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