KPIs - Connections: ~37 attempts | Bytes: ~2.5 GB | Active peers: 3 of 16 (10 stale, 3 never connected) - Error rate peak: 0.004/s | Setup p99: 2450ms | Setup p50: 80ms | Restarts: 2 - Reliability: 7/10 — 2 proxy restarts, high tunnel_error count, persistent ENFORCEMENT-SUB errors, 2/3 testers offline iOS Client (last 24h) - Devices: 0 (tunnel_started) | Attempts: 37 | Success: 0% | WG errors: 0 | tunnel_errors: 444 (438 invalid_config, 6 adapter_start_failed) | Exceptions: 1691 Tester Health (last 24h) - Family 1: F1-20 ✅ traces active (inference 6-10ms) | F1-24 💤 no traces (last seen Mar 17) Rules: 5 events on Mar 17, none in 24h - Family 2: F2-27 💤 no traces (last seen Mar 21) Rules: 11 events thru Mar 20, none in 24h Findings (8 total — reply with numbers to create tickets) 1. 🟡 NEW ozone-proxy — 2 proxy restarts in 24h (22:19 and 06:55 UTC) 2. 🟡 NEW ozone-proxy — Persistent ENFORCEMENT-SUB missing required fields for device adf736f7 (~40+ errors, empty domains array) 3. 🔵 NEW ozone-proxy — Failed to get original dest errors (8x, operation not supported — known baseline) 4. 🟡 NEW ozone-proxy — Setup p99 latency spikes to 2.45s (baseline <500ms direct, correlated with residential proxy) 5. 🟡 NEW ios-client — 444 tunnel_error events (438 invalid_configuration, 6 adapter_start_failed), tunnel_started=0 6. 🟡 NEW ios-client — 1691 $exception events (1618 untyped, rest weekly/daily aggregation types) 7. 🔵 NEW tester — F1-24 and F2-27 zero VPN traces in 24h (devices offline) 8. 🔵 NEW ozone-proxy — Blocked connections steady 2/min baseline with spike to 0.58/s --- Notable changes vs yesterday's standup: - New: ENFORCEMENT-SUB errors for device adf736f7 — this wasn't in yesterday's findings. Worth investigating the empty domains array. - New: 2 proxy restarts — no restarts yesterday - iOS tunnel_error count jumped to 444 (438 invalid_configuration) — this is a significant signal - F1-24 and F2-27 still inactive — same as yesterday, now at 8 days and 4 days respectively