Is OpenWants down?
Down
Yes, OpenWants is down.
It has failed every check since 12 Oct 2026, 02:14 UTC (7 days 11 h, 8 checks). Latest error: Connection failed (ENOTFOUND). It last passed on 11 Oct 2026, 17:31 UTC.
Latest check
- Last check
- 22 h ago (18 Oct 2026, 15:15 UTC)
- Response time
- Not measured (typical 220 ms)
- Next check
- In about 7 h
- How often
- About every 29 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 29 hours over the last 7 days.
Outages in the last 30 days
1 outage, 7 days 11 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 12 Oct 2026, 02:14 UTC | Ongoing, 7 days 11 h so far | 8 | initialize returned HTTP 301 |
Times are when our checks ran, about every 29 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 18 Oct 2026, 15:15 UTC | Connection failed (ENOTFOUND) | - | - |
| 17 Oct 2026, 09:29 UTC | Connection failed (ENOTFOUND) | - | - |
| 16 Oct 2026, 04:17 UTC | Connection failed (ENOTFOUND) | - | - |
| 14 Oct 2026, 23:16 UTC | Connection failed (ENOTFOUND) | - | - |
| 13 Oct 2026, 21:06 UTC | Connection failed (ENOTFOUND) | - | - |
| 12 Oct 2026, 19:43 UTC | Connection failed (ENOTFOUND) | - | - |
| 12 Oct 2026, 10:29 UTC | initialize returned HTTP 301 | 301 | 57 ms |
| 12 Oct 2026, 02:14 UTC | initialize returned HTTP 301 | 301 | 267 ms |
| 11 Oct 2026, 17:31 UTC | Passed | 401 | 220 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 29 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.