Is Assistant Ib26 Security 22 023 down?
Down
Yes, Assistant Ib26 Security 22 023 is down.
It has failed every check since 5 Nov 2026, 07:15 UTC (2 days 9 h, 4 checks). Latest error: Expected HTTP 402, got 530. It last passed on 4 Nov 2026, 22:04 UTC.
Latest check
- Last check
- 8 h ago (7 Nov 2026, 07:57 UTC)
- Response time
- Not measured (typical 77 ms)
- Next check
- In about 15 h
- How often
- About every 9 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 9 hours over the last 7 days.
Outages in the last 30 days
2 outages, 4 days 6 h of failed checks in total, the longest 2 days 9 h.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 5 Nov 2026, 07:15 UTC | Ongoing, 2 days 9 h so far | 4 | Expected HTTP 402, got 530 |
| 31 Oct 2026, 13:29 UTC | 45 h 10 min | 3 | Expected HTTP 402, got 530 |
Times are when our checks ran, about every 9 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 7 Nov 2026, 07:57 UTC | Expected HTTP 402, got 530 | 530 | 40 ms |
| 6 Nov 2026, 01:47 UTC | Expected HTTP 402, got 530 | 530 | 23 ms |
| 5 Nov 2026, 16:19 UTC | Expected HTTP 402, got 530 | 530 | 25 ms |
| 5 Nov 2026, 07:15 UTC | Expected HTTP 402, got 530 | 530 | 34 ms |
| 4 Nov 2026, 22:04 UTC | Passed | 402 | 71 ms |
| 4 Nov 2026, 12:50 UTC | Passed | 402 | 394 ms |
| 4 Nov 2026, 03:53 UTC | Expected HTTP 402, got 530 | 530 | 23 ms |
| 3 Nov 2026, 18:53 UTC | Passed | 402 | 417 ms |
| 3 Nov 2026, 09:58 UTC | Passed | 402 | 453 ms |
| 3 Nov 2026, 01:03 UTC | Passed | 402 | 71 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 9 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.