Flow Swiss incident

Sealing & Finalization halted on Testnet

Resolved after 20 minutes, affecting Flow Testnet, on July 10, 2025.

postmortem Jul 11, 2025, 11:23 PM UTC

## **Postmortem: Testnet Sealing and Finalization Interruption – July 10, 2025** **Summary** On July 10, 2025, from 11:02 AM to 11:22 AM PST, Testnet experienced a temporary halt in block sealing and finalization. The issue was identified and resolved within 20 minutes. Mainnet remained fully operational and was not affected at any point. **Root Cause** An internal testing framework inadvertently interfered with Testnet node communications, resulting in a disruption to the consensus process. This occurred due to overlapping configurations between the testing environment and Testnet. **Resolution and Preventative Measures** To ensure this does not happen again: * Firewall rules have been updated to sandbox the internal testing framework, fully isolating it from Testnet environments. * The testing framework has also been modified to avoid any attempts to connect to or interact with the Testnet network. Thank you, Flow Team

Started
Jul 10, 2025, 07:02 PM UTC
Resolved
Jul 10, 2025, 07:22 PM UTC
Duration
20m
Detected by Pingoru
Jul 10, 2025, 07:02 PM UTC

Affected components

Flow Testnet

Update timeline

  1. resolved Jul 10, 2025, 07:10 PM UTC

    The issue has been resolved and the network has fully recovered. Please note that this incident impacted Testnet only — Mainnet remained unaffected and continues to operate normally.

  2. postmortem Jul 11, 2025, 11:23 PM UTC

    ## **Postmortem: Testnet Sealing and Finalization Interruption – July 10, 2025** **Summary** On July 10, 2025, from 11:02 AM to 11:22 AM PST, Testnet experienced a temporary halt in block sealing and finalization. The issue was identified and resolved within 20 minutes. Mainnet remained fully operational and was not affected at any point. **Root Cause** An internal testing framework inadvertently interfered with Testnet node communications, resulting in a disruption to the consensus process. This occurred due to overlapping configurations between the testing environment and Testnet. **Resolution and Preventative Measures** To ensure this does not happen again: * Firewall rules have been updated to sandbox the internal testing framework, fully isolating it from Testnet environments. * The testing framework has also been modified to avoid any attempts to connect to or interact with the Testnet network. Thank you, Flow Team

Your product runs on more than Flow Swiss

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →