Is CIDv1 base32 prefix, value discarded down?
Up
No, CIDv1 base32 prefix, value discarded is up.
It passed its latest check 10 h ago in 41 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 10 h ago (17 Oct 2026, 09:32 UTC)
- Response time
- 41 ms (typical 58 ms)
- Next check
- Due now
- 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, 09:32 UTC | Passed | 200 | 41 ms |
| 16 Oct 2026, 23:33 UTC | Passed | 200 | 775 ms |
| 16 Oct 2026, 13:25 UTC | Passed | 200 | 70 ms |
| 16 Oct 2026, 02:50 UTC | Passed | 200 | 269 ms |
| 15 Oct 2026, 16:20 UTC | Passed | 200 | 62 ms |
| 15 Oct 2026, 07:05 UTC | Passed | 200 | 325 ms |
| 14 Oct 2026, 20:51 UTC | Passed | 200 | 45 ms |
| 14 Oct 2026, 11:36 UTC | Passed | 200 | 58 ms |
| 14 Oct 2026, 02:17 UTC | Passed | 200 | 48 ms |
| 13 Oct 2026, 17:29 UTC | Passed | 200 | 111 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.