Is Tenderly down?
Last checked 1m agoNo incidents right now.
Tenderly is operational right now. Last checked 1m ago; the most recent incident resolved 15d 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 10 incidents in the last 90 days (97.48% 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-
Timeline · 2 updates
- 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
Latest: The issue has been resolved - user can now login to Tenderly Dashboard
-
- Virtual TestnetExplorerSimulatorAlertsWeb3 ActionsDebuggerContract VerificationNode RPC
Timeline · 3 updates
- 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.
Latest: Base nodes have fully recovered and all Base services are operating normally again.
-
- AlertsAlertsAlerts
Timeline · 5 updates
- 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.
Latest: 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.
-
- AlertsAlertsAlerts
Timeline · 3 updates
- 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.
Latest: All lag is gone and incident is resolved.
-
- 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!
-
See the full Tenderly outage history
5 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
- Login and Registration Issues ResolvedStarted Jul 16, 2026, 09:15 AM UTC · Resolved Jul 16, 2026, 11:23 AM UTC · 2h 8m
- Started Jun 25, 2026, 06:23 PM UTC · Resolved Jun 25, 2026, 07:00 PM UTC · 37m
- Started Jun 25, 2026, 03:28 PM UTC · Resolved Jun 25, 2026, 05:20 PM UTC · 1h 52m
- Started Jun 24, 2026, 11:08 AM UTC · Resolved Jun 24, 2026, 12:45 PM UTC · 1h 37m
- 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