Is Assistant Ib26 Company 05 108 down?
Possible problem
Assistant Ib26 Company 05 108 may be having problems.
Its latest check failed 59 min ago: Expected HTTP 402, got 502. The check before passed. Two failed checks in a row count as an outage. Next check: due now.
Latest check
- Last check
- 59 min ago (23 Oct 2026, 15:17 UTC)
- Response time
- Not measured (typical 108 ms)
- Next check
- Due now
- How often
- About every 7 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 7 hours over the last 7 days.
Outages in the last 30 days
2 outages, 2 days 19 h of failed checks in total, the longest 2 days.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 20 Oct 2026, 23:14 UTC | 19 h 6 min | 2 | Expected HTTP 402, got 530 |
| 17 Oct 2026, 19:58 UTC | 2 days | 5 | Expected HTTP 402, got 530 |
Times are when our checks ran, about every 7 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 23 Oct 2026, 15:17 UTC | Expected HTTP 402, got 502 | 502 | 77 ms |
| 23 Oct 2026, 10:15 UTC | Passed | 402 | 1.3 s |
| 23 Oct 2026, 00:22 UTC | Passed | 402 | 73 ms |
| 22 Oct 2026, 13:59 UTC | Passed | 402 | 378 ms |
| 22 Oct 2026, 03:31 UTC | Passed | 402 | 108 ms |
| 21 Oct 2026, 18:20 UTC | Passed | 402 | 95 ms |
| 21 Oct 2026, 08:21 UTC | Expected HTTP 402, got 530 | 530 | 29 ms |
| 20 Oct 2026, 23:14 UTC | Expected HTTP 402, got 530 | 530 | 132 ms |
| 20 Oct 2026, 14:11 UTC | Passed | 402 | 62 ms |
| 20 Oct 2026, 05:04 UTC | Passed | 402 | 1.7 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 7 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.