Is Assistant Ib26 Retail 01 122 down?
Possible problem
Assistant Ib26 Retail 01 122 may be having problems.
Its latest check failed 2 h ago: Expected HTTP 402, got 530. The check before passed. Two failed checks in a row count as an outage. Next check: due now.
Latest check
- Last check
- 2 h ago (4 Nov 2026, 07:29 UTC)
- Response time
- Not measured (typical 86 ms)
- Next check
- Due now
- How often
- About every 8 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 8 hours over the last 7 days.
Outages in the last 30 days
2 outages, 2 days 11 h of failed checks in total, the longest 44 h 43 min.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 31 Oct 2026, 14:58 UTC | 44 h 43 min | 3 | Expected HTTP 402, got 502 |
| 27 Oct 2026, 09:41 UTC | 14 h 40 min | 2 | Timed out |
Times are when our checks ran, about every 8 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 4 Nov 2026, 07:29 UTC | Expected HTTP 402, got 530 | 530 | 30 ms |
| 3 Nov 2026, 22:22 UTC | Passed | 402 | 513 ms |
| 3 Nov 2026, 13:27 UTC | Passed | 402 | 566 ms |
| 3 Nov 2026, 04:37 UTC | Passed | 402 | 100 ms |
| 2 Nov 2026, 19:56 UTC | Passed | 402 | 607 ms |
| 2 Nov 2026, 11:41 UTC | Passed | 402 | 271 ms |
| 1 Nov 2026, 07:32 UTC | Expected HTTP 402, got 502 | 502 | 66 ms |
| 31 Oct 2026, 23:12 UTC | Expected HTTP 402, got 502 | 502 | 62 ms |
| 31 Oct 2026, 14:58 UTC | Expected HTTP 402, got 502 | 502 | 68 ms |
| 31 Oct 2026, 06:40 UTC | Passed | 402 | 115 ms |
Price and payment address
- Price
- $0.01 per call on Base
- Pays to
- 0x8bc2…3C8C
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 8 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.