Is Web Read down?
Down
Yes, Web Read is down.
It has not passed a check since we started checking it on 16 Oct 2026. Latest error: Expected HTTP 402, got 530.
Latest check
- Last check
- 4 h ago (18 Oct 2026, 19:18 UTC)
- Response time
- Not measured
- Next check
- In about 3 days
- How often
- About every 6 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 6 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 |
|---|---|---|---|
| 18 Oct 2026, 19:18 UTC | Expected HTTP 402, got 530 | 530 | 286 ms |
| 18 Oct 2026, 13:47 UTC | Expected HTTP 402, got 530 | 530 | 235 ms |
| 18 Oct 2026, 08:07 UTC | Expected HTTP 402, got 530 | 530 | 185 ms |
| 18 Oct 2026, 02:09 UTC | Expected HTTP 402, got 530 | 530 | 126 ms |
| 17 Oct 2026, 20:21 UTC | Expected HTTP 402, got 530 | 530 | 134 ms |
| 17 Oct 2026, 14:48 UTC | Expected HTTP 402, got 530 | 530 | 111 ms |
| 17 Oct 2026, 09:15 UTC | Expected HTTP 402, got 530 | 530 | 131 ms |
| 17 Oct 2026, 03:46 UTC | Expected HTTP 402, got 530 | 530 | 125 ms |
| 16 Oct 2026, 22:22 UTC | Expected HTTP 402, got 530 | 530 | 162 ms |
| 16 Oct 2026, 17:53 UTC | Expected HTTP 402, got 530 | 530 | 162 ms |
Price and payment address
- Price
- $0.001 per call on Base
- Pays to
- 0x6b5a…A6E1
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 6 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.