Is Atmark down?
Possible problem
Atmark may be having problems.
Its latest check failed 2 h ago: Connection failed (ENOTFOUND). The check before passed. Two failed checks in a row count as an outage. Next check: not before 16 Oct 2026, 12:07 UTC.
Latest check
- Last check
- 2 h ago (16 Oct 2026, 06:08 UTC)
- Response time
- Not measured (typical 1.3 s)
- Next check
- Not before 16 Oct 2026, 12:07 UTC
- 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 |
|---|---|---|---|
| 16 Oct 2026, 06:08 UTC | Connection failed (ENOTFOUND) | - | - |
| 15 Oct 2026, 20:42 UTC | Passed | 401 | 1.4 s |
| 15 Oct 2026, 10:54 UTC | Passed | 401 | 1.2 s |
| 15 Oct 2026, 01:36 UTC | Passed | 401 | 1.2 s |
| 14 Oct 2026, 15:32 UTC | Passed | 401 | 1.3 s |
| 14 Oct 2026, 05:48 UTC | Passed | 401 | 1.3 s |
| 13 Oct 2026, 20:57 UTC | Passed | 401 | 1.3 s |
| 13 Oct 2026, 11:34 UTC | Passed | 401 | 1.3 s |
| 13 Oct 2026, 03:12 UTC | Passed | 401 | 1.4 s |
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.