Home1

No signal critical tier-0 Node

Primary home compute node. Runs the JarvisOS control plane, the Postgres primary and internal DNS.

Last heartbeat: never
Signal source: jarvisos-agent
Address: uk-james-home1.tail99ba7.ts.net
Location: home-rack
Target RTO: 30m

Recovery readiness50/100

Recovery procedure →

Why it is no signal

self No heartbeat has ever been received from this entity.

Failover

mode: manual

VIN / VPS warm No signal

Degraded capacity: edge node has no bulk storage.

Capacity

CPU load —

Memory used —

Root disk used —

CPU temperature —

Availability class

Fleet-fatal · target 99.5%

Primary home compute node: control plane, Postgres primary, internal DNS.

Class: tier-0 Fleet-fatal: loss stops the estate or risks data. Everything else waits.
RTO (declared): 30m
RTO (achievable): 30m
RPO: —
State: rebuildable · held in postgres-primary
Redundancy: active / passive
Failover: manual → vin
Failure domain: fd-home-rack

Health check: jarvisos-agent heartbeat every 120s, observed from VIN — proves the host is alive and its agent can reach the console. Observed independently of the service.
Blind spot: Tunnel loss and host loss produce the same signal. Confirm from the LAN side before declaring a node outage.

Without it: Published routes on VIN keep serving. Anything hosted at home — control plane, Postgres primary, internal DNS — is down until the standbys are promoted.

A failover costs: None for the host itself; per-service data loss is that service's RPO.

Full classification and SLOs →

Dependencies

blast radius: 6

Depends on: none

Depended on by JarvisOS Control Plane Postgres (primary) Redis (cache / queue) Internal DNS

Hosted here JarvisOS Control Plane Postgres (primary) Redis (cache / queue) Internal DNS