Is well-003-json-to-markdown down?
Down
Yes, well-003-json-to-markdown is down.
It has failed every check since 21 Oct 2026, 22:03 UTC (5 days 12 h, 6 checks). Latest error: Connection failed (ENOTFOUND). It last passed on 21 Oct 2026, 12:22 UTC.
Latest check
- Last check
- 24 h ago (26 Oct 2026, 09:13 UTC)
- Response time
- Not measured (typical 343 ms)
- Next check
- In about 3 h
- How often
- About every 10 hours over the last 7 days
Uptime
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
1 outage, 5 days 12 h of failed checks in total.
| Started | Duration | Failed checks | First error |
|---|---|---|---|
| 21 Oct 2026, 22:03 UTC | Ongoing, 5 days 12 h so far | 6 | Connection failed (ENOTFOUND) |
Times are when our checks ran, about every 10 hours for this listing, so start times and durations are accurate to about that.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 26 Oct 2026, 09:13 UTC | Connection failed (ENOTFOUND) | - | - |
| 25 Oct 2026, 02:30 UTC | Connection failed (ENOTFOUND) | - | - |
| 23 Oct 2026, 22:52 UTC | Connection failed (ENOTFOUND) | - | - |
| 22 Oct 2026, 18:21 UTC | Connection failed (ENOTFOUND) | - | - |
| 22 Oct 2026, 07:36 UTC | Connection failed (ENOTFOUND) | - | - |
| 21 Oct 2026, 22:03 UTC | Connection failed (ENOTFOUND) | - | - |
| 21 Oct 2026, 12:22 UTC | Passed | 200 | 111 ms |
| 21 Oct 2026, 03:19 UTC | Passed | 200 | 97 ms |
| 20 Oct 2026, 18:14 UTC | Passed | 200 | 135 ms |
| 20 Oct 2026, 08:38 UTC | Passed | 200 | 355 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.