Tenderly Outage History

Tenderly is up right now

Tenderly had 47 outages in the last 2 years totaling 102h 9m of downtime — averaging 1.9 incidents per month.

There were 47 Tenderly outages since January 21, 2025 totaling 102h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tenderly.co

Major September 15, 2025

No request are served on Base network

Detected by Pingoru
Sep 15, 2025, 06:49 AM UTC
Resolved
Sep 15, 2025, 06:49 AM UTC
Duration
18s
Timeline · 2 updates
  1. monitoring Sep 15, 2025, 06:49 AM UTC

    We want to inform you about an incident on our Base network where no requests were served between 05:53 and 06:22 CET. The eth_sendRawTransaction was not working until 07:15 CET.

  2. resolved Sep 15, 2025, 06:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 14, 2025

Issue with historical Polygon mainnet data

Detected by Pingoru
Sep 14, 2025, 02:20 PM UTC
Resolved
Sep 14, 2025, 03:29 PM UTC
Duration
1h 9m
Timeline · 3 updates
  1. investigating Sep 14, 2025, 02:20 PM UTC

    Users using Polygon Mainnet APIs will not be able to retrieve data after block 76440930. Head of the chain (latest 128 blocks) remain unaffected. We are actively working with Polygon team on resolving the issue.

  2. monitoring Sep 14, 2025, 03:22 PM UTC

    The issue has been identified and historical nodes are processing again. We will share new update once the problematic block range has been synced.

  3. resolved Sep 14, 2025, 03:29 PM UTC

    Incident has been resolved, nodes are in sync.

Read the full incident report →

Minor September 10, 2025

Polygon mainnet: Ongoing network-wide disruption affecting Bor and Erigon node clients

Detected by Pingoru
Sep 10, 2025, 06:12 AM UTC
Resolved
Sep 10, 2025, 07:19 AM UTC
Duration
1h 6m
Timeline · 3 updates
  1. identified Sep 10, 2025, 06:12 AM UTC

    We’re actively tracking this issue in coordination with updates from the Polygon Foundation. We’ll share further updates as progress is made. https://status.polygon.technology/incidents/c8nc05x3qvmg

  2. monitoring Sep 10, 2025, 06:42 AM UTC

    Our node clients are now back in sync. A backfill process has been started to recover the skipped blocks. ETA for backfill is ~15mins.

  3. resolved Sep 10, 2025, 07:19 AM UTC

    The skipped block range has been fully backfilled, and all nodes are operating in sync. Normal network functionality has been restored.

Read the full incident report →

Minor September 4, 2025

Incident on Base

Detected by Pingoru
Sep 04, 2025, 01:53 PM UTC
Resolved
Sep 04, 2025, 02:39 PM UTC
Duration
46m
Timeline · 3 updates
  1. investigating Sep 04, 2025, 01:53 PM UTC

    We had an incident on Base where we did not produce new blocks between 14:08 and 14:36 CET. This affected our Virtual Testnet, Explorer and Node RPC. After this lag started to drop for Node RPC and after 14:51 we had fully mitigated the lag. Explorer and Virtual Testnets are fully operational at 15:22. Users still may experience request latency for Node RPC based in what region they are located. As of now all requests are forwarded to us-west, so us-east and europe regions might experience latency.

  2. monitoring Sep 04, 2025, 01:53 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 04, 2025, 02:39 PM UTC

    Issues are fully mitigated.

Read the full incident report →

Minor August 9, 2025

Polygon - Lag on mainnet

Detected by Pingoru
Aug 09, 2025, 08:58 AM UTC
Resolved
Aug 09, 2025, 09:16 AM UTC
Duration
18m
Timeline · 4 updates
  1. investigating Aug 09, 2025, 08:58 AM UTC

    We are experiencing lag on Polygon mainnet RPC. Team is investigating the issue.

  2. identified Aug 09, 2025, 09:00 AM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Aug 09, 2025, 09:05 AM UTC

    Fix has been implemented and lag is dropping.

  4. resolved Aug 09, 2025, 09:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 9, 2025

Brief lag experienced on Polygon mainnet at 08:05 UTC

