User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Gaming
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 24 min ago. Last stored result reached it in 192 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 164 ms | 0 |
| Tue 05 | 0 | 0.0 | 277 ms | 0 |
| Tue 07 | 0 | 0.0 | 201 ms | 0 |
| Tue 10 | 0 | 0.0 | 171 ms | 0 |
| Tue 12 | 0 | 0.0 | 178 ms | 0 |
| Tue 14 | 0 | 0.0 | 904 ms | 0 |
| Tue 16 | 0 | 0.0 | 209 ms | 0 |
| Tue 18 | 0 | 0.0 | 259 ms | 0 |
| Tue 21 | 0 | 0.0 | 199 ms | 0 |
| Tue 23 | 0 | 0.0 | 209 ms | 0 |
| Wed 01 | 0 | 0.0 | 188 ms | 0 |
| Wed 03 | 0 | 0.0 | 171 ms | 0 |
| Wed 06 | 0 | 0.0 | 162 ms | 0 |
| Wed 08 | 0 | 0.0 | 180 ms | 0 |
| Wed 10 | 0 | 0.0 | 178 ms | 0 |
| Wed 12 | 0 | 0.0 | 392 ms | 0 |
| Wed 14 | 0 | 0.0 | 143 ms | 0 |
| Wed 15 | 0 | 0.0 | 166 ms | 0 |
| Wed 17 | 0 | 0.0 | 262 ms | 0 |
| Wed 19 | 0 | 0.0 | 237 ms | 0 |
| Wed 21 | 0 | 0.0 | 172 ms | 0 |
| Wed 23 | 0 | 0.0 | 206 ms | 0 |
| Thu 01 | 0 | 0.0 | 207 ms | 0 |
| Thu 03 | 0 | 0.0 | 189 ms | 0 |
| Thu 06 | 0 | 0.0 | 156 ms | 0 |
| Thu 08 | 0 | 0.0 | 305 ms | 0 |
| Thu 10 | 0 | 0.0 | 275 ms | 0 |
| Thu 12 | 0 | 0.0 | 169 ms | 0 |
| Thu 14 | 0 | 0.0 | 156 ms | 0 |
| Thu 16 | 0 | 0.0 | 214 ms | 0 |
| Thu 18 | 0 | 0.0 | 223 ms | 0 |
| Thu 20 | 0 | 0.0 | 190 ms | 0 |
| Thu 22 | 0 | 0.0 | 125 ms | 0 |
| Fri 00 | 0 | 0.0 | 473 ms | 0 |
| Fri 02 | 0 | 0.0 | 190 ms | 0 |
| Fri 04 | 0 | 0.0 | 403 ms | 0 |
| Fri 06 | 0 | 0.0 | 366 ms | 0 |
| Fri 08 | 0 | 0.0 | 214 ms | 0 |
| Fri 10 | 0 | 0.0 | 205 ms | 0 |
| Fri 12 | 0 | 0.0 | 244 ms | 0 |
| Fri 14 | 0 | 0.0 | 146 ms | 0 |
| Fri 16 | 0 | 0.0 | 152 ms | 0 |
| Fri 17 | 0 | 0.0 | 205 ms | 0 |
| Fri 19 | 0 | 0.0 | 221 ms | 0 |
| Fri 21 | 0 | 0.0 | 185 ms | 0 |
| Fri 23 | 0 | 0.0 | 202 ms | 0 |
| Sat 01 | 0 | 0.0 | 208 ms | 0 |
| Sat 03 | 0 | 0.0 | 192 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for TreeStats 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 TreeStats goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send TreeStats alerts to Slack, Discord or a webhook — free.
TreeStats, at treestats.net, is one of the Gaming services we monitor. TreeStats records ingame data from your characters using a Decal plugin and stores it for convenient out-of-game browsing. TreeStats lets you view your characters and allegiance chains and also provides rankings and tracks server population counts.
TreeStats publishes an official status page at status.treestats.net; when we can read it, its incident level is folded into the status shown here.
Common problems for gaming services: login and matchmaking failures, server disconnects, and store or download errors.
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: 221 ms average, 99–403 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public TreeStats incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
221 ms on average over the last 24 hours (99–403 ms).
Yes, at https://status.treestats.net.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For gaming services, watch for login and matchmaking failures, server disconnects, and store or download errors. If many people report TreeStats here at once, the problem is on TreeStats'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 TreeStats. 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.