Is WebRead down?
Up
No, WebRead is up.
It passed its latest check 11 h ago in 27 ms, and every check since we started checking it on 22 Oct 2026.
Latest check
- Last check
- 11 h ago (28 Oct 2026, 12:27 UTC)
- Response time
- 27 ms (typical 96 ms)
- Next check
- In about 13 min
- How often
- About every 11 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 11 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 |
|---|---|---|---|
| 28 Oct 2026, 12:27 UTC | Passed | 200 | 27 ms |
| 27 Oct 2026, 23:38 UTC | Passed | 200 | 75 ms |
| 27 Oct 2026, 10:26 UTC | Passed | 200 | 105 ms |
| 26 Oct 2026, 20:48 UTC | Passed | 200 | 151 ms |
| 26 Oct 2026, 08:04 UTC | Passed | 200 | 92 ms |
| 25 Oct 2026, 19:59 UTC | Passed | 200 | 36 ms |
| 25 Oct 2026, 07:34 UTC | Passed | 200 | 103 ms |
| 24 Oct 2026, 20:07 UTC | Passed | 200 | 96 ms |
| 24 Oct 2026, 09:36 UTC | Passed | 200 | 95 ms |
| 23 Oct 2026, 22:50 UTC | Passed | 200 | 102 ms |
How we check
Up means the MCP handshake and the tool list worked, or the server asked for sign-in or payment.
Checks come from our server, about every 11 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.