VPS1 / de-james-vps1
No signal important tier-2 NodeSecond VPS, in a different provider region from VIN (Hetzner nbg1 against VIN's fsn1), running its own complete Coolify instance. Registered here because it is the estate's only second compute failure domain that has been proven to execute work. It is shared: another operator's watchdog agent has root on it, and it already terminates 13 public hostnames that are not this estate's. Nothing this estate depends on runs here yet.
- Last heartbeat
- never
- Signal source
- jarvisos-agent
- Address
de-james-vps1.tail99ba7.ts.net- Location
- vps-provider-nbg1
- Target RTO
- 1h
Why it is no signal
- self No heartbeat has ever been received from this entity.
Capacity
Availability class
Degraded-tolerable · target 95%Second compute failure domain: a proven place to run work that is not the home rack and not VIN. Carries no estate service.
- Class
- tier-2 Degraded-tolerable: visible, nothing else at risk.
- RTO (declared)
- 1h
- RTO (achievable)
- 1h
- RPO
- —
- State
- none
- Redundancy
- single node
- Failover
- none
- Failure domain
- fd-vps-nbg
Health check: jarvisos-agent heartbeat every 300s — proves the node is running and reachable, and can still be given work.
Observed independently of the service.
Blind spot: Declared, not running. No JarvisOS agent is installed on this node — there is no /opt/jarvisos, no /etc/jarvisos and no jarvis unit on it — so this check has never returned anything and the node reads as unknown rather than healthy. Installing one is an owner decision about a machine another operator also administers, which is why it is a requirement and not a task. Until then the node's liveness is established by `jarvisos-independence.mjs probe`, on demand, by a person.
-
Note: An accepted risk no longer matches any finding. vps1An accepted risk for "single-node-unaccepted" no longer matches any finding; it can be removed.
Dependencies
blast radius: 0Depends on: none
Depended on by: none