Is Bastrio down?
Possible problem
Bastrio may be having problems.
Its latest check failed 59 min ago: initialize returned HTTP 523. The check before passed. Two failed checks in a row count as an outage. Next check: not before 31 Oct 2026, 07:59 UTC.
Latest check
- Last check
- 59 min ago (31 Oct 2026, 01:51 UTC)
- Response time
- Not measured (typical 204 ms)
- Next check
- Not before 31 Oct 2026, 07:59 UTC
- 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 |
|---|---|---|---|
| 31 Oct 2026, 01:51 UTC | initialize returned HTTP 523 | 523 | 3.1 s |
| 30 Oct 2026, 12:00 UTC | Passed | 401 | 201 ms |
| 29 Oct 2026, 23:05 UTC | Passed | 401 | 189 ms |
| 29 Oct 2026, 09:33 UTC | Passed | 401 | 186 ms |
| 28 Oct 2026, 20:41 UTC | Passed | 401 | 248 ms |
| 28 Oct 2026, 07:33 UTC | Passed | 401 | 202 ms |
| 27 Oct 2026, 18:23 UTC | Passed | 401 | 341 ms |
| 27 Oct 2026, 05:10 UTC | Passed | 401 | 190 ms |
| 26 Oct 2026, 16:27 UTC | Passed | 401 | 204 ms |
| 26 Oct 2026, 03:38 UTC | Passed | 401 | 200 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.