Trigger.dev incident

DNS in us-east-1 is degraded

Minor Resolved View vendor source →
Started
Apr 15, 2026, 02:03 PM UTC
Resolved
Apr 15, 2026, 02:40 PM UTC
Duration
37m
Detected by Pingoru
Apr 15, 2026, 02:03 PM UTC

Affected components

Current status by service (Trigger.dev cloud)

Update timeline

  1. investigating Apr 15, 2026, 02:03 PM UTC

    This can impact HTTP requests including database queries. It seems to be impacting up to 5% of database queries for some users.

  2. resolved Apr 15, 2026, 02:40 PM UTC

    The issue is now resolved and DNS service is fully recovered. The degradation was caused by abnormal DNS load patterns, which caused intermittent issues with external resolvers. We've already applied some changes to harden our networking infrastructure and will monitor closely to confirm stability.

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