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 23 min ago. Last stored result reached it in 38 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 55 ms | 0 |
| Mon 21 | 0 | 0.0 | 59 ms | 0 |
| Tue 00 | 0 | 0.0 | 95 ms | 0 |
| Tue 02 | 0 | 0.0 | 145 ms | 0 |
| Tue 04 | 0 | 0.0 | 95 ms | 0 |
| Tue 06 | 0 | 0.0 | 34 ms | 0 |
| Tue 08 | 0 | 0.0 | 77 ms | 0 |
| Tue 10 | 0 | 0.0 | 96 ms | 0 |
| Tue 12 | 0 | 0.0 | 58 ms | 0 |
| Tue 14 | 0 | 0.0 | 135 ms | 0 |
| Tue 17 | 0 | 0.0 | 102 ms | 0 |
| Tue 19 | 0 | 0.0 | 41 ms | 0 |
| Tue 21 | 0 | 0.0 | 32 ms | 0 |
| Wed 00 | 0 | 0.0 | 96 ms | 0 |
| Wed 02 | 0 | 0.0 | 39 ms | 0 |
| Wed 04 | 0 | 0.0 | 45 ms | 0 |
| Wed 06 | 0 | 0.0 | 24 ms | 0 |
| Wed 08 | 0 | 0.0 | 31 ms | 0 |
| Wed 11 | 0 | 0.0 | 75 ms | 0 |
| Wed 13 | 0 | 0.0 | 71 ms | 0 |
| Wed 15 | 0 | 0.0 | 89 ms | 0 |
| Wed 17 | 0 | 0.0 | 132 ms | 0 |
| Wed 19 | 0 | 0.0 | 46 ms | 0 |
| Wed 22 | 0 | 0.0 | 250 ms | 0 |
| Thu 00 | 0 | 0.0 | 33 ms | 0 |
| Thu 02 | 0 | 0.0 | 96 ms | 0 |
| Thu 04 | 0 | 0.0 | 33 ms | 0 |
| Thu 05 | 0 | 0.0 | 149 ms | 0 |
| Thu 07 | 0 | 0.0 | 78 ms | 0 |
| Thu 09 | 0 | 0.0 | 85 ms | 0 |
| Thu 11 | 0 | 0.0 | 75 ms | 0 |
| Thu 13 | 0 | 0.0 | 75 ms | 0 |
| Thu 15 | 0 | 0.0 | 59 ms | 0 |
| Thu 17 | 0 | 0.0 | 98 ms | 0 |
| Thu 19 | 0 | 0.0 | 30 ms | 0 |
| Thu 21 | 0 | 0.0 | 96 ms | 0 |
| Thu 23 | 0 | 0.0 | 47 ms | 0 |
| Fri 02 | 0 | 0.0 | 73 ms | 0 |
| Fri 04 | 0 | 0.0 | 53 ms | 0 |
| Fri 06 | 0 | 0.0 | 83 ms | 0 |
| Fri 08 | 0 | 0.0 | 91 ms | 0 |
| Fri 10 | 0 | 0.0 | 70 ms | 0 |
| Fri 11 | 0 | 0.0 | 23 ms | 0 |
| Fri 14 | 0 | 0.0 | 92 ms | 0 |
| Fri 16 | 0 | 0.0 | 112 ms | 0 |
| Fri 17 | 0 | 0.0 | 106 ms | 0 |
| Fri 18 | 0 | 0.0 | 100 ms | 0 |
| Fri 19 | 0 | 0.0 | 38 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 UserJot 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 UserJot goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send UserJot alerts to Slack, Discord or a webhook — free.
UserJot is listed in our AI category and checked at userjot.com. Collect feature requests on a feedback board, publish a public roadmap and changelog, and run live chat with an AI agent. Free plan, unlimited users.
UserJot publishes an official status page at status.userjot.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 77 ms average, 23–112 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public UserJot incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
77 ms on average over the last 24 hours (23–112 ms).
Yes, at https://status.userjot.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 UserJot here at once, the problem is on UserJot'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 UserJot. 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.