Is Read down?
Down
Yes, Read is down.
It has failed every check since 13 Oct 2026, 07:15 UTC (6 days 12 h, 15 checks). Latest error: Expected HTTP 402, got 503. It last passed on 13 Oct 2026, 03:42 UTC.
Latest check
- Last check
- 24 h ago (18 Oct 2026, 19:06 UTC)
- Response time
- Not measured (typical 263 ms)
- Next check
- In about 2 days
- 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
1 outage, 6 days 12 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 13 Oct 2026, 07:15 UTC | Ongoing, 6 days 12 h so far | 15 | Expected HTTP 402, got 503 |
Times are when our checks ran, about every 4 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 18 Oct 2026, 19:06 UTC | Expected HTTP 402, got 503 | 503 | 258 ms |
| 15 Oct 2026, 15:45 UTC | Expected HTTP 402, got 503 | 503 | 618 ms |
| 15 Oct 2026, 10:57 UTC | Expected HTTP 402, got 503 | 503 | 256 ms |
| 15 Oct 2026, 06:14 UTC | Expected HTTP 402, got 503 | 503 | 584 ms |
| 15 Oct 2026, 01:29 UTC | Expected HTTP 402, got 503 | 503 | 572 ms |
| 14 Oct 2026, 20:50 UTC | Expected HTTP 402, got 503 | 503 | 264 ms |
| 14 Oct 2026, 16:03 UTC | Expected HTTP 402, got 503 | 503 | 259 ms |
| 14 Oct 2026, 11:33 UTC | Expected HTTP 402, got 503 | 503 | 266 ms |
| 14 Oct 2026, 07:05 UTC | Expected HTTP 402, got 503 | 503 | 243 ms |
| 14 Oct 2026, 02:41 UTC | Expected HTTP 402, got 503 | 503 | 270 ms |
Price and payment address
- Price
- $0.005 per call on Base
- Pays to
- 0x9fb6…400a
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.