DAMM Backoffice
We care about the backend nodes because the user experience depends on them.
This page is the operator-facing counterpart to the install surface. It shows which gateways are actually healthy, how much headroom remains, where ingress and egress are thin, and whether the fleet is being treated like disposable noise or like maintained infrastructure.
1healthy gateways
2published recovery frontdoors
93%minimum gateway headroom
90%minimum egress headroom
Gateways
Ingress nodes
| Node | Provider | Region | Status | Load | Headroom | Frontdoors | Heartbeat |
|---|---|---|---|---|---|---|---|
| Berlin Edge 1 gw-eu-1 |
hetzner | eu-central | healthy | 7 | 93% | 2 / 2 | 1s ago |
Egress
Exit pools
| Pool | Provider | Region | Countries | Load | Headroom | IPs |
|---|---|---|---|---|---|---|
| EU Exit Pool 1 eg-eu-1 |
hetzner | eu-central | DE, NL | 10 | 90% | 2 |
Stewardship
What we are watching
- Do gateways keep fresh heartbeats, or are we publishing stale capacity?
- Do we still have alternate frontdoors before users feel a failure?
- Are free or demo users silently eating the same headroom paid users need?
- Are we adding nodes where the report shows real thinness, not where vibes suggest?
Recommendations
Current next moves
No urgent placement move is being recommended by the current report artifact. That can mean the fleet is healthy enough right now, or simply that the report lacks fresh enough demand or interference data.
Built from data/tracer-report.json at 2026-05-04T11:19:57.107Z.