Flow Status

Flow mainnet is in the Epoch Fallback Mode

Update - The network is now in the Epoch Fallback Mode (EFM) and automatic epoch transitions have paused.

As a workaround to ensure that staking operations continue, the governance committee submitted a transaction (transaction ID: 05abc413e6426d83fef0c79a9f59c31b0194f26427b07ab0c1c9da7750cfba22) to advance the epoch.

We will share the plan and timelines around recovering the network from EFM and resuming automatic epoch transitions.
Sep 11, 2024 - 19:39 UTC

Identified - Earlier today, a system transaction failed to execute. The root cause has been identified and fixed however as a consequence of the failure to execute the system transaction, the network will enter the Epoch Fallback Mode (EFM) in a couple of hours.
The network will continue producing blocks and executing transactions in the Epoch Fallback Mode. However, epoch transitions will pause. Staking related operations, which depend on the epoch transitions, will also pause.
We will soon share a plan and timelines to recover from the EFM.
Sep 11, 2024 - 17:31 UTC

Flow Testnet Operational

Flow mainnet core components Operational

Collection Finalization Operational

Block Finalization Operational

Transaction Execution Operational

Block Sealing Operational

Flow mainnet Access APIs Operational

GRPC API Operational

GRPC Web API Operational

REST API Operational

EVM Gateway Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Sep 13, 2024

No incidents reported today.

Sep 12, 2024

EVM Gateway APIs Unavailable

Resolved - We have resolved the issue and confirmed the availability of the EVM GW
Sep 12, 15:27 UTC

Monitoring - We have made changes to bring the EVM Gateway back online. We are now monitoring as it catches up.
Sep 12, 15:05 UTC

Identified - We have identified an issue with the EVM GWs, and we are working to implement a fix to recover the APIs.
Sep 12, 14:55 UTC

Sep 11, 2024

EVM Gateway is in a crash loop

Resolved - This incident has been resolved.
Sep 11, 20:09 UTC

Monitoring - A fix has been implemented and we are monitoring the results.
Sep 11, 19:31 UTC

Update - We have tested the fix, working on deploying it.
Sep 11, 19:07 UTC

Identified - The Flow EVM Gateway is currently in a crash loop.
The issue has been identified.
Sep 11, 17:20 UTC

Sep 10, 2024

No incidents reported.

Sep 9, 2024

No incidents reported.

Sep 8, 2024

No incidents reported.

Sep 7, 2024

No incidents reported.

Sep 6, 2024

Deleting "Flow Mainnet (depcreated -please 'Flow mainnet..)" and "Flow Crescendo (Preview)" from the status page

Resolved - This is not an incident.

This is only to notify that the following two entries will be deleted from the Flow status page (https://status.onflow.org/):

1. Flow Mainnet (deprecated - please use 'Flow mainnet core components' and 'Flow mainnet Access APIs' instead) - Please subscribe to Flow mainnet core components and Flow mainnet Access APIs instead if you haven't already.

2. Flow Crescendo (Preview) - This network is being shut down as Crescendo is now live on mainnet.

Thank you,
Flow Foundation
Sep 6, 17:53 UTC

Sep 5, 2024

Flow Mainnet Transaction execution has stopped

Resolved - The issue has now been resolved and the network is fully functional.
Sep 5, 20:01 UTC

Update - We are continuing to monitor for any further issues.
Sep 5, 19:39 UTC

Monitoring - The performance issues have been resolved and collection nodes have recovered.
Developers are encouraged to use the next 20-30 minutes to test their apps and ensure there are no problems ahead of our next update.
Sep 5, 19:30 UTC

Investigating - Flow Mainnet network is currently not processing transactions. The Flow core team is investigating.
Sep 5, 09:46 UTC

📣 The Flow Crescendo Network Upgrade 📣

Completed - The Crescendo network upgrade is now complete and network functionality is fully restored.

The Block start height is: 85981135

See the full change log for this network upgrade here: https://github.com/onflow/flow-go/releases/tag/v0.37.10

Thank you developers for your patience and understanding,

The Flow Foundation
Sep 5, 07:23 UTC

Update - The upgrade is almost complete. 447 nodes are running the Crescendo software and blocks are processing normally.

As a final stage, we suggest that developers test and validate that the upgrade was successful for their contracts through their own access nodes. During this app-testing phase, we request that RPC operators disallow connections to avoid disrupting the tests. This means end-users cannot submit transactions until testing is complete.

The next update will be provided in 3 to 4 hours.
Sep 5, 03:10 UTC

Update - The state migration is now complete. The network nodes are now being initialized
Sep 4, 18:39 UTC

Update - The first phase of state migration which migrated the execution state to the new Atree Register Inlining format is complete. The second phase which migrates the states to the new Cadence 1.0 format has now started and will take approximately 2 hours 30 minutes to complete.
Sep 4, 15:35 UTC

Update - The Flow mainnet Crescendo network upgrade is underway. The network was stopped at height 85981134.
State migration has started and will take approximately 5 hours.
Sep 4, 12:36 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 4, 12:00 UTC

Update - Reminder: Crescendo mainnet network upgrade tomorrow.

🛠️ The Flow network will be in maintenance mode during this upgrade, meaning transactions will not process.

For Developers - Please make sure you're prepared for this upgrade by having your code updated & staged for Cadence 1.0. You can find all the details to do so in here: https://cadence-lang.org/docs/cadence-migration-guide.
Sep 3, 18:24 UTC

Update - 7 Days Until The Flow Network Upgrade (Crescendo)

Crescendo is the most significant upgrade to the Flow network since genesis. This upgrade includes full EVM equivalence for all developers on Flow, as well as marking the point of maturity for the Flow native programming environment with Cadence 1.0.

🛠️ The Flow network will be in maintenance mode during this upgrade, meaning transactions will not process.

For Developers - Please make sure you're prepared for this upgrade by having your code updated & staged for Cadence 1.0. You can find all the details to do so in here: https://cadence-lang.org/docs/cadence-migration-guide.

Thank you,

The Flow Foundation
Aug 28, 19:41 UTC

Scheduled - Crescendo is the most significant upgrade to the Flow network since genesis. This upgrade includes full EVM Equivalence for all developers on Flow as well as marking the point of maturity for the Flow native programming environment with Cadence 1.0.

Flow Mainnet Maintenance
Flow Mainnet will be upgrading on Wednesday, 4 September 2024, 12pm UTC (5am PT), transitioning from Mainnet 24 to Mainnet 25.

Flow Mainnet will be unavailable between 12pm UTC (5am PT) to 6pm UTC (11am PT) on that day.
Please plan accordingly for this Flow network upgrade.

All smart contracts must be upgraded to Cadence 1.0 before the upgrade. To ensure a seamless migration to Cadence 1.0, we are implementing a Cadence 1.0 readiness plan to flag and log transactions with potential breaking code. Starting August 7th, flagged transactions will incrementally face failures, reaching 100% by the time of the Crescendo network upgrade on September 4th, helping developers see if they need to update their smart contracts. Contracts that have been successfully prepared for Cadence 1.0 will not be impacted.

For more details on the Crescendo network upgrade you can visit here ⤵️
👉 Flow Crescendo: Road To Mainnet Upgrade

Please subscribe to this page for updates.

Thank you,

The Flow Foundation 🌊
Aug 2, 16:32 UTC

Sep 4, 2024

Sep 3, 2024

No incidents reported.

Sep 2, 2024

No incidents reported.

Sep 1, 2024

No incidents reported.

Aug 31, 2024

No incidents reported.

Aug 30, 2024

No incidents reported.