Is CUID timestamp chunk, value discarded down?
Up
No, CUID timestamp chunk, value discarded is up.
It passed its latest check 2 h ago in 48 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 2 h ago (17 Oct 2026, 19:59 UTC)
- Response time
- 48 ms (typical 53 ms)
- Next check
- In about 8 h
- How often
- About every 9 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 9 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, 19:59 UTC | Passed | 200 | 48 ms |
| 17 Oct 2026, 09:13 UTC | Passed | 200 | 53 ms |
| 16 Oct 2026, 22:31 UTC | Passed | 200 | 37 ms |
| 16 Oct 2026, 12:17 UTC | Passed | 200 | 243 ms |
| 16 Oct 2026, 02:40 UTC | Passed | 200 | 303 ms |
| 15 Oct 2026, 16:31 UTC | Passed | 200 | 81 ms |
| 15 Oct 2026, 07:04 UTC | Passed | 200 | 300 ms |
| 14 Oct 2026, 21:36 UTC | Passed | 200 | 32 ms |
| 14 Oct 2026, 12:14 UTC | Passed | 200 | 91 ms |
| 14 Oct 2026, 02:54 UTC | Passed | 200 | 296 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 9 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.