Is Fetch down?
Possible problem
Fetch may be having problems.
Its latest check failed 4 min ago: Timed out. The check before passed. Two failed checks in a row count as an outage. Next check: not before 19 Oct 2026, 11:18 UTC.
Latest check
- Last check
- 4 min ago (19 Oct 2026, 11:04 UTC)
- Response time
- Not measured (typical 2.2 s)
- Next check
- Not before 19 Oct 2026, 11:18 UTC
- How often
- About every 4 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 4 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, 11:04 UTC | Timed out | - | - |
| 19 Oct 2026, 07:57 UTC | Passed | 402 | 2.2 s |
| 19 Oct 2026, 04:50 UTC | Passed | 402 | 2.2 s |
| 19 Oct 2026, 01:53 UTC | Passed | 402 | 2.2 s |
| 18 Oct 2026, 22:43 UTC | Passed | 402 | 2.3 s |
| 18 Oct 2026, 18:15 UTC | Passed | 402 | 2.1 s |
| 18 Oct 2026, 13:11 UTC | Passed | 402 | 7.4 s |
| 18 Oct 2026, 07:59 UTC | Passed | 402 | 1.5 s |
| 18 Oct 2026, 02:36 UTC | Passed | 402 | 739 ms |
| 17 Oct 2026, 21:23 UTC | Passed | 402 | 2.3 s |
Price and payment address
- Price
- $0.005 per call on Base
- Pays to
- 0x1545…18c4
No price or payment address changes recorded.
How we check
Up means the endpoint answered an unpaid test request with a valid x402 payment challenge. We never pay, so we can't see whether the paid response works.
Checks come from our server, about every 4 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. To see what an agent gets right now, check it yourself.