Is Assistant Ib26 Analytics 20 016 down?
Possible problem
Assistant Ib26 Analytics 20 016 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: not before 21 Oct 2026, 07:35 UTC.
Latest check
- Last check
- 2 h ago (21 Oct 2026, 01:35 UTC)
- Response time
- Not measured (typical 92 ms)
- Next check
- Not before 21 Oct 2026, 07:35 UTC
- 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
1 outage, 47 h 32 min of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 17 Oct 2026, 21:11 UTC | 47 h 32 min | 5 | Expected HTTP 402, got 530 |
Times are when our checks ran, about every 5 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 21 Oct 2026, 01:35 UTC | Expected HTTP 402, got 530 | 530 | 23 ms |
| 20 Oct 2026, 15:56 UTC | Passed | 402 | 92 ms |
| 20 Oct 2026, 06:19 UTC | Passed | 402 | 64 ms |
| 19 Oct 2026, 20:43 UTC | Passed | 402 | 85 ms |
| 18 Oct 2026, 18:34 UTC | Expected HTTP 402, got 530 | 530 | 36 ms |
| 18 Oct 2026, 12:54 UTC | Expected HTTP 402, got 530 | 530 | 40 ms |
| 18 Oct 2026, 07:17 UTC | Expected HTTP 402, got 530 | 530 | 33 ms |
| 18 Oct 2026, 02:11 UTC | Expected HTTP 402, got 530 | 530 | 32 ms |
| 17 Oct 2026, 21:11 UTC | Expected HTTP 402, got 530 | 530 | 50 ms |
| 17 Oct 2026, 16:02 UTC | Passed | 402 | 176 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 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.