Skip to main content
oryn

Oryn beta · Infrastructure

System status

Live platform liveness — API, database, and infrastructure health. Support-pipeline performance is at /trust/status; resolved-incident archive at /trust/incidents.

All systems operational

Services are responding within targets. No active incidents.

Last checked: Jun 24, 2026, 10:41 AM PT

Incident history · last 90 days

1 incident-affected day

Application core

  • API Operational 1 ms · checked 2m ago

    Request handling for the Oryn web + desktop clients.

    1d affected
  • Database Operational 34 ms · checked 2m ago

    Postgres — case data, ledger entries, audit log.

    No incidents

Cache & storage

  • Redis cache Operational 30 ms · checked 2m ago

    Session + rate-limit data. Degradation slows the app but does not lose data.

    No incidents

Security

  • Auth0 sign-in Operational 225 ms · checked 2m ago

    JWKS for verifying user sessions. Degradation blocks new logins.

    No incidents
  • ClamAV file scanning Operational 30 ms · checked 2m ago

    Antivirus scan of every uploaded document.

    No incidents

Observability

  • Sentry error tracking Operational checked 2m ago

    Visibility into errors. Degradation is non-customer-impacting.

    No incidents

Infrastructure disclosure (R-7)

Oryn is currently deployed in a single region (us-west2 / Railway). Multi-region redundancy and automatic failover are not available during beta. Planned: post-beta GA release. Downtime in us-west2 affects all users simultaneously. Off-region backups in Cloudflare R2 (separate cloud, separate credentials) protect data even when the primary region is unreachable.