§ status

Operational.

Everything that is switched on is working. lightning settlement rail is still forming — not broken, not yet carrying anything. Checked 2026-10-09 04:33 UTC.

request latency + errors
p95 latency and 5xx rate, since 00:00 UTC yesterday
p95 ≤ 250ms · 0.00% 5xx across 409 requests
orangecheck
operational
me.ochk.io · web
this site and its API
this handler responded · web is up by definition
orangecheck
operational
auth host · ochk.io
issues sign-in sessions and the key that verifies them
auth host jwks · 1/1 reachable
orangecheck
operational
kv · upstash
the live store
upstash · roundtrip ok
upstash
operational
federation registry
the federation directory, and whether one can be joined
3 federations · 0 joinable · executor rail: oc-testnet-v1 (stores an invite it has no mint for) · 2 recruiting
orangecheck
operational
platform account · per federation
what the platform is owed and owes, per federation
3 snapshots read OK
orangecheck
operational
operator registry
accepted guardian operators
0 accepted operators
orangecheck
operational
oc business treasury
orangecheck's own revenue books
balance read OK
orangecheck
operational
scheduled jobs · cron
backups, anchoring, webhook retries, payout sweeps
10 jobs reporting within cadence
vercel cron
operational
oc envelope signing
signs every envelope
signs locally · always nominal
orangecheck
not probed
opentimestamps anchor
timestamps envelope hashes on bitcoin
nothing pending · 4 anchored, latest block 965487 · degrades past 24h pending, fails past 72h · opentimestamps calendars · 5/5 reachable
opentimestamps calendars
operational
nostr relay set
republishes every envelope
nostr relay set · 4/4 reachable · quorum 2 incl. 1 public
relay.ochk.io and public relays
operational
lightning settlement rail
pays users and operators
forming · no real sats can move, and no event bills for real yet
orangecheck
forming
executor · settlement signer
signs and sends each settlement
last beat 0m ago · network testnet3 · height 5157550 · v01M4BJRYAA8S34SWBVAR5AS7HZ
orangecheck
operational

§ live probes · client-side

probing… · auto-refresh 60s

me.ochk.io · /api/health
liveness — running app + cookie parsing
—
pending
auth · /api/auth/me
401 with no cookie is correct; 5xx is not
—
pending
ochk.io · /.well-known/jwks.json
public Ed25519 JWK every consumer verifies against
—
pending
envelope · /api/envelope/[id]
404 for unknown id is correct; 5xx is not
—
pending
fee policy · /api/platform-fee-policy
PLATFORM_FEE_POLICY canonical record
—
pending
integrator config · /api/integrator-config
400 without a project_key is correct; 5xx is not
—
pending

the same, as data

/api/health/deep · every subsystem below, as JSON · cached 30s
/api/public/slo-summary · the latency row, with its window and scope · cached 30s
/api/metrics · lifetime per-route counters, Prometheus format
/api/federations · the federation directory · CORS open
/api/audit/divergences · every event re-checked against its published price
/recovery · the backup, the last snapshot, and how a restore runs

A signal that contradicts what we promise reads degraded or incident here, never "operational with caveats". Anchored envelopes keep verifying against Bitcoin headers when this page, or me.ochk.io itself, is down. Post-mortems land in /changelog.