Is Monitor Latency down?
Up
No, Monitor Latency is up.
It passed its latest check 3 h ago in 39 ms, and every check since we started checking it on 11 Oct 2026.
Latest check
- Last check
- 3 h ago (14 Oct 2026, 23:18 UTC)
- Response time
- 39 ms (typical 47 ms)
- Next check
- In about 36 min
- 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 |
|---|---|---|---|
| 14 Oct 2026, 23:18 UTC | Passed | 402 | 39 ms |
| 14 Oct 2026, 19:09 UTC | Passed | 402 | 58 ms |
| 14 Oct 2026, 15:00 UTC | Passed | 402 | 65 ms |
| 14 Oct 2026, 10:57 UTC | Passed | 402 | 46 ms |
| 14 Oct 2026, 07:01 UTC | Passed | 402 | 61 ms |
| 14 Oct 2026, 03:05 UTC | Passed | 402 | 39 ms |
| 13 Oct 2026, 23:19 UTC | Passed | 402 | 128 ms |
| 13 Oct 2026, 19:30 UTC | Passed | 402 | 63 ms |
| 13 Oct 2026, 15:29 UTC | Passed | 402 | 573 ms |
| 13 Oct 2026, 11:51 UTC | Passed | 402 | 1.0 s |
Price and payment address
- Price
- $0.01 per call on Base
- Pays to
- 0xFC24…eBB3
| Date | Change |
|---|---|
| 11 Oct 2026 | Payment address changed from 0x91D5…0abd to 0xFC24…eBB3 |
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.