Where does this status come from?

From Trigger.dev's own status page API at https://status.trigger.dev. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Trigger.dev's words.

How can my agent or app check Trigger.dev status?

Fetch https://upbutler.com/status/trigger/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"trigger"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Trigger.dev's?

Add "trigger" to the dependencies of your UpButler workspace. When one of your monitors fails while Trigger.dev has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Trigger.dev down?

Right now

No. Trigger.dev is operational.

No incidents reported.

Read from status.trigger.dev 69 s ago · every 300s

For agents

proceed

Proceed.

GET upbutler.com/status/trigger/status.agent.json

MCP: upstream_status {"service":"trigger"}

Background jobs and long-running agent tasks.

What Trigger.dev reports

Operational

Taken as is from Trigger.dev's own status page API. Incident titles and component names below are theirs.

Open status.trigger.dev

UpButler's independent probe

There is no keyless endpoint of Trigger.dev that says anything useful, so UpButler does not probe it. To check your own Trigger.dev account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Trigger.dev components

12 operational

Global

APIOperational
DashboardOperational
OpenTelemetryOperational
DeploymentsOperational

US East · us-east-1

Task executionOperational
Scheduled tasksOperational

EU Central · eu-central-1

Task executionOperational
Scheduled tasksOperational

US West · us-west-2

Task executionOperational
Scheduled tasksOperational

SSO & Directory Sync

Single sign-on (SSO)Operational
Directory Sync (SCIM)Operational

Trigger.dev incidents, last 90 days

2 finished incidents seen since UpButler started tracking on 2026-10-10.

Started (UTC)	Incident	Impact	Lasted
2026-10-06 12:21	Some sensitive environment variables synced from Vercel were cleared	minor	2 h 49 min
2026-09-28 07:20	Run logs are being dropped	minor	30 min

Tell your outage from Trigger.dev's

Declare that your project depends on Trigger.dev. When one of your monitors fails while Trigger.dev has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - trigger

Ask before you retry

curl -s https://upbutler.com/status/trigger/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "trigger",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Trigger.dev down right now?: No. As of 2026-10-10 05:09 UTC, Trigger.dev is operational. This page reads the status again every 5 minutes.
Where does this status come from?: From Trigger.dev's own status page API at https://status.trigger.dev. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Trigger.dev's words.
How can my agent or app check Trigger.dev status?: Fetch https://upbutler.com/status/trigger/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"trigger"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Trigger.dev's?: Add "trigger" to the dependencies of your UpButler workspace. When one of your monitors fails while Trigger.dev has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in code, packages and workflows

UpButler is not affiliated with Trigger.dev. Status and incident text belong to Trigger.dev and are read from their public status source; the probe result is UpButler's own measurement.