VPN Keeps Disconnecting? Start With the Most Common Cause

Connects, drops a minute later, reconnects and works, drops again a while after — this kind of repeated dropping is more frustrating than never connecting at all, because every time it looks fixed. The cause is usually one of three things: the system killing the connection in the background, a brief drop during a network switch, or the node itself being unstable at that moment.

One thing worth settling before you start: an occasional single drop is not unusual, since any network has brief interruptions, and reconnecting once is completely normal. What is actually worth your time is several drops within an hour, or drops that need a manual reconnect every single time. The rule still holds: change one variable at a time. Change a system setting, the network and the node all together, and even if the dropping stops you will not know which change did it.

Start by telling the drops apart

Disconnects do not all look the same, and identifying which kind you have rules out most of the causes immediately.

• It drops after the screen is locked or the app sits in the background for a while, and you only notice when you come back: most likely the system actively killing the connection in the background. See cause one below.
• It drops for a moment right when you switch Wi-Fi, switch to mobile data, or bounce between the two: this is the network switch itself. See cause two below.
• Nothing changed, you are actively using it, and it just drops at no particular time: more likely the node being unstable at that moment. See cause three below.
• Once it drops, it will not reconnect no matter how many times you retry: this is not really "disconnecting" anymore, it is a different connection-layer problem. See VPN connected but no internet for that full sequence.

The first three are all "drops but reconnects," which is what this article covers. The fourth is a different problem entirely, so do not mix them up. The test is simply whether reconnecting succeeds: if it does, and it is just happening often, keep reading here; if reconnecting itself fails, read the article linked above instead.

Cause one: the system is killing it in the background

This is the single most common cause on phones. The system, trying to save power or memory, actively ends a background app's network connection — and the VPN client is one of those apps.

On phones, this is the usual case

Android, especially some Chinese manufacturers' custom skins, tends to run noticeably aggressive power management: a few minutes after the screen locks, a non-allowlisted app's network activity gets throttled or cut outright. The longer the screen stays locked, the more likely you come back to a dropped connection. iOS is comparatively lenient, but long lock periods or low-power mode can produce something similar.

On computers, it looks a little different

On a computer, the more common version is system sleep or a network adapter's power-saving setting: closing a laptop lid or letting it sleep cuts the whole network connection, which then has to be rebuilt on wake. That is a different mechanism from a phone's background restrictions, but the result looks similar; leave it idle for a while and it drops. Some laptops also throttle the network adapter automatically on battery power, which shows up as instability without it being obvious that a power setting is the cause.

Leave the device idle for a few minutes and check whether it reliably drops. If it drops every time, and the timing lines up with how long the screen was locked or the device was asleep, that confirms this cause.

On phones, add the VPN client to the background-activity allowlist or turn off battery restrictions for it: usually somewhere in battery or app-management settings. On computers, check the network adapter's power-management options and uncheck anything like "allow the system to turn off this device to save power." These settings only need changing once; they do not need touching again after that.

Cause two: a brief drop during a network switch

Switching from Wi-Fi to mobile data, or roaming between two Wi-Fi networks, briefly rebuilds the device's network interface, and the existing connection drops once during that process — this is normal. The actual problem is when reconnection does not keep up and the drop never recovers on its own.

Notice whether the drops consistently line up with a network switch: walking out of home Wi-Fi range, or a cell tower handoff in an elevator. If the drops correlate strongly with actions like these rather than happening at random, this is the cause.

A brief drop from a network switch does not need fixing: let the automatic reconnect finish, which normally takes a few seconds. If it stays disconnected for a while after switching, check whether the new network itself has a problem first (a newly joined Wi-Fi that needs a portal login, for instance) rather than repeatedly restarting the VPN client.

Cause three: the node was briefly unstable

Once background management and network switching are ruled out, most remaining drops trace back to the node or the route it sits on at that moment — a sudden spike in load, or a brief wobble somewhere upstream. This kind of drop usually has no pattern: nothing changed, it just dropped, and it recovers a little later on its own.

The test is simple: after a drop, switch to a node in a different region and watch it for thirty minutes to an hour. If the dropping stops, it really was the node. If it keeps happening just as often in a different region, the problem is not the node — go back and check the first two causes more carefully instead of trying a third or fourth node. For which region actually makes sense to sit on, Choosing a server location has fuller guidance.

Two causes that are easy to overlook

If the first three common causes are ruled out and the dropping still will not stop, there are two more possibilities that are not exactly rare but are easy to miss.

• A router's NAT table has a timeout: if a connection sits idle without sending data for a while, the router clears the entry, and the next bit of data looks like a fresh disconnect-and-reconnect. This kind of drop tends to happen after a stretch of no activity, and has little to do with the VPN itself.
• Security software or a firewall on a computer may reset a connection it does not recognise instead of letting it through, especially right after installing or updating one. Test by disabling it temporarily for a while; if dropping clearly decreases, that was it.

Neither of these is especially likely on its own, but if the first three causes did not solve it, they are worth testing one at a time — more productive than continuing to suspect the node. A router timeout can usually be eased by raising the connection-keepalive setting in the router's own settings (the exact option name varies by brand); if you cannot find it, a router that supports a custom NAT timeout is worth considering.

When to suspect the device itself

If the dropping only started after a specific system update, and everything was fine before that, suspect the update itself first rather than repeating every step above from scratch. An OS upgrade sometimes changes background-management policy or network-driver behaviour, breaking a setting that used to work fine. VPN stopped working after a system update covers exactly this case.

The same logic applies to a new device: if frequent dropping starts right after switching, check whether your old device's battery and network settings carried over — often the new device's power-saving defaults are simply stricter, and adjusting them fixes it with nothing wrong with the network or the account. These settings rarely migrate automatically, so two minutes checking on day one beats noticing the problem days later.

In summary

When dropping keeps happening, separate it into one of three kinds first: killed in the background, a brief switch-triggered drop, or a node that was briefly unstable. Each looks and gets fixed differently, and mixing them up just makes the search messier. If all three are ruled out, check the router timeout and security-software conflict in the corner above — both easy to overlook.

The most direct way to see fewer drops is to let the client handle reconnecting on its own instead of tapping through it every time. FastOrange tries to reconnect automatically after a drop, and switching nodes is just as quick. If you have worked through the order above and it is still dropping often, tell support roughly when it happens: a fixed time of day, or right after a specific action — that is more useful than continuing to test it yourself.