User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 178 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 05 | 0 | 0.0 | 320 ms | 0 |
| Tue 07 | 0 | 0.0 | 240 ms | 0 |
| Tue 09 | 0 | 0.0 | 227 ms | 0 |
| Tue 11 | 0 | 0.0 | 299 ms | 0 |
| Tue 13 | 0 | 0.0 | 338 ms | 0 |
| Tue 15 | 0 | 0.0 | 311 ms | 0 |
| Tue 18 | 0 | 0.0 | 323 ms | 0 |
| Tue 20 | 0 | 0.0 | 255 ms | 0 |
| Tue 22 | 0 | 0.0 | 316 ms | 0 |
| Wed 00 | 0 | 0.0 | 257 ms | 0 |
| Wed 03 | 0 | 0.0 | 388 ms | 0 |
| Wed 05 | 0 | 0.0 | 317 ms | 0 |
| Wed 07 | 0 | 0.0 | 311 ms | 0 |
| Wed 09 | 0 | 0.0 | 245 ms | 0 |
| Wed 10 | 0 | 0.0 | 204 ms | 0 |
| Wed 11 | 0 | 0.0 | 291 ms | 0 |
| Wed 13 | 0 | 0.0 | 214 ms | 0 |
| Wed 15 | 0 | 0.0 | 273 ms | 0 |
| Wed 17 | 0 | 0.0 | 344 ms | 0 |
| Wed 19 | 0 | 0.0 | 449 ms | 0 |
| Wed 22 | 0 | 0.0 | 399 ms | 0 |
| Thu 00 | 0 | 0.0 | 352 ms | 0 |
| Thu 02 | 0 | 0.0 | 436 ms | 0 |
| Thu 04 | 0 | 0.0 | 326 ms | 0 |
| Thu 06 | 0 | 0.0 | 303 ms | 0 |
| Thu 08 | 0 | 0.0 | 406 ms | 0 |
| Thu 10 | 0 | 0.0 | 260 ms | 0 |
| Thu 12 | 0 | 0.0 | 132 ms | 0 |
| Thu 14 | 0 | 0.0 | 348 ms | 0 |
| Thu 16 | 0 | 0.0 | 148 ms | 0 |
| Thu 19 | 0 | 0.0 | 384 ms | 0 |
| Thu 21 | 0 | 0.0 | 289 ms | 0 |
| Thu 23 | 0 | 0.0 | 217 ms | 0 |
| Fri 01 | 0 | 0.0 | 311 ms | 0 |
| Fri 03 | 0 | 0.0 | 231 ms | 0 |
| Fri 05 | 0 | 0.0 | 234 ms | 0 |
| Fri 07 | 0 | 0.0 | 272 ms | 0 |
| Fri 08 | 0 | 0.0 | 223 ms | 0 |
| Fri 10 | 0 | 0.0 | 316 ms | 0 |
| Fri 11 | 0 | 0.0 | 214 ms | 0 |
| Fri 13 | 0 | 0.0 | 372 ms | 0 |
| Fri 15 | 0 | 0.0 | 219 ms | 0 |
| Fri 17 | 0 | 0.0 | 293 ms | 0 |
| Fri 18 | 0 | 0.0 | 242 ms | 0 |
| Fri 20 | 0 | 0.0 | 225 ms | 0 |
| Fri 21 | 0 | 0.0 | 299 ms | 0 |
| Fri 23 | 0 | 0.0 | 295 ms | 0 |
| Sat 01 | 0 | 0.0 | 178 ms | 0 |
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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for TRACTIAN yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when TRACTIAN goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send TRACTIAN alerts to Slack, Discord or a webhook — free.
TRACTIAN is listed in our AI category and checked at tractian.com. Turn reactive maintenance into predictable operations through AI-powered hardware and software built to protect revenue, reduce costs, and mitigate risk.
TRACTIAN publishes an official status page at status.tractian.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 259 ms average, 158–400 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public TRACTIAN incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
259 ms on average over the last 24 hours (158–400 ms).
Yes, at https://status.tractian.com.
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 TRACTIAN here at once, the problem is on TRACTIAN'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 TRACTIAN. 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.