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 1 hr ago. Last stored result reached it in 80 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 68 ms | 0 |
| Mon 22 | 0 | 0.0 | 109 ms | 0 |
| Tue 00 | 0 | 0.0 | 118 ms | 0 |
| Tue 02 | 0 | 0.0 | 96 ms | 0 |
| Tue 04 | 0 | 0.0 | 92 ms | 0 |
| Tue 06 | 0 | 0.0 | 49 ms | 0 |
| Tue 08 | 0 | 0.0 | 84 ms | 0 |
| Tue 10 | 0 | 0.0 | 116 ms | 0 |
| Tue 13 | 0 | 0.0 | 99 ms | 0 |
| Tue 15 | 0 | 0.0 | 137 ms | 0 |
| Tue 17 | 0 | 0.0 | 198 ms | 0 |
| Tue 19 | 0 | 0.0 | 156 ms | 0 |
| Tue 22 | 0 | 0.0 | 92 ms | 0 |
| Wed 00 | 0 | 0.0 | 44 ms | 0 |
| Wed 02 | 0 | 0.0 | 135 ms | 0 |
| Wed 04 | 0 | 0.0 | 82 ms | 0 |
| Wed 07 | 0 | 0.0 | 137 ms | 0 |
| Wed 09 | 0 | 0.0 | 82 ms | 0 |
| Wed 11 | 0 | 0.0 | 113 ms | 0 |
| Wed 13 | 0 | 0.0 | 205 ms | 0 |
| Wed 15 | 0 | 0.0 | 64 ms | 0 |
| Wed 17 | 0 | 0.0 | 33 ms | 0 |
| Wed 20 | 0 | 0.0 | 53 ms | 0 |
| Wed 22 | 0 | 0.0 | 149 ms | 0 |
| Thu 00 | 0 | 0.0 | 156 ms | 0 |
| Thu 02 | 0 | 0.0 | 48 ms | 0 |
| Thu 04 | 0 | 0.0 | 77 ms | 0 |
| Thu 06 | 0 | 0.0 | 119 ms | 0 |
| Thu 08 | 0 | 0.0 | 35 ms | 0 |
| Thu 10 | 0 | 0.0 | 139 ms | 0 |
| Thu 12 | 0 | 0.0 | 151 ms | 0 |
| Thu 14 | 0 | 0.0 | 103 ms | 0 |
| Thu 17 | 0 | 0.0 | 81 ms | 0 |
| Thu 19 | 0 | 0.0 | 358 ms | 0 |
| Thu 21 | 0 | 0.0 | 36 ms | 0 |
| Thu 23 | 0 | 0.0 | 57 ms | 0 |
| Fri 01 | 0 | 0.0 | 93 ms | 0 |
| Fri 03 | 0 | 0.0 | 67 ms | 0 |
| Fri 05 | 0 | 0.0 | 95 ms | 0 |
| Fri 07 | 0 | 0.0 | 41 ms | 0 |
| Fri 09 | 0 | 0.0 | 144 ms | 0 |
| Fri 11 | 0 | 0.0 | 50 ms | 0 |
| Fri 13 | 0 | 0.0 | 108 ms | 0 |
| Fri 15 | 0 | 0.0 | 146 ms | 0 |
| Fri 17 | 0 | 0.0 | 131 ms | 0 |
| Fri 18 | 0 | 0.0 | 58 ms | 0 |
| Fri 20 | 0 | 0.0 | 153 ms | 0 |
| Fri 22 | 0 | 0.0 | 101 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.
Riverside Court Scheduled Maintenance
Riverside Courts will be undergoing scheduled maintenance and will not be available during this time. Thank you for your patience.
Florida Court Scheduled Maintenance
Florida Courts will be undergoing scheduled maintenance on November 14th, 2026, starting from 01:30 EST and will run for approximately 3 hours. eFiling services may not be accessible at this time.
Kern County Weekly Maintenance
Kern County will be under going scheduled maintenance for an hour and will be unavailable for filing during that time. Thank you for your patience.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for InfoTrack US System 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 InfoTrack US System goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send InfoTrack US System alerts to Slack, Discord or a webhook — free.
InfoTrack US System is listed in our Productivity category and checked at infotrack.com. File, serve and track every case from one account, backed by people who know the courts. Free to sign up. No subscription. Works with Clio and MyCase.
InfoTrack US System publishes an official status page at status.infotrack.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 93 ms average, 10–166 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 InfoTrack US System incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
93 ms on average over the last 24 hours (10–166 ms).
Yes, at https://status.infotrack.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 InfoTrack US System here at once, the problem is on InfoTrack US System'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 InfoTrack US System. 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.