Viatsy / status

Viatsy status

Down since 2026-10-22 19:05 UTC · last checked 20:34 UTC · 2026 ms · checked every about 5 minutes

Uptime

24 hours
0.00%
7 days
44.00%
30 days
86.91%
90 days
88.99%

90 days agotoday

Handshake latency p50 3118 ms · p95 5965 ms · mean time to recover 5 min

Incidents (90 days)

Ongoing outage · 2026-10-22 19:05 UTC · 4 d so far · other
Outage · 2026-10-19 04:50 UTC · 1 min · http_4xx
Outage · 2026-10-11 02:46 UTC · 7 min · http_5xx
Outage · 2026-09-22 02:08 UTC · 7 min · timeout
Outage · 2026-09-19 06:05 UTC · 18 min · timeout
Outage · 2026-09-17 03:08 UTC · 6 min · timeout
Outage · 2026-08-28 14:03 UTC · 4 min · timeout
Outage · 2026-08-28 03:02 UTC · 4 min · timeout
Outage · 2026-08-28 02:12 UTC · 7 min · timeout
Outage · 2026-08-27 23:41 UTC · 3 min · timeout
Outage · 2026-08-27 23:18 UTC · 4 min · timeout
Outage · 2026-08-27 22:57 UTC · 4 min · timeout
Outage · 2026-08-27 20:50 UTC · 5 min · timeout
Outage · 2026-08-27 20:28 UTC · 13 min · timeout
Outage · 2026-08-27 16:34 UTC · 4 min · timeout
Outage · 2026-08-10 22:10 UTC · 15 d · rpc

How this is measured

Checked by Glimind's probe (initialize + tools/list, never a tool call) from one region. Uptime counts a server as up when it completes the handshake, including when it asks for credentials. An outage starts at the first failed check, so short blips between checks are not seen. Every server is measured the same way; an owner's plan never changes these numbers. Owner updates are the owner's own words and sit next to the measurements, not in place of them.

JSON: /v1/status/mcp-registry/com.viatsy/mcp · signed proof: /v1/proof/mcp-registry/com.viatsy/mcp · Own this server?

Feedback
Help us improve