Is Risk Why down?
Up
No, Risk Why is up.
It passed its latest check 2 h ago in 217 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 2 h ago (15 Oct 2026, 17:41 UTC)
- Response time
- 217 ms (typical 516 ms)
- Next check
- In about 2 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, 17:41 UTC | Passed | 402 | 217 ms |
| 15 Oct 2026, 13:24 UTC | Passed | 402 | 954 ms |
| 15 Oct 2026, 09:08 UTC | Passed | 402 | 1.3 s |
| 15 Oct 2026, 04:49 UTC | Passed | 402 | 608 ms |
| 15 Oct 2026, 00:35 UTC | Passed | 402 | 613 ms |
| 14 Oct 2026, 20:21 UTC | Passed | 402 | 182 ms |
| 14 Oct 2026, 16:05 UTC | Passed | 402 | 136 ms |
| 14 Oct 2026, 12:04 UTC | Passed | 402 | 136 ms |
| 14 Oct 2026, 08:10 UTC | Passed | 402 | 206 ms |
| 14 Oct 2026, 04:20 UTC | Passed | 402 | 1.0 s |
Price and payment address
- Price
- $0.02 per call on Base
- Pays to
- 0xbBaC…5D91
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.