Postgres (replica)

No signal critical tier-1 Replica

Streaming standby for postgres-primary. Also the read endpoint for reporting queries.

Last heartbeat: never
Signal source: probe
Host: VIN / VPS
Replica of: Postgres (primary)
Target RTO: 45m

Recovery readiness20/100

Recovery procedure →

Why it is no signal

self No heartbeat has ever been received from this entity.

Capacity

Replication lag —

Data volume used —

Availability class

Estate-critical · target 99%

Streaming standby for postgres-primary; read endpoint for reporting.

Class: tier-1 Estate-critical: still serving, but a major capability or recovery is gone.
RTO (declared): 45m
RTO (achievable): 45m
RPO: continuous
State: durable
Redundancy: single node
Failover: none
Failure domain: fd-vps

Health check: TCP probe every 60s plus replication lag and disk metrics — proves the standby is up and streaming inside its lag threshold. Observed independently of the service.

Without it: Nothing serving is affected while the primary is healthy. What is lost is the primary's failover target — tier-0 Postgres silently drops to backup-only recovery, which is a 25 minute restore instead of a 10 minute promotion.

Full classification and SLOs →

Dependencies

blast radius: 0

Depends on VIN / VPS WireGuard (Home1 <-> VIN)

Depended on by: none