Is LexLint: compliance lint for AI, scraping, and privacy law down?
Up
No, LexLint: compliance lint for AI, scraping, and privacy law is up.
It passed its latest check 7 h ago in 190 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 7 h ago (15 Oct 2026, 10:28 UTC)
- Response time
- 190 ms (typical 190 ms)
- Next check
- In about 2 h
- How often
- About every 10 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 10 hours over the last 7 days.
Outages in the last 30 days
No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 15 Oct 2026, 10:28 UTC | Passed | 401 | 190 ms |
| 15 Oct 2026, 00:03 UTC | Passed | 401 | 189 ms |
| 14 Oct 2026, 14:32 UTC | Passed | 401 | 213 ms |
| 14 Oct 2026, 05:20 UTC | Passed | 401 | 154 ms |
| 13 Oct 2026, 19:20 UTC | Passed | 401 | 168 ms |
| 13 Oct 2026, 09:40 UTC | Passed | 401 | 217 ms |
| 13 Oct 2026, 01:09 UTC | Passed | 401 | 221 ms |
| 12 Oct 2026, 16:14 UTC | Passed | 401 | 236 ms |
| 12 Oct 2026, 06:12 UTC | Passed | 401 | 183 ms |
| 11 Oct 2026, 20:12 UTC | Passed | 401 | 264 ms |
How we check
Up means the MCP handshake and the tool list worked, or the server asked for sign-in or payment.
Checks come from our server, about every 10 hours for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.
If you think a check is wrong, contact hello@toolvet.app. More on how we check and score.