Overview

Status

Live health of the Wealthnow API, checked from our servers. Last checked 2026-09-23 06:58:17 UTC.

All systems operationalstatus.json

Components#

ComponentStatusLatencyChecked at
REST APIOperational58 ms2026-09-23 06:58:17 UTC
MCP serverOperational72 ms2026-09-23 06:58:17 UTC
API keys and authenticationOperational127 ms2026-09-23 06:58:17 UTC
DashboardOperational76 ms2026-09-23 06:58:17 UTC

What the statuses mean#

  • Operational: every check answered as expected, within its time budget.
  • Degraded: the component answers, but a check was slow, reported itself degraded, or failed while another check passed.
  • Down: no check answered as expected. A check with no answer within its time limit (5.0 s for the service checks) has failed.

What we check#

Checks run from our servers, all at once, and each result is reused for 60 seconds. None of them sends an API key, so none is billed. Latency is the time until the first response headers arrive.

ComponentCheckHealthy answerSlow after
REST APIGET https://firm.wealthnow.io/api/health200, reporting green2.0 s
REST APIGET https://firm.wealthnow.io/api/health/ready200, reporting green3.0 s
MCP serverGET https://mcp.wealthnow.io/mcp401, with a www-authenticate challenge2.0 s
MCP serverGET https://mcp.wealthnow.io/.well-known/mcp/server-card.json2002.0 s
API keys and authenticationGET https://keys.wealthnow.io/v2/liveness2002.0 s
API keys and authenticationGET https://mcp.wealthnow.io/.well-known/oauth-authorization-server2002.0 s
DashboardDashboard databaseAnswers a query1.0 s

Machine-readable status#

/status.json returns the same data in the shape of an Atlassian Statuspage summary, so monitoring tools can read status.indicator: none when everything is operational, minor when something is degraded, and major when a component is down. Each component's status is operational, degraded_performance, partial_outage or major_outage.

curl https://app.wealthnow.io/status.json

For what changed and when, see the changelog.