Desvela Registry / status

Desvela Registry status

Operational · last checked 21:30 UTC · 675 ms · checked every about 5 minutes

Uptime

24 hours

100.000%

7 days

99.92%

30 days

99.967%

90 days

99.972%

90 days agotoday

Handshake latency p50 2144 ms · p95 4351 ms · mean time to recover 6 min

Incidents (90 days)

Outage · 2026-10-15 06:29 UTC · 8 min · blocked

Outage · 2026-10-07 00:53 UTC · 7 min · timeout

Outage · 2026-09-02 12:54 UTC · 5 min · http_5xx

Outage · 2026-08-26 17:57 UTC · 7 min · timeout

Outage · 2026-08-18 08:45 UTC · 3 min · timeout

Outage · 2026-08-09 14:51 UTC · 3 min · 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/dev.desvela/registry · signed proof: /v1/proof/mcp-registry/dev.desvela/registry · Own this server?