Schednestceo Agent Utility Network / status

Schednestceo Agent Utility Network status

Operational · last checked 07:06 UTC · 1336 ms · checked every about 5 minutes

Uptime

24 hours
99.89%
7 days
56.33%
30 days
38.88%
90 days
48.01%

90 days agotoday

Handshake latency p50 1994 ms · p95 4657 ms · mean time to recover 18 min

Incidents (90 days)

Outage · 2026-10-27 05:45 UTC · 2 min · http_5xx
Outage · 2026-10-25 13:18 UTC · 2 min · timeout
Outage · 2026-10-23 08:52 UTC · 2 min · timeout
Outage · 2026-10-08 06:08 UTC · 15 d · http_5xx
Outage · 2026-10-04 01:07 UTC · 3 d · timeout
Outage · 2026-10-04 00:04 UTC · 43 min · timeout
Outage · 2026-10-03 23:40 UTC · 16 min · timeout
Outage · 2026-10-03 00:22 UTC · 53 min · timeout
Outage · 2026-10-02 23:45 UTC · 30 min · timeout
Outage · 2026-10-01 13:40 UTC · 7 min · http_5xx
Outage · 2026-09-30 18:56 UTC · 53 min · http_5xx
Outage · 2026-09-30 10:32 UTC · 7 min · timeout
Outage · 2026-09-26 20:47 UTC · 18 min · timeout
Outage · 2026-09-15 01:57 UTC · 6 min · timeout
Outage · 2026-09-13 06:14 UTC · 6 min · http_5xx
Outage · 2026-09-08 10:06 UTC · 5 min · http_4xx
Outage · 2026-09-04 12:59 UTC · 25.8 h · http_5xx
Outage · 2026-09-01 02:51 UTC · 1.7 h · http_5xx

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/io.github.schednestceo/agent-utility-network · signed proof: /v1/proof/mcp-registry/io.github.schednestceo/agent-utility-network · Own this server?

Feedback
Help us improve