Stabilising a VPN service with 50,000+ users
An outside audit and stabilisation of a large VPN service: connections dropped, bridges came and went. All of it on live production, with no maintenance window.
50 000+ service users
147 nodes
≈20 TB traffic per day
0 minutes of downtime during the work
01Problem
50,000+ users, 147 nodes, around 20 TB of traffic a day — and a steady stream of complaints about drops. A rewrite was off the table: the job was to find the causes and steady what already ran, without taking production down.
02What was done
- 01The audit came first: I looked at the infrastructure without touching it.
- 02End-to-end connection quality checks across the key routes, with no new port opened to the outside.
- 03Found the causes of the drops and backed them with measurements.
- 04Fixes went out in stages, each with a result check and a way back.
03Outcome
- The causes behind the main complaints were found and confirmed by measurement within hours.
- The client ended up with a measurable picture of service quality.
- The work went unnoticed by users: not one switchover was spotted.
04Stack
- Linux
- Xray
- Prometheus
- Grafana
- nginx
Got something similar?
Tell me what you have now and where you want to get to — I will come back with a plan, timeline and price.
Discuss a projectPlace on the map