Is Byte Protocol down?
Up
No, Byte Protocol is up.
It passed its latest check 11 h ago in 490 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 11 h ago (3 Nov 2026, 04:11 UTC)
- Response time
- 490 ms (typical 550 ms)
- Next check
- In about 2 h
- How often
- About every 13 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 13 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 |
|---|---|---|---|
| 3 Nov 2026, 04:11 UTC | Passed | 200 | 490 ms |
| 2 Nov 2026, 13:55 UTC | Passed | 200 | 726 ms |
| 2 Nov 2026, 01:16 UTC | Passed | 200 | 544 ms |
| 1 Nov 2026, 15:40 UTC | Passed | 200 | 673 ms |
| 1 Nov 2026, 04:18 UTC | Passed | 200 | 553 ms |
| 31 Oct 2026, 13:42 UTC | Passed | 200 | 543 ms |
| 31 Oct 2026, 00:16 UTC | Passed | 200 | 547 ms |
| 30 Oct 2026, 11:05 UTC | Passed | 200 | 529 ms |
| 29 Oct 2026, 21:51 UTC | Passed | 200 | 548 ms |
| 29 Oct 2026, 08:50 UTC | Passed | 200 | 511 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 13 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.