Is WhyVault down?
Up
No, WhyVault is up.
It passed its latest check 3 h ago in 980 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 3 h ago (26 Oct 2026, 02:44 UTC)
- Response time
- 980 ms (typical 837 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 |
|---|---|---|---|
| 26 Oct 2026, 02:44 UTC | Passed | 401 | 980 ms |
| 25 Oct 2026, 15:12 UTC | Passed | 401 | 971 ms |
| 25 Oct 2026, 02:53 UTC | Passed | 401 | 767 ms |
| 24 Oct 2026, 16:01 UTC | Passed | 401 | 867 ms |
| 24 Oct 2026, 04:32 UTC | Passed | 401 | 871 ms |
| 23 Oct 2026, 17:19 UTC | Passed | 401 | 1.1 s |
| 23 Oct 2026, 07:08 UTC | Passed | 401 | 1.0 s |
| 22 Oct 2026, 21:02 UTC | Passed | 401 | 450 ms |
| 22 Oct 2026, 10:14 UTC | Passed | 401 | 445 ms |
| 22 Oct 2026, 00:22 UTC | Passed | 401 | 395 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.