Detected by Pingoru
Aug 09, 2025, 08:47 AM UTC
Resolved
Aug 09, 2025, 08:47 AM UTC
Duration
Timeline · 1 update
  1. resolved Aug 09, 2025, 08:47 AM UTC

    We experienced a brief lag on polygon mainnet RPCs at 08:05 UTC this morning. The team was immediately informed by our alerting system and the lag was fully resolved at 08:25 UTC. Maximum lag was ~200 blocks.

Read the full incident report →

Minor August 6, 2025

Block Height Stalled - Berachain Bepolia

Detected by Pingoru
Aug 06, 2025, 06:03 PM UTC
Resolved
Aug 06, 2025, 07:37 PM UTC
Duration
1h 33m
Timeline · 2 updates
  1. investigating Aug 06, 2025, 06:03 PM UTC

    We are currently experiencing a halt on Berachain Bepolia, with the network stalled at block height 7,816,796. The explorer is also stalled at this height. Our engineering team is actively investigating the issue and working toward a resolution.

  2. resolved Aug 06, 2025, 07:37 PM UTC

    The incident has been resolved. All nodes are now in sync and serving the latest data

Read the full incident report →

Minor July 30, 2025

Issue on Polygon

Detected by Pingoru
Jul 30, 2025, 12:26 PM UTC
Resolved
Jul 30, 2025, 05:15 PM UTC
Duration
4h 48m
Timeline · 4 updates
  1. investigating Jul 30, 2025, 12:26 PM UTC

    Investigating - The Polygon mainnet is currently experiencing a network-wide stall at block height 74,592,247. This is affecting all network operations. Our team is actively working on a node upgrade to resolve this issue. We will provide updates as the situation progresses. Thank you for your patience during this time.

  2. identified Jul 30, 2025, 12:52 PM UTC

    Update - The Polygon mainnet remains stalled at block height 74,592,247. Important: The new Heimdall v0.2.16 upgrade has been found to cause issues with execution layer clients (Bor & Erigon). The upgrade is now PAUSED until further notice from the Matic Foundation. Please do not proceed with any node upgrades at this time. We will provide updates as soon as we receive guidance from the Matic Foundation.

  3. monitoring Jul 30, 2025, 04:39 PM UTC

    The issue has been fully mitigated, all nodes are now in sync and serving the latest data. We are continuing to monitor the results.

  4. resolved Jul 30, 2025, 05:15 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor July 30, 2025

Issues on Base(Explorer, Node, Alerts, Web3 Actions)

Detected by Pingoru
Jul 30, 2025, 08:49 AM UTC
Resolved
Jul 30, 2025, 09:52 AM UTC
Duration
1h 3m
Timeline · 2 updates
  1. monitoring Jul 30, 2025, 08:49 AM UTC

    The Base block explorer was briefly unavailable between 07:39 AM and 08:12 AM (UTC+2) on July 30, 2025. During this time: • The Explorer didn’t display any transactions, and it wasn’t possible to search for them. • Requests to fetch transaction receipts via the Node were also failing during this period. • As a result, some Alerts and Web3 Actions may have been skipped.

  2. resolved Jul 30, 2025, 09:52 AM UTC

    The issue has been resolved, and everything is now working normally. Any missed blocks have been backfilled. What happened: • Between 07:39 and 08:25 AM (UTC+2), some of our internal services were temporarily down. • From 07:10 to 10:15 AM (UTC+2), the Base explorer, transaction search, and receipt fetching from the node (EU region only) were also affected. All systems are now fully operational.

Read the full incident report →

Minor July 19, 2025

Polygon Issue

Detected by Pingoru
Jul 19, 2025, 07:49 AM UTC
Resolved
Jul 19, 2025, 10:46 AM UTC
Duration
2h 56m
Timeline · 2 updates
  1. monitoring Jul 19, 2025, 07:49 AM UTC

    We had a lag on Polygon network from 2025-07-19 06:20:00 to 2025-07-19 08:40:00. The lag has been fully mitigated. Backfilling of historical data is currently in progress, from 74135907 to 74137899 block, with an estimated completion time of approximately 3 hours.

  2. resolved Jul 19, 2025, 10:46 AM UTC

    The job backfilling of historical data has completed and Tenderly nodes are serving all block ranges for Polygon mainnet again.

Read the full incident report →

Major July 17, 2025

Issue on Base

