Tenderly incident
Monitoring Lag - Alert and Action Notifications
Tenderly experienced a minor incident on June 25, 2026 affecting Alerts and Alerts and 1 more component, lasting 1h 52m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.