Is Assistant Ib26 Analytics 05 201 down?
Up
No, Assistant Ib26 Analytics 05 201 is up.
It passed its latest check 8 h ago in 76 ms. It has passed every check since 19 Oct 2026, 21:15 UTC.
Latest check
- Last check
- 8 h ago (20 Oct 2026, 16:21 UTC)
- Response time
- 76 ms (typical 83 ms)
- Next check
- In about 2 h
- 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
3 outages, 3 days 2 h of failed checks in total, the longest 47 h 27 min.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 17 Oct 2026, 21:48 UTC | 47 h 27 min | 5 | Expected HTTP 402, got 530 |
| 14 Oct 2026, 00:54 UTC | 11 h 46 min | 3 | Expected HTTP 402, got 530 |
| 12 Oct 2026, 22:50 UTC | 14 h 33 min | 4 | Expected HTTP 402, got 502 |
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, 16:21 UTC | Passed | 402 | 76 ms |
| 20 Oct 2026, 06:55 UTC | Passed | 402 | 69 ms |
| 19 Oct 2026, 21:15 UTC | Passed | 402 | 77 ms |
| 18 Oct 2026, 19:06 UTC | Expected HTTP 402, got 530 | 530 | 49 ms |
| 18 Oct 2026, 13:31 UTC | Expected HTTP 402, got 530 | 530 | 49 ms |
| 18 Oct 2026, 07:53 UTC | Expected HTTP 402, got 530 | 530 | 37 ms |
| 18 Oct 2026, 02:47 UTC | Expected HTTP 402, got 530 | 530 | 39 ms |
| 17 Oct 2026, 21:48 UTC | Expected HTTP 402, got 530 | 530 | 42 ms |
| 17 Oct 2026, 16:36 UTC | Passed | 402 | 55 ms |
| 17 Oct 2026, 11:26 UTC | Passed | 402 | 103 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.