Looking for an update now? Check the current status, or follow Tenderly for future changes.
97.3%of 37 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
100%
30
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
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.
Legacy Incident Archive
17 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Lag on Gnosis Chiado testnet
minorSource not attested
Last archived state: resolved
View archived record details
identified
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.
July 2026
Login and Registration Issues
Source not attested
Last archived state: resolved
View archived record details
investigating
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.
June 2026
Delayed Base RPC syncing following Base network-wide halt
minorSource not attested
Last archived state: resolved
View archived record details
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.
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.
Monitoring Lag - Alert and Action Notifications
minorSource not attested
Last archived state: resolved
View archived record details
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.
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.
investigating
We are continuing to investigate this issue.
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.
Monitoring Lag on Arbitrum Sepolia, Monad and Base
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Team has discovered the RC and has applied the fix. Monitoring as the lag decreases.
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.
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.
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.
Delayed processing on Alerts and Web3 Actions
minorSource not attested
Last archived state: resolved
View archived record details
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.
Delayed processing on Alerts and Web3 Actions
minorSource not attested
Last archived state: resolved
View archived record details
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...
May 2026
Node Infrastructure Degradation
criticalSource not attested
Last archived state: resolved
View archived record details
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...
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...
