Samedaydesk Ai Readiness / status

Samedaydesk Ai Readiness status

Operational · last checked 01:07 UTC · 445 ms · checked every about 5 minutes

Uptime

24 hours
100.000%
7 days
84.74%
30 days
96.33%
90 days
96.81%

90 days agotoday

Handshake latency p50 1517 ms · p95 3178 ms · mean time to recover 8 min

Incidents (90 days)

Outage · 2026-10-22 19:33 UTC · 25.6 h · redirect
Outage · 2026-10-13 15:06 UTC · 8 min · timeout
Outage · 2026-10-06 13:11 UTC · 32 min · http_5xx
Outage · 2026-10-04 03:31 UTC · 8 min · redirect
Outage · 2026-09-24 09:17 UTC · 8 min · timeout
Outage · 2026-09-23 18:48 UTC · 7 min · redirect
Outage · 2026-09-21 10:22 UTC · 8 min · redirect
Outage · 2026-09-16 19:37 UTC · 8 min · redirect
Outage · 2026-09-14 18:46 UTC · 8 min · redirect
Outage · 2026-09-12 20:53 UTC · 10 min · redirect
Outage · 2026-09-11 07:32 UTC · 52 min · redirect
Outage · 2026-09-10 05:57 UTC · 24 min · http_5xx
Outage · 2026-09-01 14:56 UTC · 5 min · tls
Outage · 2026-08-03 21:19 UTC · 2 min · timeout
Outage · 2026-07-29 13:26 UTC · 1 min · connect

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.samedaydesk/ai-readiness · signed proof: /v1/proof/mcp-registry/com.samedaydesk/ai-readiness · Own this server?

Feedback
Help us improve