Edge node management
Oracle edge register
The MVP edge surface is built around concrete evidence: heartbeat recency, config hash alignment, source/destination check posture, runtime publication state, and billable traffic concentration.
Operational thesis
A1 is enough only when the operator can see its limits.
This view keeps "MVP edge" honest: it highlights what is active, what is degraded, and which nodes carry the most billable traffic.
Edge node management
Existing edges
Loading…
Node digest
Loading…
Runtime checks
Hash alignment
Desired = published
Without this, operators cannot prove that a route failure belongs to code, config, or traffic.
HAProxy validation
Pass before reload
Malformed route templates must stop at render time, not at customer traffic time.
nft validation
Check before apply
A routed IP lane is only safe when rule compilation is verified before activation.
WG sanity
Peer config parses
Tunnel routes are operator-safe only when bad peer payloads fail locally and loudly.
Lane-specific blast radius
Not every outage is an "edge outage."
Tunnel IP
OCI route or WG peer drift
Customer sees black-hole traffic or missing real-IP visibility even while the control plane says active.
TCP Domain Proxy
SNI mismatch or PROXY v2 misuse
Edge remains healthy, but the customer mapped the wrong backend or enabled PROXY v2 against a raw TLS service.
Web
Cloudflare verification lag
Domain intake is shared, but activation depends on Cloudflare custom hostname lifecycle, not edge config publish.