Is nlqdb — analytical memory for AI agents down?
Up
No, nlqdb — analytical memory for AI agents is up.
It passed its latest check 7 h ago in 580 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 7 h ago (19 Oct 2026, 08:53 UTC)
- Response time
- 580 ms (typical 425 ms)
- Next check
- In about 3 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 |
|---|---|---|---|
| 19 Oct 2026, 08:53 UTC | Passed | 401 | 580 ms |
| 19 Oct 2026, 00:35 UTC | Passed | 401 | 324 ms |
| 18 Oct 2026, 16:14 UTC | Passed | 401 | 458 ms |
| 18 Oct 2026, 05:18 UTC | Passed | 401 | 451 ms |
| 17 Oct 2026, 18:00 UTC | Passed | 401 | 403 ms |
| 17 Oct 2026, 07:35 UTC | Passed | 401 | 470 ms |
| 16 Oct 2026, 21:52 UTC | Passed | 401 | 290 ms |
| 16 Oct 2026, 12:03 UTC | Passed | 401 | 441 ms |
| 16 Oct 2026, 01:40 UTC | Passed | 401 | 278 ms |
| 15 Oct 2026, 15:43 UTC | Passed | 401 | 392 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.