Is UseHourly down?
Up
No, UseHourly is up.
It passed its latest check 3 h ago in 1.1 s, and every check since we started checking it on 17 Oct 2026.
Latest check
- Last check
- 3 h ago (5 Nov 2026, 03:26 UTC)
- Response time
- 1.1 s (typical 1.5 s)
- Next check
- In about 11 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 |
|---|---|---|---|
| 5 Nov 2026, 03:26 UTC | Passed | 401 | 1.1 s |
| 4 Nov 2026, 12:41 UTC | Passed | 401 | 572 ms |
| 3 Nov 2026, 21:53 UTC | Passed | 401 | 1.1 s |
| 3 Nov 2026, 07:19 UTC | Passed | 401 | 637 ms |
| 2 Nov 2026, 16:54 UTC | Passed | 401 | 1.8 s |
| 2 Nov 2026, 04:00 UTC | Passed | 401 | 568 ms |
| 1 Nov 2026, 17:31 UTC | Passed | 401 | 1.6 s |
| 1 Nov 2026, 06:04 UTC | Passed | 401 | 774 ms |
| 31 Oct 2026, 16:36 UTC | Passed | 401 | 1.4 s |
| 31 Oct 2026, 02:31 UTC | Passed | 401 | 652 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.