Server routes shown without marketing fog.
Foli uses active European directions and reserve routes. Server channels are provisioned from 1 to 10 Gbit/s; the speed you actually see still depends on your provider, route and device.
What “server speed” really means
A fast server does not guarantee a fast path from every mobile operator. That is why testing on your own network matters.
Server-side channel
Our server channels are provisioned in the 1–10 Gbit/s range depending on direction and role.
Your provider still matters
Peering, mobile filtering, DNS and regional routing can change the result even when the server is healthy.
Profiles can update
Use the subscription link so the client can receive current addresses and rules after route changes.
Honest routing notes
Good VPN support starts by saying what should not go through a tunnel.
Some should be routed directly or opened with VPN disabled if the app blocks VPN interfaces.
Use a current Foli route and refresh subscription before changing app settings.
Start with a reversible setup, ideally a separate Wi‑Fi network, not a whole-home forced tunnel.
How to choose a route without guessing
The nearest country is not always the best route. Mobile operators, peering, DNS behavior and service-level filtering can make a farther exit more reliable than a geographically closer one.
| Scenario | Try first | When to switch |
|---|---|---|
| General browsing, Telegram, YouTube | Germany or Estonia | High latency, unstable video, repeated timeouts |
| North-west Russia or nearby networks | Finland | Mobile data blocks a specific path |
| Russian banking or government apps | Direct route without VPN | The app asks to disable VPN or repeats verification |
| Home router | Separate Wi‑Fi network through VPN | The whole house loses access after a rule change |
When to report a server problem
Report it when the same subscription is current, the same client fails on two networks, or a route repeatedly connects but has no usable internet. Include route name, network type, time of test and the result from diagnostics.
How to test routes fairly
Run a fair server test with one device, one client and one subscription. Change only the route, then load the same website or service. If you change DNS, battery settings, client app and server country at the same time, the result is not useful. For video services, give each route a short warm-up; for messaging apps, test sending and receiving, not only opening the app. If a route works on home Wi‑Fi but not on mobile data, include the mobile operator in the support message because the server may be healthy while that provider path is not.
Final verification rule
Before you decide a VPN setup is fixed or broken, repeat the same small test twice: once on the network that failed and once on a second network if available. Keep the client app, route and subscription unchanged during that comparison. If the result changes only with the network, report the provider path. If it changes only with the route, report the route. If it never changes and the visible IP stays the same, focus on profile import or client application. This rule keeps support cases short and prevents accidental damage to a working configuration.