Tenderly Outage History

We are aware that Ronin (chain ID: 2020) is currently unavailable. This is due to a planned L1 → L2 migration being performed by the Ronin team. Starting at approximately 15:00 UTC on May 12, 2026 (block #55577490), the Ronin chain halted block production to begin its upgrade to an Ethereum L2. The migration is expected to take up to ~10 hours. Once the Ronin team completes the migration and provides updated snapshots and configurations, we will bring up new nodes to restore full RPC support on Tenderly. We will post updates here as the migration progresses. For more details on the migration, refer to the official Ronin announcement: https://blog.roninchain.com/p/ronin-is-coming-home-to-ethereum

The Polygon Node RPC is back in sync with the chain head. We're continuing to monitor.

A fix has been implemented and we are monitoring the results. Alerts and Web 3 Actions delivery will also be delayed starting 10:13 UTC, current lag is ~16min we expect full recovery within 10-15min.

We have successfully restored all Base Sepolia features. Virtual Testnets and WebSockets are back up and fully operational. The one remaining item is `eth_subscribe`, which is currently unavailable for both Node and Virtual TestNets. Our team is aware and actively working on it - we expect it to be re-enabled by the morning hours.

We are currently investigating an issue affecting the Sei Pacific-1 network. The root cause has been identified as a network-level issue on Sei's infrastructure. We are in active communication with the Sei team and are monitoring the situation as they work toward resolution. We will provide updates as new information becomes available.

A fix has been implemented and both networks (Polygon & Polygon Amoy) have no lag at the moment. The team will continue to monitor the status for a while.

We are pleased to report that Node RPC, Virtual Testnets, Simulations, and Debugger have been restored and are operating normally. Our team is actively working to resolve the remaining issues affecting the following components: - Explorer - Monitoring (Alerts and Web3 Actions) We will provide a further update once these components have been fully restored. We apologize for the continued inconvenience.

A fix has been implemented and we are seeing constant drop in delays of Web3 Action executions triggered by block events.

We’ve implemented a fix and are seeing the delays gradually decrease. Full recovery is expected in approximately 1.5 hours.

We have mitigated the issues on Virtual Testnets WebSocket connections and this feature should be fully functional. Alerts (currently being monitored) - notifications will be back in real time 17:30 UTC Web3 Actions (currently being monitored) - notifications will be back in real time - transaction based actions - 17:30 UTC - block based actions - 19:00 UTC

Alerts have been fully returned to normal. Web3 Actions are still due to catch up and return to real time notifications.

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

We managed to recover and will continue monitoring the system.

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

We experienced a block lag on the Flare network between 4:21 PM and 5:45 PM UTC. The issue has been resolved, and our team is actively monitoring the network to ensure stability.

We've experienced lag on Base network during following timeframes: 13:40-13:50 UTC and 14:17 - 14:22 UTC. The team mitigated the issue.

Alerts and Web3 Actions are experiencing delays for the block range [78,266,299 – 78,266,736]. Our team is actively backfilling the affected blocks to ensure that no alerts or Web3 Actions are skipped — only delayed. The team is also working on resolving Node RPC, Simulator and Explorer delays. We appreciate your patience and apologize for the inconvenience.

Between 07:46 and 08:20 CET, we experienced block lag on Mainnet, Sepolia, Base, Base Sepolia, Optimism, and Optimism Sepolia affecting both the Node RPC and Simulator. The issue has since been resolved, and our team is actively monitoring the situation to ensure stability. We apologize for any inconvenience this may have caused.

The nodes are back in sync, we will continue to monitor the network health.

We’re currently experiencing delays of up to 10 minutes in alert notifications. Our team is actively working on a fix, and we expect the issue to be resolved within the next one to two hours. Thank you for your patience and understanding.