Trigger.dev incident

Elevated dequeue times in u...

Minor Resolved View vendor source →
Started
Mar 01, 2026, 01:39 AM UTC
Resolved
Mar 01, 2026, 02:36 AM UTC
Duration
57m
Detected by Pingoru
Mar 01, 2026, 01:39 AM UTC

Affected components

Current status by service (Trigger.dev cloud)

Update timeline

  1. investigating Mar 01, 2026, 01:39 AM UTC

    Dequeues are slower than normal in us-east-1. Runs are still executing, but they are slower to start. We’re investigating the issue.

  2. resolved Mar 01, 2026, 02:36 AM UTC

    The issue is now resolved and dequeue times are back to normal. Mainly free-tier runs were affected. This was caused by a spike in the free-tier run volume.

Looking to track Trigger.dev downtime and outages?

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

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

5 free monitors · No credit card required