Is Browser Proof down?
Up
No, Browser Proof is up.
It passed its latest check 4 h ago in 200 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 4 h ago (15 Oct 2026, 07:58 UTC)
- Response time
- 200 ms (typical 224 ms)
- Next check
- Due now
- 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
No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 15 Oct 2026, 07:58 UTC | Passed | 402 | 200 ms |
| 15 Oct 2026, 03:42 UTC | Passed | 402 | 191 ms |
| 14 Oct 2026, 23:26 UTC | Passed | 402 | 302 ms |
| 14 Oct 2026, 19:12 UTC | Passed | 402 | 193 ms |
| 14 Oct 2026, 15:04 UTC | Passed | 402 | 508 ms |
| 14 Oct 2026, 11:02 UTC | Passed | 402 | 213 ms |
| 14 Oct 2026, 07:11 UTC | Passed | 402 | 519 ms |
| 14 Oct 2026, 03:20 UTC | Passed | 402 | 264 ms |
| 13 Oct 2026, 23:28 UTC | Passed | 402 | 178 ms |
| 13 Oct 2026, 19:42 UTC | Passed | 402 | 365 ms |
Price and payment address
- Price
- $0.01 per call on Base
- Pays to
- 0x8AfB…0Bc6
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.