Is Data Purchase down?
Down
Yes, Data Purchase is down.
It has failed every check since 13 Oct 2026, 02:29 UTC (5 days 23 h, 16 checks). Latest error: Expected HTTP 402, got 503. It last passed on 12 Oct 2026, 22:56 UTC.
Latest check
- Last check
- 12 h ago (18 Oct 2026, 13:17 UTC)
- Response time
- Not measured (typical 378 ms)
- Next check
- In about 2 days
- 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, 5 days 23 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 13 Oct 2026, 02:29 UTC | Ongoing, 5 days 23 h so far | 16 | Expected HTTP 402, got 503 |
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, 13:17 UTC | Expected HTTP 402, got 503 | 503 | 603 ms |
| 15 Oct 2026, 14:53 UTC | Expected HTTP 402, got 503 | 503 | 550 ms |
| 15 Oct 2026, 10:05 UTC | Expected HTTP 402, got 503 | 503 | 505 ms |
| 15 Oct 2026, 05:21 UTC | Expected HTTP 402, got 503 | 503 | 407 ms |
| 15 Oct 2026, 00:41 UTC | Expected HTTP 402, got 503 | 503 | 390 ms |
| 14 Oct 2026, 19:55 UTC | Expected HTTP 402, got 503 | 503 | 634 ms |
| 14 Oct 2026, 15:12 UTC | Expected HTTP 402, got 503 | 503 | 474 ms |
| 14 Oct 2026, 10:47 UTC | Expected HTTP 402, got 503 | 503 | 588 ms |
| 14 Oct 2026, 06:20 UTC | Expected HTTP 402, got 503 | 503 | 504 ms |
| 14 Oct 2026, 01:56 UTC | Expected HTTP 402, got 503 | 503 | 406 ms |
Price and payment address
- Price
- $0.01 per call on Base
- Pays to
- 0xe01c…c167
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.