Flow Outage History

28 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Flow status100.00% uptime history

Every Recorded Flow Incident

Flow incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 18, 2026Flow Mainnet Height Co-ordinated Zero Downtime UpgradeThe scheduled maintenance has been completed.30 minScheduled
Aug 17, 2026Flow Testnet Height Co-ordinated Zero Downtime UpgradeThe scheduled maintenance has been completed.30 minScheduled
Jul 2, 2026Flow Mainnet Height Co-ordinated Zero Downtime UpgradeThe scheduled maintenance has been completed.30 minScheduled
Jun 30, 2026Flow Testnet Height Co-ordinated Zero Downtime UpgradeThe scheduled maintenance has been completed.30 minScheduled
May 18, 2026Flow Mainnet Zero Downtime Height Co-ordinated UpgradeThe scheduled maintenance has been completed.10 minScheduled
May 14, 2026Flow Testnet Zero Downtime Height Co-ordinated UpgradeThe scheduled maintenance has been completed.10 minScheduled
Apr 7, 2026Flow Mainnet Zero Downtime Height Co-ordinated UpgradeThe scheduled maintenance has been completed.10 minScheduled
Feb 24, 2026Flow Mainnet Zero Downtime Height Co-ordinated UpgradeThe scheduled maintenance has been completed.30 minScheduled
Feb 24, 2026Flow Mainnet Network Issue### **Summary** On February 23, 2026, Flow Mainnet experienced an outage that temporarily halted block production. The network entered a safe state after detecting inconsistent results between nodes during preparations…3h 57mResolved
Feb 18, 2026Flow Testnet Zero Downtime Height Co-ordinated Upgrade TestThe height coordinated upgrade (HCU) on testnet is now complete. Testnet was successfully upgraded without any downtime 🎉🎉.30 minScheduled
Feb 13, 2026Flow mainnet height co-ordinated upgradeThe HCU is now complete. Block Height: 142100300 If you are running an access or a verification node, please update to docker tag v0.46.1-rc.130 minScheduled
Feb 13, 2026Flow Testnet Height Co-ordinated UpgradeThe scheduled maintenance has been completed.30 minScheduled
Feb 12, 2026Flow Testnet Network UpgradeThe EVM endpoint is up and running as well. Flow Testnet is now fully functional.1h 0mScheduled
Feb 12, 2026Flow Testnet Network IssueYesterday 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…2h 11mResolved
Feb 6, 2026Flow Mainnet Height Co-ordinated UpgradeThe scheduled maintenance has been completed.10 minScheduled
Feb 4, 2026Flow Testnet Height Co-ordinated UpgradeThe scheduled maintenance has been completed.30 minScheduled
Jan 29, 2026Flow Mainnet Height Co-ordinated UpgradeThe Height Coordinated Upgrade on mainnet is now complete. Block height for HCU: 14047844430 minScheduled
Jan 28, 2026Transaction ingestion is degradedThe incident has been resolved and transactions ingestion has recovered. Testnet will also automatically recover from the Epoch Fallback Mode (thanks to Epoch Fallback Recover mechanism introduced last year -…22 minResolved
Jan 28, 2026Flow Testnet Height Co-ordinated UpgradeThe testnet HCU is now complete. This upgrade introduced a non-breaking stricter transaction verification change - https://forum.flow.com/t/stricter-transaction-verification-in-the-flow-virtual-machine-fvm-and-access-ap…10 minScheduled
Jan 7, 2026Degraded Performance on Testnet and Mainnet EVM EndpointsThis incident has been resolved.1h 9mResolved
Jan 6, 2026Flow Mainnet Height Co-ordinated UpgradeThe scheduled maintenance has been completed.30 minScheduled
Jan 6, 2026Flow Testnet Height Co-ordinated UpgradeThe scheduled maintenance has been completed.10 minScheduled
Jan 3, 2026Flow mainnet height co-ordinated upgradeThe scheduled maintenance has been completed.10 minScheduled
Jan 3, 2026Flow mainnet height co-ordinated upgradeThe scheduled maintenance has been completed.30 minScheduled
Dec 27, 2025Flow Mainnet SporkUPDATE: FLOW NETWORK FULLY OPERATIONAL - CADENCE AND EVM ENVIRONMENTS LIVE The Flow network is fully operational. Both Cadence and EVM environments are live and processing transactions. NETWORK STATUS: BOTH EXECUTION…1h 0mScheduled
Dec 27, 2025Transactions are not being ingestedThe root cause of the issue has been resolved and the network has been upgraded. See maintenance incident: https://manage.statuspage.io/pages/ytw5bdg6zr13/incidents. However, the collection ingestion is still paused.14h 13mResolved
Dec 5, 2025EVM Endpoint Degraded / Not Responding# **Postmortem: EVM Endpoint Incident - December 5, 2025** ## **Introduction** On December 5, 2025, the Flow EVM JSON-RPC endpoint experienced five hours of unresponsiveness, followed by an additional five hours of…8h 27mResolved
Dec 4, 2025Flow Mainnet Height Co-ordinated upgradeThe Height Coordinated Upgrade is now complete. It occurred at block height 134918777. Transaction execution has resumed.10 minScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Flow incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Flow Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Flow acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Flow outage in this window ran 14h 13m, against a mean recovery of 1h 25m. If you depend on Flow in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.