Is X402 Chain Reads V1 Chat Qwen3 32b down?
Down
Yes, X402 Chain Reads V1 Chat Qwen3 32b is down.
It has not passed a check since we started checking it on 14 Oct 2026. Latest error: Connection failed (UND_ERR_CONNECT_TIMEOUT).
Latest check
- Last check
- 3 h ago (15 Oct 2026, 04:09 UTC)
- Response time
- Not measured
- Next check
- In about 2 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 |
|---|---|---|---|
| 15 Oct 2026, 04:09 UTC | Connection failed (UND_ERR_CONNECT_TIMEOUT) | - | - |
| 14 Oct 2026, 23:19 UTC | Connection failed (UND_ERR_CONNECT_TIMEOUT) | - | - |
| 14 Oct 2026, 18:39 UTC | Connection failed (UND_ERR_CONNECT_TIMEOUT) | - | - |
| 14 Oct 2026, 14:44 UTC | Connection failed (UND_ERR_CONNECT_TIMEOUT) | - | - |
| 14 Oct 2026, 05:00 UTC | Connection failed (UND_ERR_CONNECT_TIMEOUT) | - | - |
Price and payment address
- Price
- $0.003 per call on Base
- Pays to
- 0xBF32…a035
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.