Tenderly incident

Simulator issue

Major Resolved View vendor source →
Started
Apr 28, 2026, 09:48 AM UTC
Resolved
Apr 28, 2026, 10:16 AM UTC
Duration
28m
Detected by Pingoru
Apr 28, 2026, 09:48 AM UTC

Affected components

SimulatorSimulator

Update timeline

  1. identified Apr 28, 2026, 09:48 AM UTC

    We're investigating an issue where requests to the Simulator API with save: true, and dashboard flows that save a simulation, are currently returning errors for all networks. Ephemeral simulation runs (without save), and Node RPC simulation methods are not affected. We'll share an update as soon as we have more information.

  2. identified Apr 28, 2026, 09:48 AM UTC

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

  3. monitoring Apr 28, 2026, 10:08 AM UTC

    A fix has been implemented and we are monitoring the results. Alerts and Web 3 Actions delivery will also be delayed starting 10:13 UTC, current lag is ~16min we expect full recovery within 10-15min.

  4. resolved Apr 28, 2026, 10:16 AM UTC

    Alerts and Web 3 Actions delivery is fully recovered.

Looking to track Tenderly downtime and outages?

Pingoru polls Tenderly's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Tenderly reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Tenderly alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Tenderly for free

5 free monitors · No credit card required