Is Rattlewatch down?
Up
No, Rattlewatch is up.
It passed its latest check 2 h ago in 497 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 2 h ago (15 Oct 2026, 01:43 UTC)
- Response time
- 497 ms (typical 512 ms)
- Next check
- In about 8 h
- How often
- About every 10 hours over the last 7 days
Uptime
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 |
|---|---|---|---|
| 15 Oct 2026, 01:43 UTC | Passed | 200 | 497 ms |
| 14 Oct 2026, 16:02 UTC | Passed | 200 | 512 ms |
| 14 Oct 2026, 06:03 UTC | Passed | 200 | 553 ms |
| 13 Oct 2026, 20:22 UTC | Passed | 200 | 536 ms |
| 13 Oct 2026, 10:27 UTC | Passed | 200 | 743 ms |
| 13 Oct 2026, 00:47 UTC | Passed | 200 | 484 ms |
| 12 Oct 2026, 15:38 UTC | Passed | 200 | 484 ms |
| 12 Oct 2026, 06:26 UTC | Passed | 200 | 602 ms |
| 11 Oct 2026, 20:10 UTC | Passed | 200 | 491 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 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.