Critical incident

Tenderly: Node Infrastructure Degradation

May 15, 2026, 20:33 UTC
started
22:42 UTC
resolved
2 h 09 min
duration

Affected: Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet, Virtual Testnet, Explorer, Explorer, Explorer, Explorer, Explorer, Simulator, Simulator, Explorer, Explorer, Explorer, Explorer, Explorer, Explorer, Explorer, Explorer, Explorer, Simulator, Simulator, Simulator, Alerts, Alerts, Simulator, Simulator, Simulator, Simulator, Simulator, Simulator, Simulator, Simulator, Simulator, Alerts, Alerts, Alerts, Web3 Actions, Web3 Actions, Alerts, Alerts, Alerts, Alerts, Alerts, Alerts, Alerts, Alerts, Alerts, Web3 Actions, Web3 Actions, Web3 Actions, Web3 Actions, Web3 Actions, Web3 Actions, Web3 Actions, Web3 Actions, Web3 Actions, Web3 Actions, Web3 Actions, Web3 Actions, Node RPC, Node RPC, Node RPC, Node RPC, Node RPC, Node RPC, Node RPC, Node RPC, Node RPC, Node RPC, Node RPC, Node RPC, Node RPC

Current status of Tenderly: Operational — live Tenderly status

Timeline

  1. May 15, 2026, 20:33 UTC
    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, Tempo Moderato Testnet, Fraxtal, Monad, Monad Testnet, Sonic. Requests against these networks from our EU region would have errored or timed out. Networks with noticeable lag during the window: Ethereum, Base, Arbitrum One, BNB, Blast, Polygon, Avalanche, Sepolia, MegaETH, Gnosis, Ink, Soneium, Ronin. Impact is 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.
  2. May 15, 2026, 22:42 UTC
    resolved
    This incident has been resolved.

Updates as published by Tenderly (original).

Other services with incidents at the same time

More Tenderly incidents