Skip to content
PulseWatchOUTAGE.INTEL
Trigger.dev logo

Other

Is Trigger.dev down right now?

NormalOfficial status last polled Oct 6, 2026 20:48 UTCtrigger.devOfficial status page

Are you on the Trigger.dev team and see something inaccurate? Report it to us. We respond within one business day.

Is Trigger.dev down right now?

No. Trigger.dev has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 6, 2026 21:49 UTC

Normal

Trigger.dev is operating normally

As of Oct 6, 2026 21:49 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Oct 6, 2026 20:41 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Trigger.dev.

3

Incident days

27

No recorded incident

8h 56m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Trigger.dev. Hover a day for detail.

Sep 7Sep 12Sep 17Sep 22Sep 27Oct 201234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

3

Days with incidents

1 incident

Busiest day

8h 56m

Recorded duration

Report volume

0 reports in last 24H

09:45 PM01:15 AM04:45 AM08:15 AM11:45 AM03:15 PM06:45 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Trigger.dev: vendor-reported incident on October 6 (tracked 4h 25m)

Oct 6, 04:15 PM → Oct 6, 08:41 PM · 4h 25m · medium

Trigger.dev reported an incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked this incident for 4h 25m, closing it on 2026-10-06T20:41:45.826Z.

Duration
4h 25m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, therefore it cannot describe what users experienced. The incident is known from Trigger.dev's own status page.

Incident timeline

  1. Oct 6, 04:15 PM

    The vendor reported an incident on its own status page; PulseWatch began tracking it

  2. Oct 6, 04:17 PM

    Status updated: possible issue

  3. Oct 6, 08:41 PM

    PulseWatch closed the incident

Official updates

  1. Oct 6, 04:15 PM

    Trigger.dev reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Detected by PulseWatch

30-day uptime

98.8%

90-day uptime

99.59%

Calculated from Trigger.dev's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedMedium

Trigger.dev: the vendor reports degraded performance on Deployments on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/6/2026, 4:15:51 PM · 4h 25m

04:15 PM08:41 PM
Detection10/6/2026, 4:15:51 PM · 5h ago

Detected — medium severity

Trigger.dev: the vendor reports degraded performance on Deployments on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedHigh

Trigger.dev: the vendor reports a major outage on Single sign-on (SSO), Directory Sync (SCIM) on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/3/2026, 7:14:36 PM · 2h 14m

07:14 PM09:29 PM
Detection10/3/2026, 7:14:36 PM · 3d ago

Detected — high severity

Trigger.dev: the vendor reports a major outage on Single sign-on (SSO), Directory Sync (SCIM) on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedHigh

Trigger.dev: the vendor reports a major outage on Single sign-on (SSO), Directory Sync (SCIM) on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/29/2026, 2:44:40 PM · 2h 14m

02:44 PM04:59 PM
Detection9/29/2026, 2:44:40 PM · 7d ago

Detected — high severity

Trigger.dev: the vendor reports a major outage on Single sign-on (SSO), Directory Sync (SCIM) on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Trigger.dev enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Official status page polled; no gradeable history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

trigger.dev