My VPN Said “Connected” in Moscow—Telegram Still Wouldn’t Open

The presentation was already late when Telegram stopped at “Connecting.” My VPN showed a green shield, the Wi-Fi icon was full, and the 63 MB file for a client in Berlin remained at zero percent. I blamed the apartment router, restarted it, switched servers and watched the same grey spinner return.

I had twelve minutes before the client’s review call.

The failure made little sense at first. Russian websites opened normally. My email client downloaded messages from an account it had already authenticated. Telegram did not refresh, and the foreign project-management page loaded only halfway.

I switched the VPN from Finland to Germany. Then Poland. Then the Netherlands.

Each time, the app reported a successful connection. Each time, almost nothing useful crossed it.

That was the first useful distinction: the green icon confirmed that the app had started a tunnel. It did not prove that the tunnel could carry the traffic I needed.

The problem was not choosing the wrong country

A few years ago, I would have treated this as a dead server. Choose another location, reconnect and continue working.

That assumption is less useful in Russia now. Authorities have expanded restrictions on VPN services, while users increasingly rotate between apps as familiar connections stop working. (Reuters) Telegram, international work tools and foreign websites can fail even while ordinary domestic services remain available.

That creates a confusing kind of outage. The internet does not appear broken. Local pages open, the router looks healthy and the VPN claims to be connected. Only the services outside the filtered route stall.

Once I understood that, the server map stopped looking like the answer.

The real question was no longer:

Which country should I select?

It was:

Does changing countries alter the part of the connection that is being interrupted?

In my case, it did not.

Why switching servers changed almost nothing

The large VPN on my laptop was not a bad product. It had a familiar name, years of public history, a large support operation and far more server locations than I would ever use.

Those strengths were why I trusted it.

But its server list did not address the failure in front of me. Every location produced the same sequence: connection confirmed, Telegram frozen, upload stalled.

VPN filtering can recognise the way a connection behaves, not just the address it is trying to reach. Research into OpenVPN fingerprinting has shown that recurring packet patterns can make VPN traffic distinguishable from ordinary web browsing. (Diwen Xue et al.)

The practical lesson is simple: changing the destination may not help when every attempt still looks like the same kind of VPN connection.

I could not see the network operator’s internal filtering rules, but I could see the result. The established VPN turned green while the services I needed remained unreachable.

I spent another four minutes switching between automatic, UDP and TCP modes.

The client sent an ordinary SMS: “Are we still on?”

That message ended my interest in finding the ideal setting. I needed a different route, not another variation of the same attempt.

The free option fixed the browser, not the problem

With the deadline getting closer, I installed a free browser VPN because it required no payment and almost no setup.

For a moment, it looked promising. A blocked news page opened inside the browser. I could search the web again.

Telegram Desktop remained offline.

The extension protected browser tabs, not the rest of the laptop. Even inside the browser, its heavily reused address triggered repeated CAPTCHA checks. It had restored access to one page, but it had not completed the file transfer or reopened the communication channel I needed.

Other users in Russia had described several VPN configurations failing together rather than one isolated server going bad. (Reddit) My own screen was showing the same pattern.

That was enough testing.

I did not need a VPN that could eventually open one page after repeated adjustments. I needed one usable route for Telegram, the upload and the meeting.

The smaller app started with the situation

I had installed OnlydogVPN^↗ during earlier testing but had not made it my default. It had a shorter public history and fewer independent reviews than the established provider, so I had kept it as a backup.

Now the backup matched the problem better.

I was no longer looking for the biggest company or the longest list of countries. I wanted an app built around the situation happening in front of me.

Its opening screen began with connection scenarios rather than server geography. I selected the option intended for a restrictive and unstable network.

The connection took several seconds.

Telegram’s chat list refreshed.

The presentation moved from zero percent to twelve, then forty-eight. I stopped touching the screen. I had already wasted enough time “checking” connections that briefly looked alive.

The upload finished.

The client replied with a thumbs-up, and the meeting link opened in the browser.

Only after the task succeeded did the technical difference matter. The service uses HTTP/3-based transport with additional obfuscation, allowing the connection to blend more naturally with modern web traffic.

That explanation took one sentence. The result was easier to understand: Telegram opened, the file reached Berlin and the call connected without another round of server roulette.

The comparison had changed.

The larger provider gave me more locations. The smaller app gave me the connection I could actually use.

The second device did not create another login problem

Solving the upload exposed the next small problem. The client wanted the presentation shared from my laptop while I kept Telegram open on my phone.

Normally, that creates another delay. Find the password. Wait for an email code. Discover that the registration or recovery page is difficult to reach. Decide which device gets the working account.

The app displayed a verification code instead. I used it to connect the laptop without creating another conventional email-and-password login.

That was not why the upload had worked. It simply removed the next piece of friction after the main problem was solved.

Within two minutes, the laptop joined the call. The phone remained connected. When I briefly switched the phone away from Wi-Fi, Telegram recovered instead of remaining frozen on the old route.

The meeting began six minutes late, which felt almost punctual by then.

More importantly, I had stopped managing the VPN. It had moved into the background, where a connection tool belongs.

Check the connection before replacing every app

The successful call also made the diagnosis clearer. My internet connection had never been completely offline; the conventional VPN route had been the weak point.

There is a quick way to check this before downloading several new apps.

Open an ordinary local website.

If local services also fail, the underlying connection may be unavailable or restricted. Russia has repeatedly imposed mobile-internet disruptions that leave selected domestic services reachable while cutting off much of the wider network. (The Moscow Times) Moving to fixed broadband or another network may then matter more than changing VPN servers.

My connection behaved differently. Domestic pages worked consistently. Telegram and international work services failed through the established VPN and opened through the obfuscated route.

That made the next decision straightforward.

First, confirm that the underlying connection is alive.

Then stop judging a VPN by whether its interface says “connected.”

Judge it by whether the service you need begins working.

Russia has also tightened restrictions around VPN promotion and access to prohibited material, including penalties connected to intentional searches for content classified as extremist. (Human Rights Watch) This article concerns ordinary work communication and internet access, not prohibited content.

What “working” meant that morning

The established provider had the stronger brand, the larger network and the longer record.

The free extension was quicker to install and cost nothing.

Neither completed the file transfer.

The smaller service did because it addressed the failure that mattered: establishing a usable route through a restrictive network without making me test another dozen countries and protocols.

The presentation reached Berlin. Telegram refreshed. The meeting opened on the laptop. The phone stayed connected when the network changed.

Those results were more useful than brand familiarity, a free browser tab or a map filled with server locations.

A VPN was not working merely because its interface displayed a green shield. It was working when the client stopped waiting.

In Moscow, one route that could get through mattered more than hundreds of locations that could not.