Is Preprints Search down?
Possible problem
Preprints Search may be having problems.
Its latest check failed 3 h ago: Expected HTTP 402, got 503. The check before passed. Two failed checks in a row count as an outage. Next check: due now.
Latest check
- Last check
- 3 h ago (17 Oct 2026, 11:27 UTC)
- Response time
- Not measured (typical 1.4 s)
- Next check
- Due now
- 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
1 outage, 14 h 25 min of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 16 Oct 2026, 16:05 UTC | 14 h 25 min | 3 | Timed out |
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 |
|---|---|---|---|
| 17 Oct 2026, 11:27 UTC | Expected HTTP 402, got 503 | 503 | 1.1 s |
| 17 Oct 2026, 06:30 UTC | Passed | 402 | 1.4 s |
| 17 Oct 2026, 01:09 UTC | Expected HTTP 402, got 503 | 503 | 506 ms |
| 16 Oct 2026, 20:35 UTC | Expected HTTP 402, got 503 | 503 | 786 ms |
| 16 Oct 2026, 16:05 UTC | Timed out | - | - |
| 16 Oct 2026, 11:19 UTC | Passed | 402 | 1.8 s |
| 16 Oct 2026, 01:08 UTC | Passed | 402 | 1.4 s |
Price and payment address
- Price
- $0.01 per call on Base
- Pays to
- 0xA2A8…c8aa
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.