A2awire Benchmark Ap Exception Review 2026 09 10 Run 13e274 / status

A2awire Benchmark Ap Exception Review 2026 09 10 Run 13e274 status

Operational · last checked 04:59 UTC · 118 ms · checked every about 5 minutes

Uptime

24 hours

100.000%

7 days

99.87%

30 days

99.89%

90 days

99.54%

90 days agotoday

Handshake latency p50 158 ms · p95 1765 ms · mean time to recover 18 min

Incidents (90 days)

Outage · 2026-10-24 10:36 UTC · 6 min · timeout

Outage · 2026-10-22 19:37 UTC · 6 min · http_5xx

Outage · 2026-10-15 06:57 UTC · 25 min · timeout

Outage · 2026-10-05 13:08 UTC · 12 min · timeout

Outage · 2026-09-24 22:46 UTC · 1.6 h · timeout

Outage · 2026-09-23 06:50 UTC · 1.4 h · 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/com.a2awire/benchmark-ap-exception-review-2026-09-10-run-13e274 · signed proof: /v1/proof/mcp-registry/com.a2awire/benchmark-ap-exception-review-2026-09-10-run-13e274 · Own this server?