Flow Testnet Network Issue

Update timeline

1. investigating Feb 12, 2026, 03:21 AM UTC

   Block production on testnet has halted. We are currently investigating the issue. No impact on mainnet.

2. investigating Feb 12, 2026, 04:17 AM UTC

   Flow Testnet will be undergoing a network upgrade (spork) to recover from the current issue.

3. resolved Feb 12, 2026, 05:33 AM UTC

   The issue has been resolved with a full network upgrade (spork) on testnet

4. postmortem Feb 12, 2026, 09:29 PM UTC

   Yesterday 2/11, Flow Testnet experienced an outage during routine maintenance. ### **What Happened** The Flow team was performing maintenance to ensure testnet consensus nodes had enough disk space. During this work, a disk space reclamation process was run. There was a flaw in this process when applied to consensus nodes that caused the DKG file to be deleted. Once a majority of the nodes were updated, they were no longer able to finalize blocks. As a result, finalization halted and the network stopped progressing. _Please note: Mainnet was not impacted._ ### **Recovery** Possible recovery paths were evaluated. The safest and least disruptive way to restore the network was to perform a full network upgrade on testnet. The upgrade restored consensus and returned the network to a healthy state. ### **EVM Follow Up** After the upgrade, EVM nodes encountered a separate issue and were not able to smoothly transition to the new network state. Additional remediation was required to bring EVM services back into sync. ### **Next Steps** * Updating and testing the disk space reclamation process, adding more safety checks to ensure critical consensus state is preserved, along with clearer documentation. * Improving the EVM gateway to make it more robust during network upgrades and transitions. * Reviewing alerting and operational safeguards to surface issues more quickly.