Tenderly Outage History
Tenderly is up right nowPingoru has recorded 50 incidents for Tenderly: 33 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 7 | 8 of 720 (1%) |
| May 2026 | 3 | 26 of 744 (3%) |
| June 2026 | 6 | 7 of 720 (1%) |
| July 2026 | 1 | 2 of 744 (0%) |
| August 2026 | 2 | 0 of 744 (0%) |
| September 2026 | 1 | 1 of 720 (0%) |
| October 2026 | 0 | 0 of 530 (0%) |
Incidents, newest first
Notice September 8, 2026 Platform-Wide Service Disruption 1h 8m
Started Sep 08, 2026, 08:15 AM UTC· resolved Sep 08, 2026, 09:24 AM UTC
- monitoring Sep 08, 2026, 08:15 AM UTC
We are currently experiencing a platform-wide issue affecting all features. Our team has identified the disruption and is actively working on a resolution. We understand this is impacting your ability to use our services and apologize for the inconvenience. We will provide updates as more information becomes available. Thank you for your patience.
- monitoring Sep 08, 2026, 09:12 AM UTC
All features except Explorer are now back to being operational. We're continuing to work on resolving the remaining issue with Explorer and will post another update as soon as it's fixed. Thank you for your patience.
- resolved Sep 08, 2026, 09:24 AM UTC
This incident has been resolved. All features, including Explorer, are now fully operational. Thank you for your patience while we worked through this issue.
Minor August 27, 2026 Delayed alert notifications 1m Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet and 829 more
Started Aug 27, 2026, 05:41 PM UTC· resolved Aug 27, 2026, 05:43 PM UTC
- monitoring Aug 27, 2026, 05:41 PM UTC
Between 16:25 and 17:17 UTC, alert notifications were delivered with an average delay of around 8 minutes. Alert processing continued throughout the whole period and no alerts were lost or skipped. We rolled out the fix, delivery caught up fully, and alerting has been operating normally since 17:17 UTC.
- resolved Aug 27, 2026, 05:43 PM UTC
This incident has been resolved.
Minor August 13, 2026 Lag on Gnosis Chiado testnet 20m
Started Aug 13, 2026, 03:44 PM UTC· resolved Aug 13, 2026, 04:04 PM UTC
- identified Aug 13, 2026, 03:44 PM UTC
We're currently experiencing lag on Gnosis Chiado testnet. We're working with Gnosis team on resolving the issue as soon as possible. Apologies for the inconvenience.
- resolved Aug 13, 2026, 04:04 PM UTC
The lag has been resolved. Gnosis Chiado testnet is operating as expected now.
Notice July 16, 2026 Login and Registration Issues 2h 8m
Started Jul 16, 2026, 09:15 AM UTC· resolved Jul 16, 2026, 11:23 AM UTC
- investigating Jul 16, 2026, 09:15 AM UTC
We're currently experiencing an issue affecting login and new account registration on the Tenderly Dashboard. Users who were already logged in prior to this incident should not be impacted. API access is unaffected. We're monitoring the situation and will post updates as we have them.
- resolved Jul 16, 2026, 11:23 AM UTC
The issue has been resolved - user can now login to Tenderly Dashboard
Minor June 25, 2026 Delayed Base RPC syncing following Base network-wide halt 37m Virtual Testnet, Explorer, Simulator, Alerts and 4 more
Started Jun 25, 2026, 06:23 PM UTC· resolved Jun 25, 2026, 07:00 PM UTC
- identified Jun 25, 2026, 06:23 PM UTC
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.
- monitoring Jun 25, 2026, 06:52 PM UTC
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.
- resolved Jun 25, 2026, 07:00 PM UTC
Base nodes have fully recovered and all Base services are operating normally again.
Minor June 25, 2026 Monitoring Lag - Alert and Action Notifications 1h 52m Alerts, Alerts, Alerts
Started Jun 25, 2026, 03:28 PM UTC· resolved Jun 25, 2026, 05:20 PM UTC
- investigating Jun 25, 2026, 03:28 PM UTC
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.
- investigating Jun 25, 2026, 03:28 PM UTC
We are continuing to investigate this issue.
- investigating Jun 25, 2026, 03:30 PM UTC
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.
- monitoring Jun 25, 2026, 03:31 PM UTC
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.
- resolved Jun 25, 2026, 05:20 PM UTC
We've confirmed that the elevated lag affecting Web3 Actions and Alerting has fully cleared. All systems are back to normal operation and performing as expected.
Minor June 24, 2026 Monitoring Lag on Arbitrum Sepolia, Monad and Base 1h 37m Alerts, Alerts, Alerts
Started Jun 24, 2026, 11:08 AM UTC· resolved Jun 24, 2026, 12:45 PM UTC
- identified Jun 24, 2026, 11:55 AM UTC
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.
- monitoring Jun 24, 2026, 11:56 AM UTC
Team has discovered the RC and has applied the fix. Monitoring as the lag decreases.
- resolved Jun 24, 2026, 12:45 PM UTC
All lag is gone and incident is resolved.
Minor June 11, 2026 Alerts — Webhook Delivery Disruption (All Networks) 1h 38m Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet and 829 more
Started Jun 11, 2026, 09:54 AM UTC· resolved Jun 11, 2026, 11:33 AM UTC
- monitoring Jun 11, 2026, 09:54 AM UTC
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.
- monitoring Jun 11, 2026, 09:58 AM UTC
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.
- resolved Jun 11, 2026, 11:33 AM UTC
The issue has been fully resolved and all alerts have been backfilled. Apologies for the inconvenience!
Minor June 5, 2026 Delayed processing on Alerts and Web3 Actions 1h 13m
Started Jun 05, 2026, 04:27 PM UTC· resolved Jun 05, 2026, 05:40 PM UTC
- monitoring Jun 05, 2026, 04:27 PM UTC
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.
- resolved Jun 05, 2026, 05:40 PM UTC
Alert and Web3 Action processing across all networks is back to normal and the backlog has fully cleared.
Critical May 15, 2026 Node Infrastructure Degradation 2h 9m Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet and 85 more
Started May 15, 2026, 08:33 PM UTC· resolved May 15, 2026, 10:42 PM UTC
- investigating May 16, 2026, 07:01 AM UTC
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, Sepolia, MegaETH, Gnosis, Ink, Soneium, Ronin. Traffic continued via fallback routing but customers may have seen intermittent errors, elevated latency, or delayed Alerts and Web3 Actions. The incident was fully resolved on May 15 at 22:42 UTC. All affected networks are back in sync and we are not observing any further disruptions.
- resolved May 16, 2026, 07:02 AM UTC
This incident has been resolved.
Critical May 12, 2026 Ronin Network Unavailable – Scheduled L2 Migration 19h 48m Virtual Testnet, Explorer, Simulator, Alerts and 4 more
Started May 12, 2026, 03:34 PM UTC· resolved May 13, 2026, 11:23 AM UTC
- monitoring May 12, 2026, 03:34 PM UTC
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
- resolved May 13, 2026, 11:23 AM UTC
Migration has been completed and Ronin network is available again.
Minor May 3, 2026 Polygon Node RPC: delayed block sync 3h 50m Node RPC
Started May 03, 2026, 07:02 PM UTC· resolved May 03, 2026, 10:53 PM UTC
- investigating May 03, 2026, 07:02 PM UTC
Our Polygon Node RPC is lagging behind the chain head. The team is investigating and we'll post an update shortly.
- monitoring May 03, 2026, 07:49 PM UTC
The Polygon Node RPC is back in sync with the chain head. We're continuing to monitor.
- resolved May 03, 2026, 10:53 PM UTC
This incident has been resolved.
Minor April 30, 2026 Berachain Mainnet and Unichain Sepolia - Monitoring Lag 29m
Started Apr 30, 2026, 09:20 AM UTC· resolved Apr 30, 2026, 09:49 AM UTC
- resolved Apr 30, 2026, 01:25 PM UTC
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.
Notice April 29, 2026 Polygon Node RPC Degraded Performance 2h
Started Apr 29, 2026, 02:30 AM UTC· resolved Apr 29, 2026, 04:30 AM UTC
- resolved Apr 29, 2026, 03:16 PM UTC
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.
Major April 28, 2026 Simulator issue 28m Simulator, Simulator
Started Apr 28, 2026, 09:48 AM UTC· resolved Apr 28, 2026, 10:16 AM UTC
- identified Apr 28, 2026, 09:48 AM UTC
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.
- identified Apr 28, 2026, 09:48 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Apr 28, 2026, 10:08 AM UTC
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.
- resolved Apr 28, 2026, 10:16 AM UTC
Alerts and Web 3 Actions delivery is fully recovered.
Minor April 20, 2026 Base Sepolia outage (affecting Node RPC, Virtual Testnets, Monitoring, Simulations) 2h 2m Virtual Testnet, Explorer, Simulator, Alerts and 4 more
Started Apr 20, 2026, 07:05 PM UTC· resolved Apr 20, 2026, 09:07 PM UTC
- identified Apr 20, 2026, 07:05 PM UTC
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.
- identified Apr 20, 2026, 08:30 PM UTC
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.
- monitoring Apr 20, 2026, 09:01 PM UTC
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.
- resolved Apr 20, 2026, 09:07 PM UTC
This incident has been resolved.
Major April 13, 2026 Sei Pacific-1 network wide issue 18m Virtual Testnet, Explorer, Simulator, Alerts and 3 more
Started Apr 13, 2026, 09:14 AM UTC· resolved Apr 13, 2026, 09:33 AM UTC
- monitoring Apr 13, 2026, 09:14 AM UTC
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.
- resolved Apr 13, 2026, 09:33 AM UTC
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.
Minor April 9, 2026 Polygon Node Lag 2h 28m Virtual Testnet, Virtual Testnet, Explorer, Explorer and 8 more
Started Apr 09, 2026, 07:50 PM UTC· resolved Apr 09, 2026, 10:18 PM UTC
- investigating Apr 09, 2026, 07:50 PM UTC
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.
- identified Apr 09, 2026, 08:43 PM UTC
Team has identified the issue on Polygon Mainnet with lag dropping. Polygon Amoy lag continues to rise, and the team is continuing the investigation.
- monitoring Apr 09, 2026, 09:23 PM UTC
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.
- resolved Apr 09, 2026, 10:18 PM UTC
This incident has been resolved.
Minor April 2, 2026 Taiko Mainnet lag 7m Virtual Testnet, Explorer, Simulator, Alerts and 4 more
Started Apr 02, 2026, 06:58 PM UTC· resolved Apr 02, 2026, 07:06 PM UTC
- identified Apr 02, 2026, 06:58 PM UTC
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.
- monitoring Apr 02, 2026, 07:01 PM UTC
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.
- resolved Apr 02, 2026, 07:06 PM UTC
Explorer and Monitoring (Alerts and Web3 Actions) have been fully restored. All components are now operating normally and the incident has been resolved.
Minor March 25, 2026 Network-wide issue on Sonic chain 4d 1h Virtual Testnet, Explorer, Simulator, Alerts and 4 more
Started Mar 25, 2026, 02:29 PM UTC· resolved Mar 29, 2026, 03:57 PM UTC
- identified Mar 25, 2026, 02:29 PM UTC
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.
- resolved Mar 29, 2026, 03:57 PM UTC
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.
Major March 5, 2026 Degraded RPC Performance and Platform functionalities Across Multiple Networks 2h
Started Mar 05, 2026, 12:30 PM UTC· resolved Mar 05, 2026, 02:30 PM UTC
- resolved Mar 05, 2026, 01:36 PM UTC
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.
Minor January 31, 2026 Web3 actions with block events delayed 1h 49m
Started Jan 31, 2026, 08:28 PM UTC· resolved Jan 31, 2026, 10:18 PM UTC
- investigating Jan 31, 2026, 08:28 PM UTC
We are experiencing delays with Web3 Action executions triggered by block events across all supported networks. Our team is actively investigating and working on a fix.
- monitoring Jan 31, 2026, 09:59 PM UTC
A fix has been implemented and we are seeing constant drop in delays of Web3 Action executions triggered by block events.
- resolved Jan 31, 2026, 10:18 PM UTC
The system has stabilized and all services have returned to normal operation.
Minor January 30, 2026 Web3 actions on block events delayed on all supported networks 3h 27m
Started Jan 30, 2026, 07:03 PM UTC· resolved Jan 30, 2026, 10:30 PM UTC
- identified Jan 30, 2026, 07:03 PM UTC
We are currently experiencing delays in Web3 Action executions triggered by block events across all supported networks. Our team is actively investigating the issue and working to resolve it as quickly as possible.
- monitoring Jan 30, 2026, 08:32 PM UTC
We’ve implemented a fix and are seeing the delays gradually decrease. Full recovery is expected in approximately 1.5 hours.
- resolved Jan 30, 2026, 10:30 PM UTC
The system has stabilized and all services are back to normal.
Notice January 27, 2026 WebSocket Connectivity Issues 9h 47m
Started Jan 27, 2026, 01:23 PM UTC· resolved Jan 27, 2026, 11:11 PM UTC
- investigating Jan 27, 2026, 01:23 PM UTC
We are currently experiencing issues with WebSocket connections, which may cause connectivity problems with Virtual Testnets. Alerts and Web3 Actions are also impacted, and notifications are currently delayed by approximately 1 hour.
- identified Jan 27, 2026, 02:33 PM UTC
The issue has been identified and fix is being implemented.
- monitoring Jan 27, 2026, 05:06 PM UTC
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
- monitoring Jan 27, 2026, 08:55 PM UTC
Alerts have been fully returned to normal. Web3 Actions are still due to catch up and return to real time notifications.
- resolved Jan 27, 2026, 11:11 PM UTC
Web3 Actions have been returned to normal functioning and real time notifications.
Notice January 19, 2026 Issue with websocket connections in US-west region 15m
Started Jan 19, 2026, 02:00 PM UTC· resolved Jan 19, 2026, 02:15 PM UTC
- resolved Jan 19, 2026, 03:38 PM UTC
Between 14:00 and 14:15 UTC, we experienced issues with WebSocket connections in the US-West region, which caused connection attempts to be refused. The issue has been resolved, and all services are now operating normally. We are closely monitoring the system to ensure continued stability.