Is Assistant Bx Csv Cloud Usage Length down?
Up
No, Assistant Bx Csv Cloud Usage Length is up again.
It passed its latest check 2 h ago in 556 ms. Before that it failed our checks for 7 h 25 min, from 14 Oct 2026, 02:52 UTC.
Latest check
- Last check
- 2 h ago (14 Oct 2026, 10:18 UTC)
- Response time
- 556 ms (typical 102 ms)
- Next check
- In about 2 h
- How often
- About every 4 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 4 hours over the last 7 days.
Outages in the last 30 days
2 outages, 18 h of failed checks in total, the longest 10 h 34 min.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 14 Oct 2026, 02:52 UTC | 7 h 25 min | 2 | Expected HTTP 402, got 530 |
| 13 Oct 2026, 00:59 UTC | 10 h 34 min | 3 | Expected HTTP 402, got 530 |
Times are when our checks ran, about every 4 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 14 Oct 2026, 10:18 UTC | Passed | 402 | 556 ms |
| 14 Oct 2026, 06:31 UTC | Expected HTTP 402, got 530 | 530 | 35 ms |
| 14 Oct 2026, 02:52 UTC | Expected HTTP 402, got 530 | 530 | 37 ms |
| 13 Oct 2026, 23:04 UTC | Passed | 402 | 73 ms |
| 13 Oct 2026, 19:11 UTC | Passed | 402 | 75 ms |
| 13 Oct 2026, 15:05 UTC | Passed | 402 | 199 ms |
| 13 Oct 2026, 11:33 UTC | Passed | 402 | 59 ms |
| 13 Oct 2026, 07:32 UTC | Expected HTTP 402, got 530 | 530 | 43 ms |
| 13 Oct 2026, 04:10 UTC | Expected HTTP 402, got 530 | 530 | 36 ms |
| 13 Oct 2026, 00:59 UTC | Expected HTTP 402, got 530 | 530 | 32 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 4 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.