Is djb2 hex, input discarded down?
Up
No, djb2 hex, input discarded is up.
It passed its latest check 2 h ago in 307 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 2 h ago (17 Oct 2026, 20:17 UTC)
- Response time
- 307 ms (typical 76 ms)
- Next check
- In about 7 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 |
|---|---|---|---|
| 17 Oct 2026, 20:17 UTC | Passed | 200 | 307 ms |
| 17 Oct 2026, 09:07 UTC | Passed | 200 | 565 ms |
| 16 Oct 2026, 22:38 UTC | Passed | 200 | 311 ms |
| 16 Oct 2026, 12:52 UTC | Passed | 200 | 47 ms |
| 16 Oct 2026, 03:05 UTC | Passed | 200 | 45 ms |
| 15 Oct 2026, 17:04 UTC | Passed | 200 | 367 ms |
| 15 Oct 2026, 07:10 UTC | Passed | 200 | 454 ms |
| 14 Oct 2026, 21:00 UTC | Passed | 200 | 52 ms |
| 14 Oct 2026, 11:03 UTC | Passed | 200 | 399 ms |
| 14 Oct 2026, 02:03 UTC | Passed | 200 | 39 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.