Is Biurko down?
Down
Yes, Biurko is down.
It has failed every check since 22 Oct 2026, 02:04 UTC (19 days 3 h, 13 checks). Latest error: initialize returned HTTP 404. It last passed on 21 Oct 2026, 16:57 UTC.
Latest check
- Last check
- 8 min ago (10 Nov 2026, 05:13 UTC)
- Response time
- Not measured (typical 244 ms)
- Next check
- In about 3 days
- How often
- About every 3 days over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 3 days over the last 7 days.
Outages in the last 30 days
1 outage, 19 days 3 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 22 Oct 2026, 02:04 UTC | Ongoing, 19 days 3 h so far | 13 | initialize returned HTTP 404 |
Times are when our checks ran, about every 3 days for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 10 Nov 2026, 05:13 UTC | initialize returned HTTP 404 | 404 | 175 ms |
| 7 Nov 2026, 01:14 UTC | initialize returned HTTP 404 | 404 | 168 ms |
| 4 Nov 2026, 01:48 UTC | initialize returned HTTP 404 | 404 | 165 ms |
| 31 Oct 2026, 20:48 UTC | initialize returned HTTP 404 | 404 | 194 ms |
| 30 Oct 2026, 13:25 UTC | initialize returned HTTP 404 | 404 | 177 ms |
| 29 Oct 2026, 06:26 UTC | initialize returned HTTP 404 | 404 | 183 ms |
| 27 Oct 2026, 21:04 UTC | initialize returned HTTP 404 | 404 | 176 ms |
| 26 Oct 2026, 11:43 UTC | initialize returned HTTP 404 | 404 | 194 ms |
| 25 Oct 2026, 06:44 UTC | initialize returned HTTP 404 | 404 | 200 ms |
| 24 Oct 2026, 01:21 UTC | initialize returned HTTP 404 | 404 | 355 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 3 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.