Is Crop Factor down?
Down
Yes, Crop Factor is down.
It has failed every check since 25 Oct 2026, 11:42 UTC (2 days, 3 checks). Latest error: Expected HTTP 402, got 530. It last passed on 24 Oct 2026, 23:23 UTC.
Latest check
- Last check
- 24 h ago (26 Oct 2026, 12:01 UTC)
- Response time
- Not measured (typical 535 ms)
- Next check
- In about 72 min
- 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
2 outages, 2 days 9 h of failed checks in total, the longest 2 days.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 25 Oct 2026, 11:42 UTC | Ongoing, 2 days so far | 3 | Expected HTTP 402, got 530 |
| 22 Oct 2026, 09:09 UTC | 8 h 40 min | 2 | Expected HTTP 402, got 530 |
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 |
|---|---|---|---|
| 26 Oct 2026, 12:01 UTC | Expected HTTP 402, got 530 | 530 | 99 ms |
| 25 Oct 2026, 23:31 UTC | Expected HTTP 402, got 530 | 530 | 131 ms |
| 25 Oct 2026, 11:42 UTC | Expected HTTP 402, got 530 | 530 | 102 ms |
| 24 Oct 2026, 23:23 UTC | Passed | 402 | 547 ms |
| 24 Oct 2026, 12:14 UTC | Expected HTTP 402, got 530 | 530 | 99 ms |
| 24 Oct 2026, 01:38 UTC | Passed | 402 | 569 ms |
| 23 Oct 2026, 14:24 UTC | Expected HTTP 402, got 530 | 530 | 117 ms |
| 23 Oct 2026, 03:18 UTC | Passed | 402 | 610 ms |
| 22 Oct 2026, 22:42 UTC | Expected HTTP 402, got 530 | 530 | 90 ms |
| 22 Oct 2026, 17:49 UTC | Passed | 402 | 536 ms |
Price and payment address
- Price
- $0.02 per call on Polygon
- Pays to
- 0xb531…DBDa
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.