Skip to main content
Trigger.dev

DNS in us-east-1 is degraded

Partial outage Lasted 37m · started · Trigger.dev's page

Level
confirmed
Worst impact
Partial outage
Regions
us, us-east-1
Down Index
34of 100

What to do

  • Check whether you use Trigger.dev in us, us-east-1. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 37m it lasted.

    Anything that failed between 2026-04-15 14:03 UTC and 2026-04-15 14:40 UTC may need a replay.
  • Subscribe to Trigger.dev's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=trigger-dev works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Trigger.dev 3

  1. update

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

    provider

  2. update

    This is a coredns issue. We have spread out the coredns pods onto more nodes and added more replicas. This wasn't the same issue as we have seen with previous DNS problems. We're determining why this happened still. We're monitoring the change as the error rate comes down.

    provider

  3. resolved

    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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-25546a6dc5

Is Trigger.dev still down?

No, this incident was resolved 2026-04-15 14:40 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.

How long did it last?

37m, from 2026-04-15 14:03 UTC to 2026-04-15 14:40 UTC, by the times Trigger.dev posted.

What was affected?

Trigger.dev named in us, us-east-1.

What caused it?

Trigger.dev hasn't published a root cause. If it does, it shows here.

Where does this come from?

Trigger.dev's official status page, https://status.trigger.dev, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.