Is UpFork down?
Up
No, UpFork is up.
It passed its latest check 8 h ago in 196 ms. It has passed every check since 13 Oct 2026, 04:51 UTC.
Latest check
- Last check
- 8 h ago (14 Oct 2026, 16:53 UTC)
- Response time
- 196 ms (typical 207 ms)
- Next check
- In about 55 min
- How often
- About every 9 hours over the last 7 days
Uptime
Last 24 hours100%2 checks
Last 7 days88.9%9 checks
Last 30 days88.9%9 checks
All checks passedSome failedAll failedNot checked
Uptime is the share of checks that passed. We checked it about every 9 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 |
|---|---|---|---|
| 14 Oct 2026, 16:53 UTC | Passed | 200 | 196 ms |
| 14 Oct 2026, 07:49 UTC | Passed | 200 | 207 ms |
| 13 Oct 2026, 22:26 UTC | Passed | 200 | 192 ms |
| 13 Oct 2026, 13:29 UTC | Passed | 200 | 308 ms |
| 13 Oct 2026, 04:51 UTC | Passed | 200 | 251 ms |
| 12 Oct 2026, 19:40 UTC | initialize returned HTTP 502 | 502 | 285 ms |
| 12 Oct 2026, 11:12 UTC | Passed | 200 | 240 ms |
| 12 Oct 2026, 02:06 UTC | Passed | 200 | 165 ms |
| 11 Oct 2026, 17:45 UTC | Passed | 200 | 312 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 9 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.