Is Crypto Impermanent Loss down?
Up
No, Crypto Impermanent Loss is up.
It passed its latest check 1 h ago in 273 ms, and every check since we started checking it on 17 Oct 2026.
Latest check
- Last check
- 1 h ago (19 Oct 2026, 12:33 UTC)
- Response time
- 273 ms (typical 159 ms)
- Next check
- In about 4 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 |
|---|---|---|---|
| 19 Oct 2026, 12:33 UTC | Passed | 402 | 273 ms |
| 19 Oct 2026, 09:30 UTC | Passed | 402 | 159 ms |
| 19 Oct 2026, 06:17 UTC | Passed | 402 | 215 ms |
| 19 Oct 2026, 03:15 UTC | Passed | 402 | 209 ms |
| 19 Oct 2026, 00:08 UTC | Passed | 402 | 148 ms |
| 18 Oct 2026, 20:28 UTC | Passed | 402 | 149 ms |
| 18 Oct 2026, 15:23 UTC | Passed | 402 | 166 ms |
| 18 Oct 2026, 10:18 UTC | Passed | 402 | 152 ms |
| 18 Oct 2026, 04:51 UTC | Passed | 402 | 141 ms |
| 17 Oct 2026, 23:27 UTC | Passed | 402 | 169 ms |
Price and payment address
- Price
- $0.002 per call on Base
- Pays to
- 0x8a0F…b0f6
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.