Is X402scan Scan down?
Down
Yes, X402scan Scan is down.
It has failed every check since 3 Nov 2026, 15:03 UTC (6 days 10 h, 10 checks). Latest error: Expected HTTP 402, got 404. It last passed on 3 Nov 2026, 06:25 UTC.
Latest check
- Last check
- 12 h ago (9 Nov 2026, 12:28 UTC)
- Response time
- Not measured (typical 1.8 s)
- Next check
- In about 2 days
- How often
- About every 10 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 10 hours over the last 7 days.
Outages in the last 30 days
1 outage, 6 days 10 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 3 Nov 2026, 15:03 UTC | Ongoing, 6 days 10 h so far | 10 | Expected HTTP 402, got 404 |
Times are when our checks ran, about every 10 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 9 Nov 2026, 12:28 UTC | Expected HTTP 402, got 404 | 404 | 111 ms |
| 8 Nov 2026, 05:46 UTC | Expected HTTP 402, got 404 | 404 | 107 ms |
| 7 Nov 2026, 03:07 UTC | Expected HTTP 402, got 404 | 404 | 107 ms |
| 6 Nov 2026, 00:04 UTC | Expected HTTP 402, got 404 | 404 | 74 ms |
| 5 Nov 2026, 13:50 UTC | Expected HTTP 402, got 404 | 404 | 120 ms |
| 5 Nov 2026, 04:01 UTC | Expected HTTP 402, got 404 | 404 | 118 ms |
| 4 Nov 2026, 18:20 UTC | Expected HTTP 402, got 404 | 404 | 122 ms |
| 4 Nov 2026, 08:37 UTC | Expected HTTP 402, got 404 | 404 | 164 ms |
| 3 Nov 2026, 23:44 UTC | Expected HTTP 402, got 404 | 404 | 122 ms |
| 3 Nov 2026, 15:03 UTC | Expected HTTP 402, got 404 | 404 | 124 ms |
Price and payment address
- Price
- $0.02 per call on Base
- Pays to
- 0xaBa4…8CB7
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 10 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.