Is FetchRelay down?
Down
Yes, FetchRelay is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: initialize returned HTTP 404.
Latest check
- Last check
- 14 h ago (19 Oct 2026, 05:37 UTC)
- Response time
- Not measured
- Next check
- In about 13 h
- How often
- About every 27 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 27 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 |
|---|---|---|---|
| 19 Oct 2026, 05:37 UTC | initialize returned HTTP 404 | 404 | 212 ms |
| 18 Oct 2026, 05:07 UTC | initialize returned HTTP 404 | 404 | 111 ms |
| 17 Oct 2026, 02:16 UTC | initialize returned HTTP 404 | 404 | 130 ms |
| 16 Oct 2026, 00:02 UTC | initialize returned HTTP 404 | 404 | 92 ms |
| 14 Oct 2026, 18:57 UTC | initialize returned HTTP 404 | 404 | 90 ms |
| 13 Oct 2026, 13:07 UTC | initialize returned HTTP 404 | 404 | 128 ms |
| 12 Oct 2026, 10:46 UTC | initialize returned HTTP 404 | 404 | 173 ms |
| 12 Oct 2026, 01:42 UTC | initialize returned HTTP 404 | 404 | 359 ms |
| 11 Oct 2026, 17:22 UTC | initialize returned HTTP 404 | 404 | 237 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 27 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.