Is Tenderly down?
Last checked 4m agoNo incidents right now.
Tenderly is operational right now. Last checked 4m ago; the most recent incident resolved 2d ago.
Real-time Tenderly status, recent outages, and incident history — pulled directly from Tenderly's official status page at https://status.tenderly.co every 5 minutes. Pingoru tracks 833 Tenderly services and has captured 14 incidents in the last 90 days (97.42% uptime). Get email, Slack, Discord, or webhook alerts the moment Tenderly reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Virtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual Testnet
Timeline · 3 updates
- 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!
Latest: The issue has been fully resolved and all alerts have been backfilled. Apologies for the inconvenience!
-
-
Timeline · 2 updates
- 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.
Latest: Alert and Web3 Action processing across all networks is back to normal and the backlog has fully cleared.
-
- Virtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual Testnet
Timeline · 2 updates
- identified · Jun 05, 2026, 07:35 AM 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, 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 returns to normal.
- resolved · Jun 05, 2026, 08:01 AM UTC
This incident is now resolved. Processing of Alerts and Web3 Actions across all networks has returned to normal latency and the backlog has fully cleared. As noted during the incident, no Alerts or Web3 Actions were skipped, and all queued events have now been processed and delivered. Thank you for your patience.
Latest: This incident is now resolved. Processing of Alerts and Web3 Actions across all networks has returned to normal latency and the backlog has fully cleared. As noted during the incid…
-
- Virtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual TestnetVirtual Testnet
Timeline · 2 updates
- 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.
Latest: This incident has been resolved.
-
- Virtual TestnetExplorerSimulatorAlertsWeb3 ActionsDebuggerContract VerificationNode RPC
Timeline · 2 updates
- 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.
Latest: Migration has been completed and Ronin network is available again.
-
See the full Tenderly outage history
9 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Tenderly outage history →Or sign up free to get alerts when Tenderly breaks · 10 free monitors · No credit card
- Started Jun 11, 2026, 09:54 AM UTC · Resolved Jun 11, 2026, 11:33 AM UTC · 1h 38m
- Started Jun 05, 2026, 04:27 PM UTC · Resolved Jun 05, 2026, 05:40 PM UTC · 1h 13m
- Started Jun 05, 2026, 07:35 AM UTC · Resolved Jun 05, 2026, 08:01 AM UTC · 25m
- Node Infrastructure Degradation ResolvedStarted May 15, 2026, 08:33 PM UTC · Resolved May 15, 2026, 10:42 PM UTC · 2h 9m
- Started May 12, 2026, 03:34 PM UTC · Resolved May 13, 2026, 11:23 AM UTC · 19h 48m
- Polygon Node RPC: delayed block sync ResolvedStarted May 03, 2026, 07:02 PM UTC · Resolved May 03, 2026, 10:53 PM UTC · 3h 50m
- Started Apr 30, 2026, 01:25 PM UTC · Resolved Apr 30, 2026, 01:25 PM UTC · —
- Started Apr 29, 2026, 04:30 AM UTC · Resolved Apr 29, 2026, 04:30 AM UTC · —