Belegante Byte Aetherx / status

Belegante Byte Aetherx status

Down since 2026-10-17 16:42 UTC · last checked 18:44 UTC · 10501 ms · checked every about 5 minutes

Uptime

24 hours
77.94%
7 days
96.42%
30 days
98.67%
90 days
98.67%

90 days agotoday

Handshake latency p50 1809 ms · p95 3579 ms · mean time to recover 7 min

Incidents (90 days)

Ongoing outage · 2026-10-17 16:42 UTC · 5.0 h so far · timeout
Outage · 2026-10-17 16:14 UTC · 8 min · timeout
Outage · 2026-10-17 07:06 UTC · 8 min · timeout
Outage · 2026-10-15 06:23 UTC · 7 min · timeout
Outage · 2026-10-14 19:12 UTC · 7 min · timeout
Outage · 2026-10-12 22:37 UTC · 7 min · timeout
Outage · 2026-10-12 05:24 UTC · 7 min · timeout
Outage · 2026-10-11 19:16 UTC · 7 min · timeout
Outage · 2026-10-11 02:03 UTC · 7 min · timeout
Outage · 2026-10-10 09:50 UTC · 7 min · timeout
Outage · 2026-10-10 04:46 UTC · 7 min · timeout
Outage · 2026-10-10 03:44 UTC · 8 min · timeout
Outage · 2026-10-09 01:21 UTC · 7 min · timeout
Outage · 2026-10-08 21:18 UTC · 7 min · timeout
Outage · 2026-10-08 19:17 UTC · 7 min · timeout
Outage · 2026-10-07 16:55 UTC · 7 min · timeout
Outage · 2026-10-07 00:43 UTC · 7 min · timeout
Outage · 2026-10-05 12:13 UTC · 7 min · timeout
Outage · 2026-10-03 20:14 UTC · 7 min · http_5xx
Outage · 2026-10-03 11:03 UTC · 11 min · timeout
Outage · 2026-09-30 13:13 UTC · 7 min · timeout
Outage · 2026-09-30 12:12 UTC · 8 min · timeout
Outage · 2026-09-29 18:39 UTC · 6 min · timeout
Outage · 2026-09-29 17:02 UTC · 9 min · timeout
Outage · 2026-09-29 15:20 UTC · 10 min · timeout
Outage · 2026-09-29 13:52 UTC · 15 min · http_5xx
Outage · 2026-09-29 12:43 UTC · 8 min · http_5xx
Outage · 2026-09-28 08:30 UTC · 11 min · timeout
Outage · 2026-09-26 05:19 UTC · 8 min · timeout
Outage · 2026-09-24 20:08 UTC · 19 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/io.github.belegante-byte/aetherx-mcp · signed proof: /v1/proof/mcp-registry/io.github.belegante-byte/aetherx-mcp · Own this server?