Is Assistant Ib26 Analytics 19 173 down?
Possible problem
Assistant Ib26 Analytics 19 173 may be having problems.
Its latest check failed 5 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, 04:29 UTC.
Latest check
- Last check
- 5 h ago (20 Oct 2026, 22:24 UTC)
- Response time
- Not measured (typical 74 ms)
- Next check
- Not before 21 Oct 2026, 04:29 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, 45 h 49 min of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 17 Oct 2026, 21:19 UTC | 45 h 49 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 |
|---|---|---|---|
| 20 Oct 2026, 22:24 UTC | Expected HTTP 402, got 530 | 530 | 23 ms |
| 20 Oct 2026, 13:02 UTC | Passed | 402 | 65 ms |
| 20 Oct 2026, 03:56 UTC | Passed | 402 | 57 ms |
| 19 Oct 2026, 19:08 UTC | Passed | 402 | 4.9 s |
| 18 Oct 2026, 18:34 UTC | Expected HTTP 402, got 530 | 530 | 36 ms |
| 18 Oct 2026, 13:03 UTC | Expected HTTP 402, got 530 | 530 | 38 ms |
| 18 Oct 2026, 07:28 UTC | Expected HTTP 402, got 530 | 530 | 40 ms |
| 18 Oct 2026, 02:21 UTC | Expected HTTP 402, got 530 | 530 | 174 ms |
| 17 Oct 2026, 21:19 UTC | Expected HTTP 402, got 530 | 530 | 44 ms |
| 17 Oct 2026, 16:10 UTC | Passed | 402 | 1.2 s |
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.