Is Collision 1d down?
Down
Yes, Collision 1d is down.
It has failed every check since 25 Oct 2026, 11:26 UTC (2 days 1 h, 3 checks). Latest error: Expected HTTP 402, got 530. It last passed on 25 Oct 2026, 00:02 UTC.
Latest check
- Last check
- 24 h ago (26 Oct 2026, 12:15 UTC)
- Response time
- Not measured (typical 478 ms)
- Next check
- Due now
- How often
- About every 9 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 9 hours over the last 7 days.
Outages in the last 30 days
2 outages, 3 days 18 h of failed checks in total, the longest 2 days 1 h.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 25 Oct 2026, 11:26 UTC | Ongoing, 2 days 1 h so far | 3 | Expected HTTP 402, got 530 |
| 22 Oct 2026, 09:04 UTC | 41 h 23 min | 3 | Expected HTTP 402, got 530 |
Times are when our checks ran, about every 9 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 26 Oct 2026, 12:15 UTC | Expected HTTP 402, got 530 | 530 | 154 ms |
| 25 Oct 2026, 23:50 UTC | Expected HTTP 402, got 530 | 530 | 89 ms |
| 25 Oct 2026, 11:26 UTC | Expected HTTP 402, got 530 | 530 | 102 ms |
| 25 Oct 2026, 00:02 UTC | Passed | 402 | 550 ms |
| 24 Oct 2026, 13:03 UTC | Expected HTTP 402, got 530 | 530 | 106 ms |
| 24 Oct 2026, 02:27 UTC | Passed | 402 | 578 ms |
| 22 Oct 2026, 23:37 UTC | Expected HTTP 402, got 530 | 530 | 98 ms |
| 22 Oct 2026, 13:18 UTC | Expected HTTP 402, got 530 | 530 | 200 ms |
| 22 Oct 2026, 09:04 UTC | Expected HTTP 402, got 530 | 530 | 145 ms |
| 22 Oct 2026, 04:46 UTC | Passed | 402 | 236 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 9 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.