Detected by Pingoru
Jul 17, 2025, 05:49 PM UTC
Resolved
Jul 17, 2025, 08:23 PM UTC
Duration
2h 34m
Timeline · 4 updates
  1. investigating Jul 17, 2025, 05:49 PM UTC

    Currently showcasing and loading transactions for Base is not possible. Monitoring (Alerts and Web 3 Actions) are also degraded. We are investigating the issue

  2. identified Jul 17, 2025, 06:02 PM UTC

    Team has identified the potential issue and is releasing a hotfix.

  3. monitoring Jul 17, 2025, 06:45 PM UTC

    We have deployed the fix and are now observing how the system is reacting. We are loading most of the transactions on the Base Explorer, but degradation may occur. Currently Monitoring system is catching up to the lag that has been accumulated due to the outage. We expected to be in sync in ~2h.

  4. resolved Jul 17, 2025, 08:23 PM UTC

    The incident has been resolved. And monitoring lag has been fully mitigated. All systems are functioning and back to normal.

Read the full incident report →

Minor July 10, 2025

Polygon - Network wide issues due to Heimdall v2 migration

Detected by Pingoru
Jul 10, 2025, 07:47 PM UTC
Resolved
Jul 11, 2025, 10:44 AM UTC
Duration
14h 57m
Timeline · 4 updates
  1. investigating Jul 10, 2025, 07:47 PM UTC

    Network wide incident has been identified on Polygon mainnet

  2. identified Jul 11, 2025, 08:26 AM UTC

    Team is still actively working on stabilising Polygon mainnet, lag was observed on Polygon RPCs on couple of occasions 23:30-01:20 CEST and 4:55 - 9:50 CEST. To mitigate the lag the unprocessed blocks are skipped and the backfilling process is started.

  3. monitoring Jul 11, 2025, 09:42 AM UTC

    The lag has been fully mitigated and all nodes are now in sync. Backfilling of historical data is currently in progress, with an estimated completion time of approximately 2 hours.

  4. resolved Jul 11, 2025, 10:44 AM UTC

    The job backfilling of historical data has completed and Tenderly nodes are serving all block ranges for Polygon mainnet again.

Read the full incident report →

Minor June 27, 2025

Issues with creating Virtual Testnets for networks Sophon, Sophon Testnet, Lens, ZkSync Era and Zksync Era Sepolia

Detected by Pingoru
Jun 27, 2025, 03:21 PM UTC
Resolved
Jun 28, 2025, 10:15 AM UTC
Duration
18h 54m
Timeline · 3 updates
  1. identified Jun 27, 2025, 03:21 PM UTC

    We're currently experiencing issues with creating Virtual Testnets for networks Sophon, Sophon Testnet, Lens, ZkSync Era and Zksync Era Sepolia. The team is working on it and we'll post update as soon as possible.

  2. monitoring Jun 27, 2025, 06:04 PM UTC

    The team improved the situation but Virtual Testnet creation for the listed networks is still unstable - issues during Virtual Testnet creation are still possible. The team will continue working on this in order to fix the issue fully. We'll keep you posted!

  3. resolved Jun 28, 2025, 10:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 12, 2025

Web3 Actions & Alerts lag

Detected by Pingoru
Jun 12, 2025, 07:07 PM UTC
Resolved
Jun 12, 2025, 05:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Jun 12, 2025, 07:07 PM UTC

    On June 12th since around 17:50 UTC Web 3 Actions and Alerts monitoring performance has been degraded. Incident was mitigated at around ~19:00 UTC.

Read the full incident report →

Major June 12, 2025

Issue with Ethereum Mainnet Virtual Testnets

Detected by Pingoru
Jun 12, 2025, 08:10 AM UTC
Resolved
Jun 12, 2025, 01:21 PM UTC
Duration
5h 11m
Timeline · 3 updates
  1. investigating Jun 12, 2025, 08:10 AM UTC

    We noticed increased number of timeouts on mainnet vNet RPCs. The team is investigating the RC.

  2. monitoring Jun 12, 2025, 12:56 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 12, 2025, 01:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 10, 2025

Hiccup on Node wss connections

Detected by Pingoru
Jun 10, 2025, 05:11 PM UTC
Resolved
Jun 10, 2025, 05:11 PM UTC
Duration
Timeline · 1 update
  1. resolved Jun 10, 2025, 05:11 PM UTC

    We experienced small downtime on all Node WSS connections on 10th of June at 15:02 UTC. Only US regions were affected - connections were dropped and new ones couldn’t established. US-east was down for ~4min and US-west for ~8min.

