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 2 hr ago. Last stored result reached it in 407 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 935 ms | 0 |
| Nov 7 | 0 | 0.0 | 500 ms | 0 |
| Nov 8 | 0 | 0.0 | 658 ms | 0 |
| Nov 8 | 0 | 0.0 | 572 ms | 0 |
| Nov 8 | 0 | 0.0 | 596 ms | 0 |
| Nov 8 | 0 | 0.0 | 515 ms | 0 |
| Nov 9 | 0 | 0.0 | 457 ms | 0 |
| Nov 9 | 0 | 0.0 | 493 ms | 0 |
| Nov 9 | 0 | 0.0 | 917 ms | 0 |
| Nov 9 | 0 | 0.0 | 570 ms | 0 |
| Nov 10 | 0 | 0.0 | 459 ms | 0 |
| Nov 10 | 0 | 0.0 | 500 ms | 0 |
| Nov 10 | 0 | 0.0 | 521 ms | 0 |
| Nov 10 | 0 | 0.0 | 517 ms | 0 |
| Nov 11 | 0 | 0.0 | 365 ms | 0 |
| Nov 11 | 0 | 0.0 | 431 ms | 0 |
| Nov 11 | 0 | 0.0 | 575 ms | 0 |
| Nov 11 | 0 | 0.0 | 354 ms | 0 |
| Nov 12 | 0 | 0.0 | 454 ms | 0 |
| Nov 12 | 0 | 0.0 | 778 ms | 0 |
| Nov 12 | 0 | 0.0 | 419 ms | 0 |
| Nov 12 | 0 | 0.0 | 599 ms | 0 |
| Nov 13 | 0 | 0.0 | 649 ms | 0 |
| Nov 13 | 0 | 0.0 | 529 ms | 0 |
| Nov 13 | 0 | 0.0 | 749 ms | 0 |
| Nov 13 | 0 | 0.0 | 613 ms | 0 |
| Nov 14 | 0 | 0.0 | 496 ms | 0 |
| Nov 14 | 0 | 0.0 | 713 ms | 0 |
| Nov 14 | 0 | 0.0 | 538 ms | 0 |
| Nov 14 | 0 | 0.0 | 429 ms | 0 |
| Nov 15 | 0 | 0.0 | 407 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for LegalOn 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 LegalOn goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track LegalOn (legalontech.com) as part of the AI group. LegalOn is legal AI for the full legal workday: review contracts, manage matters, and search every agreement in the platform or in Word. Trusted by 9K+ teams.
LegalOn publishes an official status page at status.legalontech.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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 506 ms average, 340–892 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public LegalOn incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
506 ms on average over the last 24 hours (340–892 ms).
Yes, at https://status.legalontech.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 LegalOn here at once, the problem is on LegalOn'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 LegalOn. 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.