Is Trigger.dev down in the US?
Checks passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Trigger.dev at Nov 7, 2026, 5:47 PM UTC.
Over the last 24 hours we completed 264 checks from Ashburn and San Jose and 264 answered cleanly, 100.00% availability.
Of the 2 other regions we check Trigger.dev from, all 2 read checks passing right now.
Email me the next time we see Trigger.dev go down
What our Ashburn and San Jose probes measured
Last checked Nov 7, 2026, 5:47 PM UTC.
Trigger.dev from Ashburn and San Jose over the last 30 days
Over the last 30 days, Trigger.dev answered our Ashburn probe in 840 ms on average, and 1 check in 20 took longer than 1,218 ms.
Over the last 30 days, Trigger.dev answered our San Jose probe in 930 ms on average, and 1 check in 20 took longer than 1,310 ms.
Ranked by average response time across the 4 cities we check Trigger.dev from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 578 ms and Tokyo slowest at 1,604 ms.
From Ashburn and San Jose we ran 1,302 checks of Trigger.dev in 6 days, and 1,302 answered cleanly: 100.00% availability.
Every one of those days was clean: not one failed check.
In Ashburn local time (EST), Trigger.dev was slowest around 5 AM, at 1,016 ms on average over the last 14 days, and quickest around 9 AM, at 629 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Sat, Nov 7 | 198 | 100.00% | 971 ms |
| Fri, Nov 6 | 252 | 100.00% | 958 ms |
| Thu, Nov 5 | 251 | 100.00% | 848 ms |
| Wed, Nov 4 | 251 | 100.00% | 778 ms |
| Tue, Nov 3 | 246 | 100.00% | 837 ms |
| Mon, Nov 2 | 104 | 100.00% | 944 ms |
Trigger.dev outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Trigger.dev outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Trigger.dev from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 117 checks |
| Tokyo | Checks passing | 100.00% of 69 checks |
Other countries we check Trigger.dev from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Trigger.dev's public endpoints. They are not user reports, and they are not Trigger.dev's own status page.
See Trigger.dev's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Trigger.dev has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter