Is Inspect down?
Down
Yes, Inspect is down.
It has failed every check since 16 Oct 2026, 01:02 UTC (2 days 5 h, 11 checks). Latest error: Expected HTTP 402, got 410. It last passed on 15 Oct 2026, 20:49 UTC.
Latest check
- Last check
- 47 min ago (18 Oct 2026, 05:01 UTC)
- Response time
- Not measured (typical 349 ms)
- Next check
- In about 5 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
1 outage, 2 days 5 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 16 Oct 2026, 01:02 UTC | Ongoing, 2 days 5 h so far | 11 | Expected HTTP 402, got 410 |
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 |
|---|---|---|---|
| 18 Oct 2026, 05:01 UTC | Expected HTTP 402, got 410 | 410 | 371 ms |
| 17 Oct 2026, 23:17 UTC | Expected HTTP 402, got 410 | 410 | 460 ms |
| 17 Oct 2026, 17:30 UTC | Expected HTTP 402, got 410 | 410 | 384 ms |
| 17 Oct 2026, 11:56 UTC | Expected HTTP 402, got 410 | 410 | 358 ms |
| 17 Oct 2026, 06:31 UTC | Expected HTTP 402, got 410 | 410 | 334 ms |
| 17 Oct 2026, 01:10 UTC | Expected HTTP 402, got 410 | 410 | 395 ms |
| 16 Oct 2026, 19:55 UTC | Expected HTTP 402, got 410 | 410 | 388 ms |
| 16 Oct 2026, 14:40 UTC | Expected HTTP 402, got 410 | 410 | 375 ms |
| 16 Oct 2026, 09:30 UTC | Expected HTTP 402, got 410 | 410 | 363 ms |
| 16 Oct 2026, 05:13 UTC | Expected HTTP 402, got 410 | 410 | 304 ms |
Price and payment address
- Price
- $0.005 per call on Base
- Pays to
- 0x2c49…5452
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.