Is Weavz down?
Up
No, Weavz is up.
It passed its latest check 2 h ago in 1.7 s, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 2 h ago (17 Oct 2026, 22:19 UTC)
- Response time
- 1.7 s (typical 2.0 s)
- Next check
- In about 7 h
- How often
- About every 10 hours over the last 7 days
Uptime
Last 24 hours100%3 checks
Last 7 days100%16 checks
Last 30 days100%16 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 |
|---|---|---|---|
| 17 Oct 2026, 22:19 UTC | Passed | 401 | 1.7 s |
| 17 Oct 2026, 12:12 UTC | Passed | 401 | 4.2 s |
| 17 Oct 2026, 02:00 UTC | Passed | 401 | 2.0 s |
| 16 Oct 2026, 16:16 UTC | Passed | 401 | 2.0 s |
| 16 Oct 2026, 05:32 UTC | Passed | 401 | 2.6 s |
| 15 Oct 2026, 19:15 UTC | Passed | 401 | 3.5 s |
| 15 Oct 2026, 10:05 UTC | Passed | 401 | 2.6 s |
| 15 Oct 2026, 00:26 UTC | Passed | 401 | 2.2 s |
| 14 Oct 2026, 14:40 UTC | Passed | 401 | 3.5 s |
| 14 Oct 2026, 05:12 UTC | Passed | 401 | 1.7 s |
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.