Rootz Origin Filings / status

Rootz Origin Filings status

Down since 2026-10-25 04:20 UTC · last checked 04:47 UTC · 10767 ms · checked every about 5 minutes

Uptime

24 hours
83.65%
7 days
80.99%
30 days
69.72%
90 days
70.03%

90 days agotoday

Handshake latency p50 1011 ms · p95 5224 ms · mean time to recover 8 min

Incidents (90 days)

Ongoing outage · 2026-10-25 04:20 UTC · 43 min so far · timeout
Outage · 2026-10-25 04:04 UTC · 3 min · timeout
Outage · 2026-10-25 02:07 UTC · 3 min · timeout
Outage · 2026-10-25 01:51 UTC · 4 min · timeout
Outage · 2026-10-25 01:47 UTC · 1 min · timeout
Outage · 2026-10-25 01:22 UTC · 6 min · timeout
Outage · 2026-10-25 00:51 UTC · 2 min · timeout
Outage · 2026-10-25 00:46 UTC · 4 min · timeout
Outage · 2026-10-24 23:52 UTC · 2 min · timeout
Outage · 2026-10-24 22:22 UTC · 11 min · timeout
Outage · 2026-10-24 22:03 UTC · 6 min · timeout
Outage · 2026-10-24 21:15 UTC · 2 min · timeout
Outage · 2026-10-24 21:10 UTC · 3 min · timeout
Outage · 2026-10-24 20:27 UTC · 1 min · timeout
Outage · 2026-10-24 19:43 UTC · 4 min · timeout
Outage · 2026-10-24 19:17 UTC · 1 min · timeout
Outage · 2026-10-24 14:46 UTC · 27 min · timeout
Outage · 2026-10-24 12:48 UTC · 6 min · timeout
Outage · 2026-10-24 12:39 UTC · 2 min · timeout
Outage · 2026-10-24 12:35 UTC · 2 min · timeout
Outage · 2026-10-24 12:31 UTC · 2 min · timeout
Outage · 2026-10-24 09:52 UTC · 2 min · timeout
Outage · 2026-10-24 07:54 UTC · 1.5 h · timeout
Outage · 2026-10-24 06:47 UTC · 5 min · timeout
Outage · 2026-10-24 06:22 UTC · 6 min · timeout
Outage · 2026-10-24 00:41 UTC · 1 min · timeout
Outage · 2026-10-23 19:12 UTC · 2 min · timeout
Outage · 2026-10-23 02:48 UTC · 27 min · timeout
Outage · 2026-10-22 22:46 UTC · 4 min · timeout
Outage · 2026-10-22 22:32 UTC · 13 min · timeout

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/global.rootz.origin/filings · signed proof: /v1/proof/mcp-registry/global.rootz.origin/filings · Own this server?

Feedback
Help us improve