status

System status.

Live read from opchain.dev/api/health. Refreshes on load and every 60 seconds while the tab is visible.

checking…

contacting /api/health

API health

—

measuring round-trip…

Production version

—

SHA of the worker currently serving opchain.dev

Last checked

—

auto-refreshes every 60 s

What we measure

API health. A GET /api/health returning a 200 with status: "ok" means every edge-served route is reachable and the worker is running.
Version. The version field is the git SHA stamped at build time. Compare against the main branch to see if a deploy is pending.
Latency. Round-trip from your browser to the Cloudflare edge nearest you. Treat anything under 500 ms as normal; anything over 2 s suggests a regional issue.

If something is broken

Production breakages get reverted by hand on a developer laptop — there's no auto-rollback. The fastest signal that we're aware is a non-current SHA in the version card above.

Cloudflare incidents that affect opchain: cloudflarestatus.com
Open issues: github.com/asfbay-bit/opchain/issues
Report a new problem:

opchain.dev runs on Cloudflare Workers with a static Astro site served through the ASSETS binding. See how opchain.dev is built for the full stack and security for hardening posture.