- Level
- confirmed
- Worst impact
- Degraded
- Components
- OpenTelemetry
- Down Index
- 18of 100
What to do
Check whether you use Trigger.dev OpenTelemetry. 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 30m it lasted.
Anything that failed between 2026-09-28 07:20 UTC and 2026-09-28 07:50 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 2
- degraded
We're investigating run logs being dropped (from your run when you do console.log/logger.log). This doesn't impact run operation but does impact observability. This isn't due to a code or configuration change. More information soon.
provider
- resolved
Logs are being fully ingested again. The issue was with the internal workers in our shared OpenTelemetry service. They became unhealthy but weren't rolled. We're looking into why and how to prevent this from happening again.
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-add8f17d68
Is Trigger.dev still down?
No, this incident was resolved 2026-09-28 07:50 UTC. For Trigger.dev's live state, see https://down.guide/trigger-dev.
How long did it last?
30m, from 2026-09-28 07:20 UTC to 2026-09-28 07:50 UTC, by the times Trigger.dev posted.
What was affected?
Trigger.dev named OpenTelemetry.
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.