Is goodbotbad.bot down?
Up
No, goodbotbad.bot is up.
It passed its latest check 1 h ago in 365 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 1 h ago (5 Nov 2026, 11:18 UTC)
- Response time
- 365 ms (typical 565 ms)
- Next check
- In about 12 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, 11:18 UTC | Passed | 401 | 365 ms |
| 4 Nov 2026, 20:28 UTC | Passed | 401 | 688 ms |
| 4 Nov 2026, 05:32 UTC | Passed | 401 | 691 ms |
| 3 Nov 2026, 15:35 UTC | Passed | 401 | 753 ms |
| 3 Nov 2026, 01:21 UTC | Passed | 401 | 589 ms |
| 2 Nov 2026, 10:58 UTC | Passed | 401 | 346 ms |
| 1 Nov 2026, 23:25 UTC | Passed | 401 | 344 ms |
| 1 Nov 2026, 13:18 UTC | Passed | 401 | 357 ms |
| 1 Nov 2026, 00:26 UTC | Passed | 401 | 633 ms |
| 31 Oct 2026, 10:09 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.