Is Web2md down?
Up
No, Web2md is up.
It passed its latest check 3 h ago in 307 ms. It has passed every check since 16 Oct 2026, 07:51 UTC.
Latest check
- Last check
- 3 h ago (16 Oct 2026, 07:51 UTC)
- Response time
- 307 ms (typical 162 ms)
- Next check
- Not before 16 Oct 2026, 14:24 UTC
- How often
- About every 10 hours over the last 7 days
Uptime
Last 24 hours66.7%3 checks
Last 7 days44.4%9 checks
Last 30 days44.4%9 checks
All checks passedSome failedAll failedNot checked
Uptime is the share of checks that passed. We checked it about every 10 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 |
|---|---|---|---|
| 16 Oct 2026, 07:51 UTC | Passed | 200 | 307 ms |
| 15 Oct 2026, 21:18 UTC | Connection failed (ENOTFOUND) | - | - |
| 15 Oct 2026, 11:50 UTC | Passed | 200 | 332 ms |
| 15 Oct 2026, 02:15 UTC | Passed | 200 | 162 ms |
| 14 Oct 2026, 17:08 UTC | Passed | 200 | 136 ms |
| 13 Oct 2026, 13:52 UTC | initialize returned HTTP 502 | 502 | 315 ms |
| 12 Oct 2026, 11:13 UTC | initialize returned HTTP 502 | 502 | 207 ms |
| 12 Oct 2026, 02:20 UTC | initialize returned HTTP 502 | 502 | 260 ms |
| 11 Oct 2026, 18:06 UTC | initialize returned HTTP 502 | 502 | 303 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 10 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.