Status

No public uptime history yet.

Nothing is deployed publicly, so there is nothing to measure and no history to show. We would rather say that than show a green badge that means nothing.

  • No public instance
  • No uptime history
  • No SLA

What we can honestly say.

Today

  • No public deployment of the app, the API or this site.
  • No status history, uptime figure or incident log. None has been recorded.
  • No uptime target, support SLA or on-call rota. Alert routing is not wired up.
  • No third-party status service is used, and none is embedded here.

When there is a public instance

  • This page will link to a real status feed and say when monitoring began.
  • Uptime will be reported only from measurements, with the period they cover.
  • Incidents will be listed with what happened, not just that they ended.

What the health endpoints mean.

If you run Orynt yourself, the API exposes two probes for your own monitoring or orchestrator. They are public and need no credentials.

GET /health/live

Liveness. The process is up and answering. It returns 200 with {"status":"ok"} and checks nothing else. Use it to decide whether to restart the process.

GET /health/ready

Readiness. It checks that the database answers a query and that no migrations are pending. If both are fine it returns 200 with "status":"ready". Otherwise it returns 503 with "status":"not_ready". Use it to decide whether to send traffic.

response shape
GET /health/ready

200 {"status":"ready","checks":{"database":"ok","migrations":"ok"}}

503 {"status":"not_ready","checks":{"database":"unavailable","migrations":"unknown"}}
# migrations can also read "pending: <names>"

What “ready” does not tell you.

It does not check your wallet connection, the billing provider, email, webhook delivery, or whether any payment is stuck. A healthy API can still have a payout that says checking. For payments, look at the app's overview and incidents, and see what to do when a payment is checking.

What is monitored publicly.

Components and whether they have public monitoring
ComponentWhat it isPublic monitoring
Marketing siteStatic pages served by the same API process as the app.None
Web app (/app)The product interface.None
API (/v1)REST API, webhooks, receipts.None
Customer walletsOwned and run by you, not by us. Orynt can only report what the wallet tells it.Not ours to monitor
Billing providerSandbox provider only; live providers are not commissioned.None
Email deliveryNot commissioned; mail is queued, not delivered, by default.None
Webhook deliveryAt-least-once with backoff; each endpoint has a delivery log in the app.Per-endpoint log only

Something not working?

Tell us. Contact support and include the request_id from any error. Do not include credentials, seed phrases or private keys.

Want to try it where you can watch it?

Run it locally with the practice wallet, or on regtest, and point your own monitoring at the health endpoints.