How this works: architecture, safety system, and the chaos engineering game
VPN (active) eBGP K8s ClusterMesh Upstream DMZ
NL ↔ GR budget 40ms
NL ↔ NO budget 20ms
NL ↔ CH budget 20ms
NL ↔ NO-DMZ01 budget —
NL ↔ NO-DMZ02 budget —
NL ↔ GR freedom 40ms
NL ↔ NO freedom 20ms
NL ↔ CH freedom 20ms
NL ↔ NO-DMZ01 freedom —
NL ↔ NO-DMZ02 freedom —
GR ↔ NO inalan 50ms
GR ↔ CH inalan 55ms
GR ↔ NO-DMZ01 inalan —
GR ↔ NO-DMZ02 inalan —
NO ↔ CH vps 20ms
NO ↔ NO-DMZ01 vps —
NO ↔ NO-DMZ02 vps —
CH ↔ NO-DMZ01 vps —
CH ↔ NO-DMZ02 vps —
NO-DMZ01 ↔ NO-DMZ02 pair —
NL ↔ TX budget 115ms
NL ↔ TX freedom 115ms
GR ↔ TX inalan 155ms
CH ↔ TX vps 135ms
NO ↔ TX vps 135ms
TX ↔ NO-DMZ01 vps —
TX ↔ NO-DMZ02 vps —
27/27
VTI Tunnels
27 active
0/0
BGP Established
3
Failover Layers
DEGRADED
ClusterMesh
0 global svc
74ms
Avg Latency
p99 217ms
131.4s
MTTR
123 events / 7d
Tunnels 12/12 up
Uptime 88.00%
Devices 125
Tunnels 7/7 up
Uptime 92.00%
Devices 50
Alerts 1
Tunnels 18/18 up
Uptime 100.00%
Tunnels 7/7 up
Uptime 100.00%
Tunnels 7/7 up
Uptime 100.00%
| NL | GR | NO | CH | TX | |
|---|---|---|---|---|---|
| NL | — | 40.0 | 20.0 | 20.0 | 115.0 |
| GR | 40.0 | — | 50.0 | 55.0 | 155.0 |
| NO | 20.0 | 50.0 | — | 20.0 | 135.0 |
| CH | 20.0 | 55.0 | 20.0 | — | 135.0 |
| TX | 115.0 | 155.0 | 135.0 | 135.0 | — |
1 BFD sub-second (~900ms)
2 BGP hold-time 30s (aggressive VTI timers 10/30)
3 ISP SLA-track default route (~6-10s)
Last: WAN failover · Aug 27, 14:10 UTC · 123 events/24h
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.