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 59 min ago. Last stored result reached it in 218 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 241 ms | 0 |
| Mon 20 | 0 | 0.0 | 301 ms | 0 |
| Mon 23 | 0 | 0.0 | 142 ms | 0 |
| Tue 01 | 0 | 0.0 | 228 ms | 0 |
| Tue 03 | 0 | 0.0 | 123 ms | 0 |
| Tue 05 | 0 | 0.0 | 242 ms | 0 |
| Tue 07 | 0 | 0.0 | 261 ms | 0 |
| Tue 09 | 0 | 0.0 | 264 ms | 0 |
| Tue 11 | 0 | 0.0 | 228 ms | 0 |
| Tue 13 | 0 | 0.0 | 321 ms | 0 |
| Tue 16 | 0 | 0.0 | 266 ms | 0 |
| Tue 18 | 0 | 0.0 | 200 ms | 0 |
| Tue 20 | 0 | 0.0 | 268 ms | 0 |
| Tue 22 | 0 | 0.0 | 235 ms | 0 |
| Wed 01 | 0 | 0.0 | 329 ms | 0 |
| Wed 03 | 0 | 0.0 | 114 ms | 0 |
| Wed 05 | 0 | 0.0 | 242 ms | 0 |
| Wed 07 | 0 | 0.0 | 205 ms | 0 |
| Wed 10 | 0 | 0.0 | 232 ms | 0 |
| Wed 12 | 0 | 0.0 | 216 ms | 0 |
| Wed 14 | 0 | 0.0 | 232 ms | 0 |
| Wed 16 | 0 | 0.0 | 190 ms | 0 |
| Wed 18 | 0 | 0.0 | 145 ms | 0 |
| Wed 20 | 0 | 0.0 | 212 ms | 0 |
| Wed 23 | 0 | 0.0 | 258 ms | 0 |
| Thu 01 | 0 | 0.0 | 265 ms | 0 |
| Thu 03 | 0 | 0.0 | 279 ms | 0 |
| Thu 05 | 0 | 0.0 | 274 ms | 0 |
| Thu 07 | 0 | 0.0 | 120 ms | 0 |
| Thu 09 | 0 | 0.0 | 271 ms | 0 |
| Thu 11 | 0 | 0.0 | 232 ms | 0 |
| Thu 13 | 0 | 0.0 | 86 ms | 0 |
| Thu 15 | 0 | 0.0 | 268 ms | 0 |
| Thu 17 | 0 | 0.0 | 171 ms | 0 |
| Thu 19 | 0 | 0.0 | 132 ms | 0 |
| Thu 21 | 0 | 0.0 | 152 ms | 0 |
| Thu 23 | 0 | 0.0 | 249 ms | 0 |
| Fri 01 | 0 | 0.0 | 93 ms | 0 |
| Fri 04 | 0 | 0.0 | 239 ms | 0 |
| Fri 06 | 0 | 0.0 | 218 ms | 0 |
| Fri 08 | 0 | 0.0 | 257 ms | 0 |
| Fri 10 | 0 | 0.0 | 251 ms | 0 |
| Fri 12 | 0 | 0.0 | 229 ms | 0 |
| Fri 14 | 0 | 0.0 | 133 ms | 0 |
| Fri 16 | 0 | 0.0 | 228 ms | 0 |
| Fri 18 | 0 | 0.0 | 195 ms | 0 |
| Fri 19 | 0 | 0.0 | 286 ms | 0 |
| Fri 21 | 0 | 0.0 | 218 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 Honorlock 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 Honorlock goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Honorlock alerts to Slack, Discord or a webhook — free.
Honorlock, at honorlock.com, is one of the AI services we monitor. Secure online exams with online proctoring that combines live monitoring with AI to detect cell phones, block AI, lock the browser, and improve assessments.
Honorlock publishes an official status page at status.honorlock.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 216 ms average, 93–286 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Honorlock incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
216 ms on average over the last 24 hours (93–286 ms).
Yes, at https://status.honorlock.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 Honorlock here at once, the problem is on Honorlock'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 Honorlock. 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.