Is Read down?
Up
No, Read is up.
It passed its latest check 3 h ago in 402 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 3 h ago (17 Oct 2026, 02:27 UTC)
- Response time
- 402 ms (typical 319 ms)
- Next check
- In about 39 min
- 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 |
|---|---|---|---|
| 17 Oct 2026, 02:27 UTC | Passed | 402 | 402 ms |
| 16 Oct 2026, 21:38 UTC | Passed | 402 | 315 ms |
| 16 Oct 2026, 16:55 UTC | Passed | 402 | 372 ms |
| 16 Oct 2026, 12:10 UTC | Passed | 402 | 305 ms |
| 16 Oct 2026, 07:35 UTC | Passed | 402 | 288 ms |
| 16 Oct 2026, 03:00 UTC | Passed | 402 | 319 ms |
| 15 Oct 2026, 22:37 UTC | Passed | 402 | 389 ms |
| 15 Oct 2026, 18:37 UTC | Passed | 402 | 277 ms |
| 15 Oct 2026, 14:24 UTC | Passed | 402 | 404 ms |
| 15 Oct 2026, 10:06 UTC | Passed | 402 | 319 ms |
Price and payment address
- Price
- $0.002 per call on Base
- Pays to
- 0xBbfC…E704
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.