Is WaveGuard down?
Up
No, WaveGuard is up.
It passed its latest check 3 h ago in 4.8 s. It has passed every check since 27 Oct 2026, 04:27 UTC.
Latest check
- Last check
- 3 h ago (27 Oct 2026, 04:27 UTC)
- Response time
- 4.8 s (typical 4.4 s)
- Next check
- Not before 27 Oct 2026, 10:21 UTC
- How often
- About every 11 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 11 hours over the last 7 days.
Outages in the last 30 days
2 outages, 38 h 52 min of failed checks in total, the longest 19 h 47 min.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 15 Oct 2026, 15:28 UTC | 19 h 47 min | 2 | initialize returned HTTP 408 |
| 14 Oct 2026, 01:01 UTC | 19 h 5 min | 2 | Timed out |
Times are when our checks ran, about every 11 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 27 Oct 2026, 04:27 UTC | Passed | 200 | 4.8 s |
| 26 Oct 2026, 15:51 UTC | Timed out | - | - |
| 26 Oct 2026, 03:26 UTC | Passed | 200 | 2.9 s |
| 25 Oct 2026, 15:52 UTC | Passed | 200 | 5.0 s |
| 25 Oct 2026, 04:27 UTC | Passed | 200 | 2.5 s |
| 24 Oct 2026, 16:51 UTC | Passed | 200 | 2.8 s |
| 24 Oct 2026, 05:30 UTC | Timed out | - | - |
| 23 Oct 2026, 18:48 UTC | Passed | 200 | 5.6 s |
| 23 Oct 2026, 07:56 UTC | Passed | 200 | 5.6 s |
| 22 Oct 2026, 21:52 UTC | Passed | 200 | 3.0 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 11 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.