Is Web Data API Plan Finder down?
Possible problem
Web Data API Plan Finder may be having problems.
Its latest check failed 7 h ago: initialize returned HTTP 503. The check before passed. Two failed checks in a row count as an outage. Next check: due now.
Latest check
- Last check
- 7 h ago (15 Oct 2026, 08:08 UTC)
- Response time
- Not measured (typical 936 ms)
- Next check
- Due now
- How often
- About every 9 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 9 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, 08:08 UTC | initialize returned HTTP 503 | 503 | 985 ms |
| 14 Oct 2026, 22:58 UTC | Passed | 200 | 936 ms |
| 14 Oct 2026, 12:44 UTC | Passed | 200 | 1.0 s |
| 14 Oct 2026, 03:45 UTC | Passed | 200 | 924 ms |
| 13 Oct 2026, 17:56 UTC | Passed | 200 | 901 ms |
| 13 Oct 2026, 08:45 UTC | Passed | 200 | 512 ms |
| 12 Oct 2026, 23:10 UTC | Passed | 200 | 1.0 s |
| 12 Oct 2026, 14:18 UTC | Passed | 200 | 911 ms |
| 12 Oct 2026, 04:14 UTC | Passed | 200 | 1.0 s |
| 11 Oct 2026, 19:02 UTC | Passed | 200 | 962 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 9 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.