Is Resolve Eip155:1 down?
Down
Yes, Resolve Eip155:1 is down.
It has not passed a check since we started checking it on 11 Oct 2026. Latest error: Expected HTTP 402, got 400.
Latest check
- Last check
- 2 h ago (19 Oct 2026, 03:06 UTC)
- Response time
- Not measured
- Next check
- In about 3 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, 03:06 UTC | Expected HTTP 402, got 400 | 400 | 308 ms |
| 18 Oct 2026, 23:27 UTC | Expected HTTP 402, got 400 | 400 | 354 ms |
| 18 Oct 2026, 18:55 UTC | Expected HTTP 402, got 400 | 400 | 346 ms |
| 18 Oct 2026, 13:19 UTC | Expected HTTP 402, got 400 | 400 | 465 ms |
| 18 Oct 2026, 07:37 UTC | Expected HTTP 402, got 400 | 400 | 324 ms |
| 18 Oct 2026, 01:42 UTC | Expected HTTP 402, got 400 | 400 | 339 ms |
| 17 Oct 2026, 19:55 UTC | Expected HTTP 402, got 400 | 400 | 335 ms |
| 17 Oct 2026, 14:15 UTC | Expected HTTP 402, got 400 | 400 | 537 ms |
| 17 Oct 2026, 08:44 UTC | Expected HTTP 402, got 400 | 400 | 387 ms |
| 17 Oct 2026, 03:12 UTC | Expected HTTP 402, got 400 | 400 | 306 ms |
Price and payment address
- Price
- $0.01 per call on Base
- Pays to
- 0x66ec…9e71
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.