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 min ago. Last stored result reached it in 381 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 09 | 0 | 0.0 | 296 ms | 0 |
| Wed 12 | 0 | 0.0 | 256 ms | 0 |
| Wed 14 | 0 | 0.0 | 231 ms | 0 |
| Wed 16 | 0 | 0.0 | 392 ms | 0 |
| Wed 18 | 0 | 0.0 | 223 ms | 0 |
| Wed 20 | 0 | 0.0 | 127 ms | 0 |
| Wed 22 | 0 | 0.0 | 139 ms | 0 |
| Thu 01 | 0 | 0.0 | 228 ms | 0 |
| Thu 02 | 0 | 0.0 | 310 ms | 0 |
| Thu 04 | 0 | 0.0 | 175 ms | 0 |
| Thu 06 | 0 | 0.0 | 200 ms | 0 |
| Thu 08 | 0 | 0.0 | 183 ms | 0 |
| Thu 10 | 0 | 0.0 | 203 ms | 0 |
| Thu 12 | 0 | 0.0 | 261 ms | 0 |
| Thu 14 | 0 | 0.0 | 188 ms | 0 |
| Thu 16 | 0 | 0.0 | 143 ms | 0 |
| Thu 19 | 0 | 0.0 | 233 ms | 0 |
| Thu 21 | 0 | 0.0 | 195 ms | 0 |
| Thu 23 | 0 | 0.0 | 202 ms | 0 |
| Fri 01 | 0 | 0.0 | 146 ms | 0 |
| Fri 03 | 0 | 0.0 | 200 ms | 0 |
| Fri 05 | 0 | 0.0 | 202 ms | 0 |
| Fri 07 | 0 | 0.0 | 361 ms | 0 |
| Fri 08 | 0 | 0.0 | 133 ms | 0 |
| Fri 10 | 0 | 0.0 | 205 ms | 0 |
| Fri 11 | 0 | 0.0 | 196 ms | 0 |
| Fri 13 | 0 | 0.0 | 121 ms | 0 |
| Fri 15 | 0 | 0.0 | 230 ms | 0 |
| Fri 17 | 0 | 0.0 | 250 ms | 0 |
| Fri 19 | 0 | 0.0 | 117 ms | 0 |
| Fri 20 | 0 | 0.0 | 237 ms | 0 |
| Fri 22 | 0 | 0.0 | 124 ms | 0 |
| Fri 23 | 0 | 0.0 | 173 ms | 0 |
| Sat 01 | 0 | 0.0 | 174 ms | 0 |
| Sat 03 | 0 | 0.0 | 123 ms | 0 |
| Sat 05 | 0 | 0.0 | 213 ms | 0 |
| Sat 07 | 0 | 0.0 | 138 ms | 0 |
| Sat 10 | 0 | 0.0 | 132 ms | 0 |
| Sat 12 | 0 | 0.0 | 257 ms | 0 |
| Sat 14 | 0 | 0.0 | 226 ms | 0 |
| Sat 17 | 0 | 0.0 | 187 ms | 0 |
| Sat 19 | 0 | 0.0 | 233 ms | 0 |
| Sat 21 | 0 | 0.0 | 157 ms | 0 |
| Sun 00 | 0 | 0.0 | 130 ms | 0 |
| Sun 02 | 0 | 0.0 | 113 ms | 0 |
| Sun 04 | 0 | 0.0 | 381 ms | 0 |
| Sun 06 | 0 | 0.0 | 196 ms | 0 |
| Sun 07 | 0 | 0.0 | 110 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 10 days of data so far, so the 90-day numbers fill in over time.
No outages on record for TRM Labs 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 TRM Labs goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
TRM Labs, at trmlabs.com, is one of the AI services we monitor. Uncover illicit activity and disrupt threats with TRM. Bring AI and all-source intelligence into every investigation.
TRM Labs publishes an official status page at status.trmlabs.com; 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 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 181 ms average, 78–381 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public TRM Labs incident since monitoring began 10 days ago.
From our own checks: 100% over 10 days of checks.
181 ms on average over the last 24 hours (78–381 ms).
Yes, at https://status.trmlabs.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 TRM Labs here at once, the problem is on TRM Labs'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 TRM Labs. 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.