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 264 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 118 ms | 0 |
| Mon 16 | 0 | 0.0 | 243 ms | 0 |
| Mon 18 | 0 | 0.0 | 110 ms | 0 |
| Mon 20 | 0 | 0.0 | 174 ms | 0 |
| Mon 22 | 0 | 0.0 | 192 ms | 0 |
| Tue 00 | 0 | 0.0 | 208 ms | 0 |
| Tue 02 | 0 | 0.0 | 214 ms | 0 |
| Tue 05 | 0 | 0.0 | 223 ms | 0 |
| Tue 07 | 0 | 0.0 | 237 ms | 0 |
| Tue 09 | 0 | 0.0 | 185 ms | 0 |
| Tue 11 | 0 | 0.0 | 173 ms | 0 |
| Tue 13 | 0 | 0.0 | 118 ms | 0 |
| Tue 15 | 0 | 0.0 | 151 ms | 0 |
| Tue 18 | 0 | 0.0 | 258 ms | 0 |
| Tue 20 | 0 | 0.0 | 263 ms | 0 |
| Tue 22 | 0 | 0.0 | 217 ms | 0 |
| Wed 00 | 0 | 0.0 | 216 ms | 0 |
| Wed 03 | 0 | 0.0 | 150 ms | 0 |
| Wed 05 | 0 | 0.0 | 203 ms | 0 |
| Wed 07 | 0 | 0.0 | 238 ms | 0 |
| Wed 09 | 0 | 0.0 | 167 ms | 0 |
| Wed 12 | 0 | 0.0 | 163 ms | 0 |
| Wed 14 | 0 | 0.0 | 289 ms | 0 |
| Wed 16 | 0 | 0.0 | 164 ms | 0 |
| Wed 18 | 0 | 0.0 | 191 ms | 0 |
| Wed 20 | 0 | 0.0 | 216 ms | 0 |
| Wed 22 | 0 | 0.0 | 181 ms | 0 |
| Thu 01 | 0 | 0.0 | 217 ms | 0 |
| Thu 03 | 0 | 0.0 | 215 ms | 0 |
| Thu 05 | 0 | 0.0 | 201 ms | 0 |
| Thu 07 | 0 | 0.0 | 279 ms | 0 |
| Thu 09 | 0 | 0.0 | 198 ms | 0 |
| Thu 11 | 0 | 0.0 | 222 ms | 0 |
| Thu 13 | 0 | 0.0 | 163 ms | 0 |
| Thu 15 | 0 | 0.0 | 224 ms | 0 |
| Thu 17 | 0 | 0.0 | 267 ms | 0 |
| Thu 19 | 0 | 0.0 | 221 ms | 0 |
| Thu 20 | 0 | 0.0 | 213 ms | 0 |
| Thu 22 | 0 | 0.0 | 146 ms | 0 |
| Fri 00 | 0 | 0.0 | 213 ms | 0 |
| Fri 02 | 0 | 0.0 | 194 ms | 0 |
| Fri 04 | 0 | 0.0 | 282 ms | 0 |
| Fri 06 | 0 | 0.0 | 259 ms | 0 |
| Fri 08 | 0 | 0.0 | 218 ms | 0 |
| Fri 10 | 0 | 0.0 | 222 ms | 0 |
| Fri 12 | 0 | 0.0 | 192 ms | 0 |
| Fri 14 | 0 | 0.0 | 224 ms | 0 |
| Fri 16 | 0 | 0.0 | 264 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Transfix 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 Transfix goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Transfix alerts to Slack, Discord or a webhook — free.
We track Transfix (transfix.io) as part of the AI group. Transfix pairs an AI freight TMS with custom cost models so brokers, 3PLs, and carriers price freight in seconds, win more loads, and grow margins.
Transfix publishes an official status page at status.transfix.io; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 221 ms average, 146–282 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Transfix incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
221 ms on average over the last 24 hours (146–282 ms).
Yes, at https://status.transfix.io.
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 Transfix here at once, the problem is on Transfix'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 Transfix. 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.