Trigger.dev experienced a minor incident on March 1, 2026 affecting Current status by service (Trigger.dev cloud), lasting 57m. The incident has been resolved; the full update timeline is below.
Affected components
Current status by service (Trigger.dev cloud)
Update timeline
- 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.
- 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.