Is Cases Search down?
Possible problem
Cases Search may be having problems.
Its latest check failed 27 min ago: Expected HTTP 402, got 503. The check before passed. Two failed checks in a row count as an outage. Next check: in about 3 h.
Latest check
- Last check
- 27 min ago (15 Oct 2026, 02:05 UTC)
- Response time
- Not measured (typical 1.2 s)
- Next check
- In about 3 h
- 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 |
|---|---|---|---|
| 15 Oct 2026, 02:05 UTC | Expected HTTP 402, got 503 | 503 | 7.4 s |
| 14 Oct 2026, 21:53 UTC | Passed | 402 | 3.3 s |
| 14 Oct 2026, 17:56 UTC | Expected HTTP 402, got 503 | 503 | 7.8 s |
| 14 Oct 2026, 13:48 UTC | Passed | 402 | 2.7 s |
| 14 Oct 2026, 09:46 UTC | Passed | 402 | 2.5 s |
| 14 Oct 2026, 05:50 UTC | Passed | 402 | 793 ms |
| 14 Oct 2026, 01:55 UTC | Passed | 402 | 1.1 s |
| 13 Oct 2026, 22:06 UTC | Passed | 402 | 522 ms |
| 13 Oct 2026, 18:33 UTC | Expected HTTP 402, got 503 | 503 | 7.3 s |
| 13 Oct 2026, 14:35 UTC | Passed | 402 | 5.5 s |
Price and payment address
- Price
- $0.01 per call on Base
- Pays to
- 0xA2A8…c8aa
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.