User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 18 min ago. Last stored result reached it in 1105 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 1285 ms | 0 |
| Mon 20 | 0 | 0.0 | 1199 ms | 0 |
| Mon 22 | 0 | 0.0 | 1031 ms | 0 |
| Tue 00 | 0 | 0.0 | 1183 ms | 0 |
| Tue 02 | 0 | 0.0 | 1182 ms | 0 |
| Tue 04 | 0 | 0.0 | 1154 ms | 0 |
| Tue 06 | 0 | 0.0 | 956 ms | 0 |
| Tue 08 | 0 | 0.0 | 1093 ms | 0 |
| Tue 10 | 0 | 0.0 | 1281 ms | 0 |
| Tue 13 | 0 | 0.0 | 1160 ms | 0 |
| Tue 15 | 0 | 0.0 | 1064 ms | 0 |
| Tue 17 | 0 | 0.0 | 1058 ms | 0 |
| Tue 19 | 0 | 0.0 | 1450 ms | 0 |
| Tue 22 | 0 | 0.0 | 1209 ms | 0 |
| Wed 00 | 0 | 0.0 | 1100 ms | 0 |
| Wed 02 | 0 | 0.0 | 1239 ms | 0 |
| Wed 03 | 0 | 0.0 | 1024 ms | 0 |
| Wed 05 | 0 | 0.0 | 1163 ms | 0 |
| Wed 07 | 0 | 0.0 | 1173 ms | 0 |
| Wed 09 | 0 | 0.0 | 1299 ms | 0 |
| Wed 12 | 0 | 0.0 | 1174 ms | 0 |
| Wed 14 | 0 | 0.0 | 1182 ms | 0 |
| Wed 16 | 0 | 0.0 | 1045 ms | 0 |
| Wed 18 | 0 | 0.0 | 1118 ms | 0 |
| Wed 20 | 0 | 0.0 | 1029 ms | 0 |
| Wed 22 | 0 | 0.0 | 1179 ms | 0 |
| Thu 01 | 0 | 0.0 | 1200 ms | 0 |
| Thu 03 | 0 | 0.0 | 993 ms | 0 |
| Thu 05 | 0 | 0.0 | 1113 ms | 0 |
| Thu 07 | 0 | 0.0 | 1250 ms | 0 |
| Thu 09 | 0 | 0.0 | 1181 ms | 0 |
| Thu 11 | 0 | 0.0 | 1063 ms | 0 |
| Thu 13 | 0 | 0.0 | 942 ms | 0 |
| Thu 15 | 0 | 0.0 | 1112 ms | 0 |
| Thu 17 | 0 | 0.0 | 983 ms | 0 |
| Thu 19 | 0 | 0.0 | 973 ms | 0 |
| Thu 21 | 0 | 0.0 | 1346 ms | 0 |
| Thu 23 | 0 | 0.0 | 1234 ms | 0 |
| Fri 01 | 0 | 0.0 | 1362 ms | 0 |
| Fri 03 | 0 | 0.0 | 923 ms | 0 |
| Fri 06 | 0 | 0.0 | 1139 ms | 0 |
| Fri 08 | 0 | 0.0 | — | 0 |
| Fri 10 | 0 | 0.0 | 1125 ms | 0 |
| Fri 12 | 0 | 0.0 | 987 ms | 0 |
| Fri 14 | 0 | 0.0 | 1044 ms | 0 |
| Fri 16 | 0 | 0.0 | 1339 ms | 0 |
| Fri 18 | 0 | 0.0 | 1128 ms | 0 |
| Fri 19 | 0 | 0.0 | 1105 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 Trackier 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 Trackier goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Trackier alerts to Slack, Discord or a webhook — free.
We track Trackier (trackier.com) as part of the Productivity group. Discover Trackier, a partner marketing platform built to manage affiliates, partnerships, attribution, and campaigns with automation, and real-time insights.
Trackier publishes an official status page at status.trackier.com; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
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: 1153 ms average, 923–1362 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Trackier incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1153 ms on average over the last 24 hours (923–1362 ms).
Yes, at https://status.trackier.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Trackier here at once, the problem is on Trackier'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 Trackier. 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.