Trigger.dev incident

Some schedules have stopped...

Major Resolved View vendor source →

Trigger.dev experienced a major incident on January 21, 2026 affecting Current status by service (Trigger.dev cloud), lasting 19m. The incident has been resolved; the full update timeline is below.

Started
Jan 21, 2026, 10:56 AM UTC
Resolved
Jan 21, 2026, 11:15 AM UTC
Duration
19m
Detected by Pingoru
Jan 21, 2026, 10:56 AM UTC

Affected components

Current status by service (Trigger.dev cloud)

Update timeline

  1. investigating Jan 21, 2026, 10:56 AM UTC

    We had a brief outage earlier which affected a subset of schedules. We are working on a fix to get them going again.

  2. resolved Jan 21, 2026, 11:15 AM UTC

    All schedules have been fully restored.