Sponsorable / status

Sponsorable status

Down since 2026-10-20 15:28 UTC · last checked 16:56 UTC · 522 ms · checked every about 5 minutes

Uptime

24 hours
0.00%
7 days
12.90%
30 days
76.12%
90 days
79.92%

90 days agotoday

Handshake latency p50 2126 ms · p95 3760 ms · mean time to recover 1526 min

Incidents (90 days)

Ongoing outage · 2026-10-20 15:28 UTC · 6 d so far · other
Outage · 2026-10-18 16:20 UTC · 25.5 h · other
Outage · 2026-10-16 02:55 UTC · 8 min · timeout
Outage · 2026-10-10 00:06 UTC · 7 min · timeout
Outage · 2026-09-26 00:03 UTC · 15 min · timeout
Outage · 2026-08-29 23:27 UTC · 33 min · rpc
Outage · 2026-08-27 21:20 UTC · 25.5 h · rpc
Outage · 2026-08-25 19:38 UTC · 25.6 h · rpc
Outage · 2026-08-23 19:39 UTC · 25.4 h · rpc
Outage · 2026-08-22 22:24 UTC · 2.1 h · rpc
Outage · 2026-08-20 19:56 UTC · 25.8 h · rpc
Outage · 2026-08-20 00:01 UTC · 14 min · timeout
Outage · 2026-08-18 22:18 UTC · 25.7 h · rpc
Outage · 2026-08-16 16:54 UTC · 25.6 h · rpc
Outage · 2026-08-14 20:58 UTC · 25.5 h · rpc
Outage · 2026-08-12 20:06 UTC · 25.4 h · rpc
Outage · 2026-08-10 19:33 UTC · 25.4 h · rpc
Outage · 2026-08-08 19:51 UTC · 25.4 h · rpc
Outage · 2026-08-06 18:35 UTC · 25.4 h · rpc
Outage · 2026-08-04 15:41 UTC · 25.4 h · rpc
Outage · 2026-08-02 15:23 UTC · 25.4 h · rpc
Outage · 2026-07-31 15:42 UTC · 25.4 h · rpc
Outage · 2026-07-29 15:05 UTC · 25.4 h · 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.sponsorable/sponsorable · signed proof: /v1/proof/mcp-registry/com.sponsorable/sponsorable · Own this server?

Feedback
Help us improve