A2awire Benchmark Accurate Financial Record Reconcile 2026 09 22 Af293a80 / status

A2awire Benchmark Accurate Financial Record Reconcile 2026 09 22 Af293a80 status

Operational · last checked 00:40 UTC · 83 ms · checked every about 5 minutes

Uptime

24 hours

100.000%

7 days

99.73%

30 days

99.91%

90 days

99.49%

90 days agotoday

Handshake latency p50 158 ms · p95 1729 ms · mean time to recover 13 min

Incidents (90 days)

Outage · 2026-10-24 10:28 UTC · 13 min · timeout

Outage · 2026-10-22 19:29 UTC · 13 min · http_5xx

Outage · 2026-10-15 07:02 UTC · 12 min · timeout

Outage · 2026-09-24 22:56 UTC · 1.2 h · timeout

Outage · 2026-09-23 06:43 UTC · 2.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-accurate-financial-record-reconcile-2026-09-22-af293a80 · signed proof: /v1/proof/mcp-registry/com.a2awire/benchmark-accurate-financial-record-reconcile-2026-09-22-af293a80 · Own this server?