Is Crub down?
Up
No, Crub is up.
It passed its latest check 1 h ago in 242 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 1 h ago (20 Oct 2026, 20:21 UTC)
- Response time
- 242 ms (typical 314 ms)
- Next check
- In about 9 h
- How often
- About every 10 hours over the last 7 days
Uptime
Last 24 hours100%3 checks
Last 7 days100%17 checks
Last 30 days100%24 checks
All checks passedSome failedAll failedNot checked
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 |
|---|---|---|---|
| 20 Oct 2026, 20:21 UTC | Passed | 401 | 242 ms |
| 20 Oct 2026, 10:50 UTC | Passed | 401 | 206 ms |
| 20 Oct 2026, 01:35 UTC | Passed | 401 | 500 ms |
| 19 Oct 2026, 16:31 UTC | Passed | 401 | 414 ms |
| 19 Oct 2026, 07:40 UTC | Passed | 401 | 370 ms |
| 18 Oct 2026, 23:04 UTC | Passed | 401 | 254 ms |
| 18 Oct 2026, 13:29 UTC | Passed | 401 | 285 ms |
| 18 Oct 2026, 03:13 UTC | Passed | 401 | 301 ms |
| 17 Oct 2026, 16:07 UTC | Passed | 401 | 324 ms |
| 17 Oct 2026, 04:55 UTC | Passed | 401 | 273 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.