Is bsv.cx down?
Up
No, bsv.cx is up.
It passed its latest check 1 h ago in 414 ms. It has passed every check since 12 Oct 2026, 12:54 UTC.
Latest check
- Last check
- 1 h ago (17 Oct 2026, 21:43 UTC)
- Response time
- 414 ms (typical 430 ms)
- Next check
- In about 9 h
- How often
- About every 10 hours over the last 7 days
Uptime
Last 24 hours100%3 checks
Last 7 days93.8%16 checks
Last 30 days93.8%16 checks
All checks passedSome failedAll failedNot checked
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 |
|---|---|---|---|
| 17 Oct 2026, 21:43 UTC | Passed | 200 | 414 ms |
| 17 Oct 2026, 11:21 UTC | Passed | 200 | 659 ms |
| 17 Oct 2026, 00:56 UTC | Passed | 200 | 600 ms |
| 16 Oct 2026, 14:23 UTC | Passed | 200 | 437 ms |
| 16 Oct 2026, 04:42 UTC | Passed | 200 | 453 ms |
| 15 Oct 2026, 19:18 UTC | Passed | 200 | 441 ms |
| 15 Oct 2026, 09:57 UTC | Passed | 200 | 430 ms |
| 14 Oct 2026, 23:50 UTC | Passed | 200 | 388 ms |
| 14 Oct 2026, 14:06 UTC | Passed | 200 | 397 ms |
| 14 Oct 2026, 04:05 UTC | Passed | 200 | 610 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.