VPN Standup | Mar 01 | Last 12h KPIs - Connection...
# ozone-vpn-reliability
o
VPN Standup | Mar 01 | Last 12h KPIs • Connections: ~9,000 | Bytes: ~1.5 GB | Active peers: 1 • Error rate peak: 0.63/s | Setup p99: 2,193ms | Restarts: 0 • Reliability: 5/10 — Production ozone-proxy and wgcm both appear fully inactive; staging is operational but experienced 6 hours of extreme dial latency and a DNS resolver incident. Findings (6 total — reply with numbers to create tickets) [1] 🔴 NEW ozone-proxy — Production ozone-proxy inactive — 0 tunnels and 0 connections for entire 12h window [2] 🔴 NEW wgcm — Production wgcm manages 0 peers while WireGuard interface shows 15 peers [3] 🟡 NEW ozone-proxy — Staging direct-path dial p99 saturated at 10s histogram ceiling for ~6 hours (0514–1116 UTC) [4] 🟡 NEW ozone-proxy — Staging DNS resolver burst — systemd-resolved misbehaving at 16:05 UTC [5] 🟡 NEW ozone-proxy — Staging setup latency p99 breaching 2s threshold at multiple points in the window [6] 🔵 wgcm — wgcm persistent low-rate error traces in Tempo (~2/hr, paired, throughout window) Reply with finding numbers to create tickets (e.g.
1 3
or
all
). Findings marked ⚠️ already have open tickets — new tickets won't be created for those unless you ask.
Finding details
r
3, 4, 5