User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Trigger.dev down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → trigger.dev—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 36 min ago. Last stored result reached it in 421 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 05 | 0 | 0.0 | 289 ms | 0 |
| Mon 07 | 0 | 0.0 | 374 ms | 0 |
| Mon 10 | 0 | 0.0 | 310 ms | 0 |
| Mon 12 | 0 | 0.0 | 339 ms | 0 |
| Mon 14 | 0 | 0.0 | 327 ms | 0 |
| Mon 16 | 0 | 0.0 | 419 ms | 0 |
| Mon 18 | 0 | 0.0 | 301 ms | 0 |
| Mon 20 | 0 | 0.0 | 288 ms | 0 |
| Mon 22 | 0 | 0.0 | 428 ms | 0 |
| Tue 00 | 0 | 0.0 | 381 ms | 0 |
| Tue 02 | 0 | 0.0 | 331 ms | 0 |
| Tue 05 | 0 | 0.0 | 563 ms | 0 |
| Tue 07 | 0 | 0.0 | 387 ms | 0 |
| Tue 09 | 0 | 0.0 | 389 ms | 0 |
| Tue 11 | 0 | 0.0 | 395 ms | 0 |
| Tue 13 | 0 | 0.0 | 299 ms | 0 |
| Tue 15 | 0 | 0.0 | 334 ms | 0 |
| Tue 18 | 0 | 0.0 | 358 ms | 0 |
| Tue 20 | 0 | 0.0 | 343 ms | 0 |
| Tue 22 | 0 | 0.0 | 338 ms | 0 |
| Wed 00 | 0 | 0.0 | 231 ms | 0 |
| Wed 03 | 0 | 0.0 | 365 ms | 0 |
| Wed 05 | 0 | 0.0 | 312 ms | 0 |
| Wed 07 | 0 | 0.0 | 265 ms | 0 |
| Wed 09 | 0 | 0.0 | 368 ms | 0 |
| Wed 12 | 0 | 0.0 | 331 ms | 0 |
| Wed 14 | 0 | 0.0 | 542 ms | 0 |
| Wed 16 | 0 | 0.0 | 359 ms | 0 |
| Wed 18 | 0 | 0.0 | 291 ms | 0 |
| Wed 20 | 0 | 0.0 | 671 ms | 0 |
| Wed 22 | 0 | 0.0 | 325 ms | 0 |
| Thu 01 | 0 | 0.0 | 269 ms | 0 |
| Thu 03 | 0 | 0.0 | 366 ms | 0 |
| Thu 05 | 0 | 0.0 | 370 ms | 0 |
| Thu 07 | 0 | 0.0 | 414 ms | 0 |
| Thu 09 | 0 | 0.0 | 292 ms | 0 |
| Thu 11 | 0 | 0.0 | 323 ms | 0 |
| Thu 13 | 0 | 0.0 | 441 ms | 0 |
| Thu 15 | 0 | 0.0 | 697 ms | 0 |
| Thu 17 | 0 | 0.0 | 415 ms | 0 |
| Thu 19 | 0 | 0.0 | 362 ms | 0 |
| Thu 21 | 0 | 0.0 | 260 ms | 0 |
| Thu 23 | 0 | 0.0 | 582 ms | 0 |
| Fri 01 | 0 | 0.0 | 453 ms | 0 |
| Fri 03 | 0 | 0.0 | 904 ms | 0 |
| Fri 05 | 0 | 0.0 | 479 ms | 0 |
| Fri 07 | 0 | 0.0 | 352 ms | 0 |
| Fri 08 | 0 | 0.0 | 421 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Trigger.dev badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Trigger.dev yet. Outages of 10 minutes or more get their own page here.
Having trouble with Trigger.dev?
One report per service every 10 minutes from this network. No account.
Follow Trigger.dev
Get an email when Trigger.dev goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Trigger.dev alerts to Slack, Discord or a webhook — free.
About Trigger.dev
Trigger.dev is listed in our AI category and checked at trigger.dev. Trigger.dev is the open source platform for durable AI agents and workflows in TypeScript. Long-running tasks with retries, queues, and LLM observability.
Trigger.dev publishes an official status page at status.trigger.dev; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 460 ms average, 260–904 ms range across 13 successful checks.
Questions
Is Trigger.dev down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Trigger.dev last down?
We have not recorded a public Trigger.dev incident since monitoring began 8 days ago.
What is Trigger.dev's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Trigger.dev respond?
460 ms on average over the last 24 hours (260–904 ms).
Does Trigger.dev have an official status page?
Yes, at https://status.trigger.dev.
Trigger.dev not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Trigger.dev here at once, the problem is on Trigger.dev's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Trigger.dev. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.