Why a Server or Connection Protocol Sometimes Goes Temporarily Down

VPN blocking isn't a one-time event — it's an ongoing process. Deep packet inspection (DPI) systems regularly update the signatures they use to recognize VPN connections, and VPN providers respond by updating their masking parameters. Sometimes this back-and-forth creates a temporary window where a specific location or a specific connection method stops working on a particular network.

Why It Happens "Partially"

Blocks are almost never uniform across every ISP at once. Different internet providers within the same country run different DPI hardware, different signature versions, and roll out restrictions at different times. So the realistic picture looks like this: a location works fine on one operator, has intermittent issues on another at the very same moment, and the situation can flip the next day.

What We Do on Our Side

• We monitor the availability of every location and publish it live on the status page — no sugarcoating: if a location is down, it will show up there.
• When we detect sustained degradation, we change masking parameters on the server side (this doesn't require reinstalling the app on your end).
• We keep multiple locations running at once specifically so you always have a working fallback if one node gets temporarily caught by a block on your operator's network.

What to Do If a Specific Location Won't Connect for You

First, a simple checklist before contacting support:

• Check that location's status on the status page — if it's already showing red there, we already know and are working on it.
• Try a different location — if the issue is a block specific to your operator, another location will likely work right away.
• Update the app to the latest version — sometimes updated masking parameters require an updated client.

If none of that helps, that's exactly the case where it's worth writing to support: reports like these help us spot a targeted issue at a specific operator faster.