← Back to RiskState

Status

Independent uptime and latency monitoring for the RiskState API and web surfaces.

Monitored services

Risk State API (v1)API check
POST api.riskstate.ai/v1/risk-state

Core policy engine. Asserts HTTP 200 plus a valid policy payload (version, exposure_policy, max_size_fraction, policy_hash) — not just a reachable host.

Portfolio Risk State (v2)API check
POST api.riskstate.ai/v2/portfolio-risk-state

Portfolio aggregation — gross/net exposure, concentration, per-position assessment. Probed with a real authenticated request asserting 200 + an assessment.

Stress Scenario (v2)API check
POST api.riskstate.ai/v2/stress-scenario

Scenario / stress export — flash-crash, funding-blowout, depeg, cascade templates. Probed with a real authenticated request asserting 200 + a P&L result.

Market DataUptime
GET api.riskstate.ai/.netlify/functions/visualizer-data

Aggregated public market-data feed powering the visualizer.

Docs & Landing (riskstate.ai)Uptime
GET riskstate.ai

Public documentation, demo, and marketing site.

How we monitor

  • Provider: Checkly — an independent, third-party monitoring service running outside our infrastructure.
  • Locations: 2 global checkpoints (N. Virginia and Frankfurt).
  • Frequency: probes run every 5–15 minutes.
  • Depth: the v1 and v2 endpoints are validated with content assertions (they must return real output — correct version, an exposure_policy object, and a policy_hash for v1; a portfolio assessment / P&L result for v2), not merely a reachable host.
  • Alerting: email on failure (Telegram webhook optional).

Monitoring is independent of the RiskState application. A degraded or failing check here reflects real availability as observed from outside our network.