Is Ripplewatch down?
Up
No, Ripplewatch is up.
It passed its latest check 4 h ago in 413 ms, and every check since we started checking it on 21 Oct 2026.
Latest check
- Last check
- 4 h ago (7 Nov 2026, 07:26 UTC)
- Response time
- 413 ms (typical 442 ms)
- Next check
- In about 9 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, 07:26 UTC | Passed | 401 | 413 ms |
| 6 Nov 2026, 19:39 UTC | Passed | 401 | 340 ms |
| 6 Nov 2026, 09:19 UTC | Passed | 401 | 1.2 s |
| 5 Nov 2026, 20:07 UTC | Passed | 401 | 344 ms |
| 5 Nov 2026, 05:22 UTC | Passed | 401 | 831 ms |
| 4 Nov 2026, 14:33 UTC | Passed | 401 | 1.1 s |
| 4 Nov 2026, 00:03 UTC | Passed | 401 | 389 ms |
| 3 Nov 2026, 09:45 UTC | Passed | 401 | 853 ms |
| 2 Nov 2026, 19:10 UTC | Passed | 401 | 1.5 s |
| 2 Nov 2026, 05:45 UTC | Passed | 401 | 907 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.