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 41 min ago. Last stored result reached it in 105 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 173 ms | 0 |
| Nov 7 | 0 | 0.0 | 172 ms | 0 |
| Nov 7 | 0 | 0.0 | 54 ms | 0 |
| Nov 7 | 0 | 0.0 | 130 ms | 0 |
| Nov 8 | 0 | 0.0 | 108 ms | 0 |
| Nov 8 | 0 | 0.0 | 132 ms | 0 |
| Nov 8 | 0 | 0.0 | 98 ms | 0 |
| Nov 8 | 0 | 0.0 | 148 ms | 0 |
| Nov 9 | 0 | 0.0 | 153 ms | 0 |
| Nov 9 | 0 | 0.0 | 117 ms | 0 |
| Nov 9 | 0 | 0.0 | 122 ms | 0 |
| Nov 9 | 0 | 0.0 | 78 ms | 0 |
| Nov 10 | 0 | 0.0 | 81 ms | 0 |
| Nov 10 | 0 | 0.0 | 71 ms | 0 |
| Nov 10 | 0 | 0.0 | 92 ms | 0 |
| Nov 10 | 0 | 0.0 | 173 ms | 0 |
| Nov 11 | 0 | 0.0 | 133 ms | 0 |
| Nov 11 | 0 | 0.0 | 91 ms | 0 |
| Nov 11 | 0 | 0.0 | 37 ms | 0 |
| Nov 11 | 0 | 0.0 | 117 ms | 0 |
| Nov 12 | 0 | 0.0 | 118 ms | 0 |
| Nov 12 | 0 | 0.0 | 73 ms | 0 |
| Nov 12 | 0 | 0.0 | 101 ms | 0 |
| Nov 12 | 0 | 0.0 | 70 ms | 0 |
| Nov 13 | 0 | 0.0 | 81 ms | 0 |
| Nov 13 | 0 | 0.0 | 46 ms | 0 |
| Nov 13 | 0 | 0.0 | 78 ms | 0 |
| Nov 13 | 0 | 0.0 | 84 ms | 0 |
| Nov 14 | 0 | 0.0 | 105 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 7 days of data so far, so the 90-day numbers fill in over time.
One report per service every 10 minutes from this network. No account.
Get an email when Nicejob goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Nicejob alerts to Slack, Discord or a webhook — free.
We track Nicejob (get.nicejob.com) as part of the AI group. NiceJob's AI growth platform helps service businesses get more reviews, leads, and repeat customers. Start your free 14-day trial today.
Nicejob publishes an official status page at status.nicejob.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. We logged 1 public incident since monitoring began 7 days ago.
Response time over the last 24 hours: 77 ms average, 25–124 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
The most recent public incident we recorded started 2026-11-06 and lasted 2 days 12 h. 1 incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
77 ms on average over the last 24 hours (25–124 ms).
Yes, at https://status.nicejob.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 Nicejob here at once, the problem is on Nicejob'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 Nicejob. 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.