There were 9 Tenderly outages since March 5, 2026 totaling 102h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.
Monitoring lag was detected on Berachain Mainnet and Unichain Sepolia between 09:20 UTC and 09:49 UTC. Lag has since dropped to 0 and all components are operational.
We experienced elevated latency on Polygon Node RPC starting at 16:45 CEST. The issue lasted approximately 15 minutes (16:45–17:01 CEST) and has since been resolved.
We're investigating an issue where requests to the Simulator API with save: true, and dashboard flows that save a simulation, are currently returning errors for all networks. Ephemeral simulation runs (without save), and Node RPC simulation methods are not affected. We'll share an update as soon as we have more information.
We are continuing to work on a fix for this issue.
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.
Alerts and Web 3 Actions delivery is fully recovered.
We are currently experiencing an issue affecting all Tenderly features on Base Sepolia. Our team has been notified and is actively investigating and working on a fix. All other networks are unaffected. We will provide updates as the situation develops. We apologize for the inconvenience.
We have resolved the issue affecting Node RPC, Monitoring, and Simulations on Base Sepolia - these features are now fully operational. Our engineering team is continuing to work on restoring Websockets and Virtual TestNets. We will share another update as soon as those are resolved. Thank you for your patience.
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.
This incident has been resolved.
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.
The issue affecting the Sei Pacific-1 network has been resolved. All systems are operating normally. We apologize for any inconvenience caused and thank you for your patience.
We have identified our Polygon Mainnet nodes are lagging by ~1500 blocks as well as our Polygon Amoy by ~3000 blocks. Team is working on investigating the issue.
Team has identified the issue on Polygon Mainnet with lag dropping. Polygon Amoy lag continues to rise, and the team is continuing the investigation.
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.
This incident has been resolved.
We're currently experiencing lag on Taiko Mainnet network that's affecting all features. The team is working on resolution and we'll keep you posted on all updates.
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.
Explorer and Monitoring (Alerts and Web3 Actions) have been fully restored. All components are now operating normally and the incident has been resolved.
The Sonic chain is currently experiencing a network-wide issue causing nodes to halt during block processing. Our Sonic chain endpoints are affected as a direct result. We are in active contact with the Sonic team and are monitoring the situation closely for updates.
The node lag affecting the Sonic network has been resolved. All services are fully operational as of 16:51 CEST. We apologize for any inconvenience caused.
Between 14:34 and 14:54 UTC, our node infrastructure experienced increased latency and block synchronization delays across multiple networks: Ethereum Mainnet Base Polygon Optimism Worldchain Arbitrum Arbitrum Sepolia Monad Avalanche Plasma Testnet Blast Mainnet Base Sepolia Arbitrum Nova Requests to these networks may have returned stale or delayed data during this window. Additionally, related platform services — including transaction simulations, Virtual Testnet creation, and monitoring — were impacted across the following networks: BSC BSC Testnet Conflux eSpace Conflux eSpace Testnet Avalanche Base Boba Sepolia Ethereum Mainnet Flare Gnosis Gnosis Chiado Injective Mantle Metis Sepolia Monad Testnet Optimism Bedrock Optimism Sepolia Plasma Testnet Polygon Scroll SEI Pacific Sepolia Ethereum Sonic Blaze Stable Testnet Swellchain Tempo Moderato Tempo Testnet Zircuit Garfield During this period, simulations may have failed, Virtual Testnets could not be created at newer blocks, and monitoring experienced delays. All services have fully recovered and are operating normally. No data loss occurred.
Pingoru polls Tenderly's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required