Read the full incident report →

Major May 26, 2025

Alert and web3 action monitoring delays on all networks

Detected by Pingoru
May 26, 2025, 02:02 PM UTC
Resolved
May 27, 2025, 12:00 PM UTC
Duration
21h 57m
Timeline · 4 updates
  1. identified May 26, 2025, 02:02 PM UTC

    We're experiencing alert and web3 actions delays on all networks. The team is currently working on the fix .

  2. identified May 26, 2025, 02:16 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified May 26, 2025, 06:07 PM UTC

    The delay issues have been resolved on all networks except BNB for now. The team will work on a fix for BNB and we’ll keep you posted on the progress.

  4. resolved May 27, 2025, 12:00 PM UTC

    As of approximately 6:00 PM UTC on May 26th, alerts and Web3 actions on BNB are no longer experiencing delays. To mitigate the issue, we had to skip processing blocks from the timeframe between 2:00 PM and 6:00 PM UTC on May 26th. As a result, any alerts that would have been triggered during that period were not processed. We appreciate your understanding and apologise for any inconvenience this may have caused.

Read the full incident report →

Major May 16, 2025

Ethereum Sepolia RPC experiencing issues

Detected by Pingoru
May 16, 2025, 01:43 PM UTC
Resolved
May 16, 2025, 07:14 PM UTC
Duration
5h 30m
Timeline · 3 updates
  1. identified May 16, 2025, 01:43 PM UTC

    We're having issues on Ethereum Sepolia RPC at the moment so you might experience increase in errors. The team is working on the fix.

  2. identified May 16, 2025, 07:12 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved May 16, 2025, 07:14 PM UTC

    The incident has been resolved and we are serving traffic trough Sepolia RPC again.

Read the full incident report →

Critical April 28, 2025

Base Node RPC issues

Detected by Pingoru
Apr 28, 2025, 09:29 AM UTC
Resolved
Apr 28, 2025, 09:06 PM UTC
Duration
11h 37m
Timeline · 4 updates
  1. investigating Apr 28, 2025, 09:29 AM UTC

    Node RPC for Base network is experiencing issues in all regions.

  2. investigating Apr 28, 2025, 12:35 PM UTC

    Base Node RPC is in sync and working but rerouted to Euorpe since 12:37 CET

  3. monitoring Apr 28, 2025, 08:41 PM UTC

    Node RPC for Base in US east region is syncing and is no longer rerouted to EU. US west is in the process of syncing and should be in full sync in ~ 30 minutes.

  4. resolved Apr 28, 2025, 09:06 PM UTC

    Node RPC for Base in US west region is syncing and is no longer rerouted to EU. All regions have been recovered and the incident is resolved.

Read the full incident report →

Major April 8, 2025

Explorer is not working

Detected by Pingoru
Apr 08, 2025, 01:45 PM UTC
Resolved
Apr 08, 2025, 05:19 PM UTC
Duration
3h 34m
Timeline · 2 updates
  1. identified Apr 08, 2025, 01:45 PM UTC

    Explorers and project transaction listing are not working at the moment. The team is working on resolving the issue.

  2. resolved Apr 08, 2025, 05:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 3, 2025

Web3 Actions & Alerts Experiencing Delays

Detected by Pingoru
Apr 03, 2025, 05:22 PM UTC
Resolved
Apr 03, 2025, 05:22 PM UTC
Duration
Timeline · 3 updates
  1. identified Apr 03, 2025, 02:53 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Apr 03, 2025, 02:55 PM UTC

    Affected networks are: BNB, Base, Arbitrum and Polygon

  3. resolved Apr 03, 2025, 06:34 PM UTC

    This incident has been resolved on April 3rd at 5pm CEST.

Read the full incident report →

Major January 21, 2025

Base RPC lag

Detected by Pingoru
Jan 21, 2025, 08:48 AM UTC
Resolved
Jan 21, 2025, 12:56 PM UTC
Duration
4h 7m
Timeline · 3 updates
  1. identified Jan 21, 2025, 08:48 AM UTC

    Our Base RPCs are lagging and we're working on a fix.

  2. monitoring Jan 21, 2025, 10:58 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 21, 2025, 12:56 PM UTC

    This incident has been resolved.

Read the full incident report →