Tenderly had 47 outages in the last 2 years totaling 102h 9m of downtime — averaging 1.9 incidents per month.
There were 47 Tenderly outages since January 21, 2025 totaling 102h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.
We want to inform you about an incident on our Base network where no requests were served between 05:53 and 06:22 CET. The eth_sendRawTransaction was not working until 07:15 CET.
This incident has been resolved.
Users using Polygon Mainnet APIs will not be able to retrieve data after block 76440930. Head of the chain (latest 128 blocks) remain unaffected. We are actively working with Polygon team on resolving the issue.
The issue has been identified and historical nodes are processing again. We will share new update once the problematic block range has been synced.
Incident has been resolved, nodes are in sync.
We’re actively tracking this issue in coordination with updates from the Polygon Foundation. We’ll share further updates as progress is made. https://status.polygon.technology/incidents/c8nc05x3qvmg
Our node clients are now back in sync. A backfill process has been started to recover the skipped blocks. ETA for backfill is ~15mins.
The skipped block range has been fully backfilled, and all nodes are operating in sync. Normal network functionality has been restored.
We had an incident on Base where we did not produce new blocks between 14:08 and 14:36 CET. This affected our Virtual Testnet, Explorer and Node RPC. After this lag started to drop for Node RPC and after 14:51 we had fully mitigated the lag. Explorer and Virtual Testnets are fully operational at 15:22. Users still may experience request latency for Node RPC based in what region they are located. As of now all requests are forwarded to us-west, so us-east and europe regions might experience latency.
A fix has been implemented and we are monitoring the results.
Issues are fully mitigated.
We are experiencing lag on Polygon mainnet RPC. Team is investigating the issue.
The issue has been identified and a fix is being implemented.
Fix has been implemented and lag is dropping.
This incident has been resolved.
We experienced a brief lag on polygon mainnet RPCs at 08:05 UTC this morning. The team was immediately informed by our alerting system and the lag was fully resolved at 08:25 UTC. Maximum lag was ~200 blocks.
We are currently experiencing a halt on Berachain Bepolia, with the network stalled at block height 7,816,796. The explorer is also stalled at this height. Our engineering team is actively investigating the issue and working toward a resolution.
The incident has been resolved. All nodes are now in sync and serving the latest data
Investigating - The Polygon mainnet is currently experiencing a network-wide stall at block height 74,592,247. This is affecting all network operations. Our team is actively working on a node upgrade to resolve this issue. We will provide updates as the situation progresses. Thank you for your patience during this time.
Update - The Polygon mainnet remains stalled at block height 74,592,247. Important: The new Heimdall v0.2.16 upgrade has been found to cause issues with execution layer clients (Bor & Erigon). The upgrade is now PAUSED until further notice from the Matic Foundation. Please do not proceed with any node upgrades at this time. We will provide updates as soon as we receive guidance from the Matic Foundation.
The issue has been fully mitigated, all nodes are now in sync and serving the latest data. We are continuing to monitor the results.
The incident has been resolved.
The Base block explorer was briefly unavailable between 07:39 AM and 08:12 AM (UTC+2) on July 30, 2025. During this time: • The Explorer didn’t display any transactions, and it wasn’t possible to search for them. • Requests to fetch transaction receipts via the Node were also failing during this period. • As a result, some Alerts and Web3 Actions may have been skipped.
The issue has been resolved, and everything is now working normally. Any missed blocks have been backfilled. What happened: • Between 07:39 and 08:25 AM (UTC+2), some of our internal services were temporarily down. • From 07:10 to 10:15 AM (UTC+2), the Base explorer, transaction search, and receipt fetching from the node (EU region only) were also affected. All systems are now fully operational.
We had a lag on Polygon network from 2025-07-19 06:20:00 to 2025-07-19 08:40:00. The lag has been fully mitigated. Backfilling of historical data is currently in progress, from 74135907 to 74137899 block, with an estimated completion time of approximately 3 hours.
The job backfilling of historical data has completed and Tenderly nodes are serving all block ranges for Polygon mainnet again.
Currently showcasing and loading transactions for Base is not possible. Monitoring (Alerts and Web 3 Actions) are also degraded. We are investigating the issue
Team has identified the potential issue and is releasing a hotfix.
We have deployed the fix and are now observing how the system is reacting. We are loading most of the transactions on the Base Explorer, but degradation may occur. Currently Monitoring system is catching up to the lag that has been accumulated due to the outage. We expected to be in sync in ~2h.
The incident has been resolved. And monitoring lag has been fully mitigated. All systems are functioning and back to normal.
Network wide incident has been identified on Polygon mainnet
Team is still actively working on stabilising Polygon mainnet, lag was observed on Polygon RPCs on couple of occasions 23:30-01:20 CEST and 4:55 - 9:50 CEST. To mitigate the lag the unprocessed blocks are skipped and the backfilling process is started.
The lag has been fully mitigated and all nodes are now in sync. Backfilling of historical data is currently in progress, with an estimated completion time of approximately 2 hours.
The job backfilling of historical data has completed and Tenderly nodes are serving all block ranges for Polygon mainnet again.
We're currently experiencing issues with creating Virtual Testnets for networks Sophon, Sophon Testnet, Lens, ZkSync Era and Zksync Era Sepolia. The team is working on it and we'll post update as soon as possible.
The team improved the situation but Virtual Testnet creation for the listed networks is still unstable - issues during Virtual Testnet creation are still possible. The team will continue working on this in order to fix the issue fully. We'll keep you posted!
This incident has been resolved.
On June 12th since around 17:50 UTC Web 3 Actions and Alerts monitoring performance has been degraded. Incident was mitigated at around ~19:00 UTC.
We noticed increased number of timeouts on mainnet vNet RPCs. The team is investigating the RC.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We experienced small downtime on all Node WSS connections on 10th of June at 15:02 UTC. Only US regions were affected - connections were dropped and new ones couldn’t established. US-east was down for ~4min and US-west for ~8min.
We're experiencing alert and web3 actions delays on all networks. The team is currently working on the fix .
We are continuing to work on a fix for this issue.
The delay issues have been resolved on all networks except BNB for now. The team will work on a fix for BNB and we’ll keep you posted on the progress.
As of approximately 6:00 PM UTC on May 26th, alerts and Web3 actions on BNB are no longer experiencing delays. To mitigate the issue, we had to skip processing blocks from the timeframe between 2:00 PM and 6:00 PM UTC on May 26th. As a result, any alerts that would have been triggered during that period were not processed. We appreciate your understanding and apologise for any inconvenience this may have caused.
We're having issues on Ethereum Sepolia RPC at the moment so you might experience increase in errors. The team is working on the fix.
We are continuing to work on a fix for this issue.
The incident has been resolved and we are serving traffic trough Sepolia RPC again.
Node RPC for Base network is experiencing issues in all regions.
Base Node RPC is in sync and working but rerouted to Euorpe since 12:37 CET
Node RPC for Base in US east region is syncing and is no longer rerouted to EU. US west is in the process of syncing and should be in full sync in ~ 30 minutes.
Node RPC for Base in US west region is syncing and is no longer rerouted to EU. All regions have been recovered and the incident is resolved.
Explorers and project transaction listing are not working at the moment. The team is working on resolving the issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
Affected networks are: BNB, Base, Arbitrum and Polygon
This incident has been resolved on April 3rd at 5pm CEST.
Our Base RPCs are lagging and we're working on a fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.