Is Registry Cask down?
Down
Yes, Registry Cask is down.
It has not passed a check since we started checking it on 16 Oct 2026. Latest error: Expected HTTP 402, got 400.
Latest check
- Last check
- 45 min ago (17 Oct 2026, 13:27 UTC)
- Response time
- Not measured
- Next check
- In about 5 h
- How often
- About every 5 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 5 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 |
|---|---|---|---|
| 17 Oct 2026, 13:27 UTC | Expected HTTP 402, got 400 | 400 | 465 ms |
| 17 Oct 2026, 08:02 UTC | Expected HTTP 402, got 400 | 400 | 221 ms |
| 17 Oct 2026, 02:44 UTC | Expected HTTP 402, got 400 | 400 | 239 ms |
| 16 Oct 2026, 21:22 UTC | Expected HTTP 402, got 400 | 400 | 567 ms |
| 16 Oct 2026, 16:09 UTC | Expected HTTP 402, got 400 | 400 | 472 ms |
| 16 Oct 2026, 11:38 UTC | Expected HTTP 402, got 400 | 400 | 201 ms |
| 16 Oct 2026, 07:19 UTC | Expected HTTP 402, got 400 | 400 | 188 ms |
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 5 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.