Is 1F4BC down?
Up
No, 1F4BC is up.
It passed its latest check 7 h ago in 1.3 s. It has passed every check since 12 Oct 2026, 13:46 UTC.
Latest check
- Last check
- 7 h ago (26 Oct 2026, 09:28 UTC)
- Response time
- 1.3 s (typical 1.2 s)
- Next check
- In about 3 h
- How often
- About every 11 hours over the last 7 days
Uptime
Last 24 hours100%2 checks
Last 7 days100%16 checks
Last 30 days97.2%36 checks
All checks passedSome failedAll failedNot checked
Uptime is the share of checks that passed. We checked it about every 11 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 |
|---|---|---|---|
| 26 Oct 2026, 09:28 UTC | Passed | 200 | 1.3 s |
| 25 Oct 2026, 21:28 UTC | Passed | 200 | 1.2 s |
| 25 Oct 2026, 09:28 UTC | Passed | 200 | 1.3 s |
| 24 Oct 2026, 22:23 UTC | Passed | 200 | 890 ms |
| 24 Oct 2026, 10:58 UTC | Passed | 200 | 1.1 s |
| 24 Oct 2026, 00:18 UTC | Passed | 200 | 1.0 s |
| 23 Oct 2026, 13:12 UTC | Passed | 200 | 906 ms |
| 23 Oct 2026, 02:08 UTC | Passed | 200 | 1.3 s |
| 22 Oct 2026, 15:30 UTC | Passed | 200 | 1.5 s |
| 22 Oct 2026, 05:29 UTC | Passed | 200 | 944 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 11 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.