Tenderly Outage History
Uptime record, past incidents, and downtime history for Tenderly.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| June 2026 | 85.2% | 27 | 4 |
| May 2026 | 87.1% | 31 | 4 |
| April 2026 | 80% | 30 | 6 |
| March 2026 | 66.7% | 3 | 1 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Mar 29
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
June 2026
Delayed Base RPC syncing following Base network-wide halt
Started: Jun 25, 6:23 PM
monitoring
Our Base nodes have recovered and caught up to the live chain head following today's Base network-wide halt. RPC is now serving current block data, though some services may still need a little time to fully process the backlog and return to normal. We are monitoring to confirm syncing stays stable.
Jun 25, 6:52 PM
identified
Base mainnet experienced a network-wide chain halt earlier today that paused block production across the network. We are actively working with the Base team to recover our Base nodes and resume syncing. You may see delayed or stale block data on Base until this is resolved. You can follow the upstream incident on the Base status page at https://status.base.org/incidents/5c4gm1wzbjs4, and we will update here as recovery progresses.
Jun 25, 6:23 PM
Monitoring Lag - Alert and Action Notifications
Started: Jun 25, 3:28 PM
monitoring
Monitoring — 16:57 UTC
Recovery is progressing. The alert delivery backlog has decreased significantly and continues to clear. We are monitoring until full recovery is confirmed.
Delayed notifications will be delivered automatically — no action is required on your end.
Jun 25, 3:31 PM
investigating
Identified — 16:30 UTC
We have identified the cause: a significant surge in transaction volume on Base, Monad, and Arbitrum Sepolia caused a backlog in our alerting pipeline.
End-to-end alert delivery latency peaked at approximately 7 minutes.
All networks are affected as our alerting pipeline is shared. Traffic is now normalizing and latency is slowly decreasing.
Jun 25, 3:30 PM
investigating
We are continuing to investigate this issue.
Jun 25, 3:28 PM
investigating
Investigating — 15:58 UTC
We have noticed a performance degradation on our alerting system starting 15:58 UTC.
Alert and action-triggered notifications are delayed across all networks. Slack, Telegram, and email alerts are operational.
Jun 25, 3:28 PM
Monitoring Lag on Arbitrum Sepolia, Monad and Base
Started: Jun 24, 11:08 AM
monitoring
Team has discovered the RC and has applied the fix. Monitoring as the lag decreases.
Jun 24, 11:56 AM
identified
We have noticed a performance degradation on our alerting system starting 13:08 CEST
Alerts are delayed on three networks Arbitrum Sepolia, Monad and Base.
Actions triggered by alerts are impacted.
Slack, Telegram, email alerts are operational.
Jun 24, 11:55 AM
Alerts — Webhook Delivery Disruption (All Networks)
Started: Jun 11, 9:54 AM
monitoring
Our team has identified the issue and is actively working on a fix. All undelivered alerts will be backfilled once the issue is resolved — no data will be lost.
We will continue to post updates here as our investigation progresses.
Jun 11, 9:58 AM
monitoring
We are currently investigating an issue affecting webhook delivery for Alert destinations across all networks. Affected alerts are not being delivered to configured webhook endpoints at this time.
Jun 11, 9:54 AM
Delayed processing on Alerts and Web3 Actions
Started: Jun 5, 4:27 PM
monitoring
We are currently experiencing increased latency affecting Alerts and Web3 Actions across all networks. Our team has identified the cause and deployed a fix that improved the situation and they are currently working on complete resolution. Importantly, no Alerts or Web3 Actions will be skipped. All events are being queued and will be processed, so you will receive every notification and action execution once the backlog clears. We will post another update as soon as processing returns to normal.
Jun 5, 4:27 PM
Delayed processing on Alerts and Web3 Actions
Started: Jun 5, 7:35 AM
identified
We are currently experiencing increased latency affecting Alerts and Web3 Actions across all networks. Our team has identified the cause and deployed a fix, and processing lag is already dropping. We expect full recovery within approximately 15 minutes. Importantly, no Alerts or Web3 Actions will be skipped. All events are being queued and will be processed, so you will receive every notification and action execution once the backlog clears. We will post another update as soon as processing r...
Jun 5, 7:35 AM
May 2026
Node Infrastructure Degradation
Started: May 16, 7:01 AM
investigating
Between May 15 20:33 UTC and May 15 22:42 UTC, a networking issue caused node infrastructure to fall behind chain tip on multiple networks.
Networks with request failures during the window: Ink, Avalanche, Soneium, World Chain Sepolia, Ronin, Polygon Amoy, Ink Sepolia. Requests against these networks from our EU region would have errored or timed out until traffic was rerouted.
Networks with noticeable lag during the window: Ethereum, Base, Arbitrum One, BNB, Blast, Polygon, Avalanche, Sepo...
May 16, 7:01 AM
Ronin Network Unavailable – Scheduled L2 Migration
Started: May 12, 3:34 PM
monitoring
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 supp...
May 12, 3:34 PM
Polygon Node RPC: delayed block sync
Started: May 3, 7:02 PM
monitoring
The Polygon Node RPC is back in sync with the chain head. We're continuing to monitor.
May 3, 7:49 PM
investigating
Our Polygon Node RPC is lagging behind the chain head. The team is investigating and we'll post an update shortly.
May 3, 7:02 PM
April 2026
Simulator issue
Started: Apr 28, 9:48 AM
monitoring
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.
Apr 28, 10:08 AM
identified
We are continuing to work on a fix for this issue.
Apr 28, 9:48 AM
identified
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.
Apr 28, 9:48 AM
Base Sepolia outage (affecting Node RPC, Virtual Testnets, Monitoring, Simulations)
Started: Apr 20, 7:05 PM
monitoring
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.
Apr 20, 9:01 PM
identified
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.
Apr 20, 8:30 PM
identified
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.
Apr 20, 7:05 PM
Sei Pacific-1 network wide issue
Started: Apr 13, 9:14 AM
monitoring
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.
Apr 13, 9:14 AM
Polygon Node Lag
Started: Apr 9, 7:50 PM
monitoring
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.
Apr 9, 9:23 PM
identified
Team has identified the issue on Polygon Mainnet with lag dropping.
Polygon Amoy lag continues to rise, and the team is continuing the investigation.
Apr 9, 8:43 PM
investigating
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.
Apr 9, 7:50 PM
Taiko Mainnet lag
Started: Apr 2, 6:58 PM
monitoring
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.
Apr 2, 7:01 PM
identified
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.
Apr 2, 6:58 PM
March 2026
Network-wide issue on Sonic chain
Started: Mar 25, 2:29 PM
identified
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.
Mar 25, 2:29 PM