How this works: architecture, safety system, and the chaos engineering game

Fetching live status...
Network Topology
VPN Tunnels
NL ↔ GR budget 20ms
NL ↔ NO budget 20ms
NL ↔ CH budget 20ms
NL ↔ NO-DMZ01 budget
NL ↔ NO-DMZ02 budget
NL ↔ GR freedom 20ms
NL ↔ NO freedom 20ms
NL ↔ CH freedom 20ms
NL ↔ NO-DMZ01 freedom
NL ↔ NO-DMZ02 freedom
GR ↔ NO inalan 40ms
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 120ms
NL ↔ TX freedom 120ms
GR ↔ TX inalan 160ms
CH ↔ TX vps 140ms
NO ↔ TX vps 140ms
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 224ms
132.4s
MTTR
145 events / 7d
NL primary
Tunnels 12/12 up
Uptime 86.61%
Devices 127
GR secondary
Tunnels 7/7 up
WAN inalan
Uptime 92.00%
Devices 50
Alerts 1
NO transit
Tunnels 18/18 up
Uptime 100.00%
CH transit
Tunnels 7/7 up
Uptime 100.00%
TX transit
Tunnels 7/7 up
Uptime 100.00%
Cross-Site Latency (ms)
NLGRNOCHTX
NL20.020.020.0120.0
GR20.040.055.0160.0
NO20.040.020.0140.0
CH20.055.020.0140.0
TX120.0160.0140.0140.0
Failover Layers
1 BFD sub-second (~900ms)
2 BGP hold-time 30s (aggressive VTI timers 10/30)
3 ISP SLA-track default route (~6-10s)
No failover events recorded · MTTR 132.4s