Is IncidentVault down?
Up
No, IncidentVault is up.
It passed its latest check 6 h ago in 562 ms, and every check since we started checking it on 27 Oct 2026.
Latest check
- Last check
- 6 h ago (7 Nov 2026, 10:06 UTC)
- Response time
- 562 ms (typical 562 ms)
- Next check
- In about 8 h
- How often
- About every 14 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 14 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 |
|---|---|---|---|
| 7 Nov 2026, 10:06 UTC | Passed | 401 | 562 ms |
| 6 Nov 2026, 22:39 UTC | Passed | 401 | 563 ms |
| 6 Nov 2026, 12:02 UTC | Passed | 401 | 565 ms |
| 5 Nov 2026, 23:35 UTC | Passed | 401 | 406 ms |
| 5 Nov 2026, 08:15 UTC | Passed | 401 | 5.5 s |
| 4 Nov 2026, 17:40 UTC | Passed | 401 | 4.0 s |
| 4 Nov 2026, 02:39 UTC | Passed | 401 | 562 ms |
| 3 Nov 2026, 12:15 UTC | Passed | 401 | 563 ms |
| 2 Nov 2026, 22:06 UTC | Passed | 401 | 512 ms |
| 2 Nov 2026, 08:28 UTC | Passed | 401 | 604 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 14 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.