Is History down?
Down
Yes, History is down.
It has failed every check since 12 Oct 2026, 21:04 UTC (6 days 4 h, 31 checks). Latest error: Expected HTTP 402, got 404. It last passed on 12 Oct 2026, 17:32 UTC.
Latest check
- Last check
- 3 h ago (18 Oct 2026, 21:54 UTC)
- Response time
- Not measured (typical 313 ms)
- Next check
- In about 2 h
- 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, 6 days 4 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 12 Oct 2026, 21:04 UTC | Ongoing, 6 days 4 h so far | 31 | Expected HTTP 402, got 404 |
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 |
|---|---|---|---|
| 18 Oct 2026, 21:54 UTC | Expected HTTP 402, got 404 | 404 | 227 ms |
| 18 Oct 2026, 16:33 UTC | Expected HTTP 402, got 404 | 404 | 937 ms |
| 18 Oct 2026, 10:49 UTC | Expected HTTP 402, got 404 | 404 | 777 ms |
| 18 Oct 2026, 04:55 UTC | Expected HTTP 402, got 404 | 404 | 238 ms |
| 17 Oct 2026, 22:59 UTC | Expected HTTP 402, got 404 | 404 | 640 ms |
| 17 Oct 2026, 17:19 UTC | Expected HTTP 402, got 404 | 404 | 442 ms |
| 17 Oct 2026, 11:42 UTC | Expected HTTP 402, got 404 | 404 | 844 ms |
| 17 Oct 2026, 06:18 UTC | Expected HTTP 402, got 404 | 404 | 661 ms |
| 17 Oct 2026, 00:53 UTC | Expected HTTP 402, got 404 | 404 | 134 ms |
| 16 Oct 2026, 19:35 UTC | Expected HTTP 402, got 404 | 404 | 446 ms |
Price and payment address
- Price
- $0.03 per call on Base
- Pays to
- 0x617d…7C9e
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.