VPN state, activity, load, and headroom at a glance.
This panel is generated from the control plane report artifact rather than hand-written copy. It is meant to answer the first operator questions quickly: do we have healthy ingress capacity, what changed recently, and where is the next constraint likely to land.
Capacity is healthy enough for the current snapshot
Registered gateways are healthy, recovery endpoints are published, and the minimum headroom scores are comfortably above the alert band.
Current capacity surface
Gateways are published only when registration and heartbeat freshness are both intact. Egress pools remain separate so outbound capacity can be inspected independently.
Gateways
| Gateway | Status | Load | Headroom | Frontdoors | Heartbeat |
|---|---|---|---|---|---|
|
Berlin Edge 1
gw-eu-1 · eu-central
|
Healthy | 7 | 93% | 2 / 2 | 1s ago |
Egress Pools
| Pool | Countries | Load | Headroom | IPs |
|---|---|---|---|---|
|
EU Exit Pool 1
eg-eu-1 · eu-central
|
DE, NL | 10 | 90% | 2 |
Enrollment throughput and local resource profile
Published from data/benchmark-enroll-quality.json at 2026-04-20T16:48:32.472Z.
External interference wired into operator judgment
The permeability surface is where DAMM turns interference and weak reachability into something actionable. It tracks which user-network slices are degraded, which are effectively blocked, and whether the next move is to reweight, withdraw, or add ingress.
This is a placement and routing input, not a world map. The operator should read it as: where are paths weak, how replaceable are they, and what concrete capacity move should follow.
Two sampled zones show thin replaceability and one is effectively blocked against the only published provider-region slice.
Recent actions and longer-running state
The recent activity list is drawn from the admin audit trail. It is not a generic log dump; it is the operator-relevant tail.
-
admin_login
2026-04-21T07:52:11.691Z
tracer
-
gateway_register
2026-04-21T07:52:10.465Z
gw-eu-1 · gw-eu-1
The historical summary is deliberately compact. The point is to show drift and lifecycle events quickly, not to replace raw evidence files.
Metered clients and where to add capacity next
The top device list makes metered usage visible without needing to open raw state. Suspended devices surface here as an operator-visible condition rather than disappearing quietly.
| Device | Status | Gateway | Usage | Sessions |
|---|---|---|---|---|
|
tracer-laptop
66d3f8bd-25d8-4641-8d84-d135591f2d1b · standard
|
active | gw-eu-1 | 0.00 MB | 0 |
Placement recommendations stay heuristic for now. The immediate value is not perfect optimization; it is making the next ingress or egress decision legible from actual state.
No immediate expansion or repair action is being suggested by the current snapshot.