Is conbot down?
Down
Yes, conbot is down.
It has failed every check since 26 Oct 2026, 03:12 UTC (15 days 14 h, 11 checks). Latest error: Connection failed (ENOTFOUND). It last passed on 25 Oct 2026, 15:01 UTC.
Latest check
- Last check
- 2 days ago (8 Nov 2026, 05:38 UTC)
- Response time
- Not measured (typical 746 ms)
- Next check
- In about 6 h
- How often
- About every 2 days over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 2 days over the last 7 days.
Outages in the last 30 days
1 outage, 15 days 14 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 26 Oct 2026, 03:12 UTC | Ongoing, 15 days 14 h so far | 11 | Timed out |
Times are when our checks ran, about every 2 days for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 8 Nov 2026, 05:38 UTC | Connection failed (ENOTFOUND) | - | - |
| 5 Nov 2026, 06:06 UTC | Connection failed (ENOTFOUND) | - | - |
| 3 Nov 2026, 21:18 UTC | Connection failed (ENOTFOUND) | - | - |
| 2 Nov 2026, 14:39 UTC | Timed out | - | - |
| 1 Nov 2026, 05:59 UTC | Connection failed (ENOTFOUND) | - | - |
| 30 Oct 2026, 23:45 UTC | Connection failed (ENOTFOUND) | - | - |
| 29 Oct 2026, 18:21 UTC | Timed out | - | - |
| 28 Oct 2026, 12:30 UTC | Connection failed (ENOTFOUND) | - | - |
| 27 Oct 2026, 04:14 UTC | Connection failed (ENOTFOUND) | - | - |
| 26 Oct 2026, 15:06 UTC | Connection failed (ENOTFOUND) | - | - |
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 2 days 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.