Your VPN app stopped working: why unrelated apps fail on the same day

The app had been sitting on your phone for months and it worked. Today it says “Connecting…” and nothing follows. You go looking for what happened to yours — and notice that people are asking exactly the same thing about a dozen other apps that have nothing to do with each other.

A two-minute check: what exactly broke

Before you delete the app, reinstall it and buy another one, run three checks in a row. They split every possible cause into three different piles, and the piles are treated differently.

1. Wi-Fi versus mobile data. Turn mobile data off, turn Wi-Fi on and try the very same app. If it comes up, the problem is in the cellular network, not in the program. If it comes up nowhere, the cause is in the phone or in the service itself — the next two points.
2. A second such app on the phone. Open your app list and look for another one you installed “just in case” six months ago. Android allows exactly one connection of this kind, and while the slot is taken, a new app will never come up (details below).
3. The expiry of your key or subscription. In services where a Telegram bot hands you an access key, “it stopped working” often means literally that: the key has expired. The bot shows it, and reinstalling the app does not help.

The rest of the article explains why the first check so often settles the matter, and why several unrelated apps stop on the same day.

Why unrelated apps stop on the same day

This is the strangest part of it, and the most explainable. Different companies, different sites, different prices — and people ask about them on the same days, in the same words: stopped working, will not connect, none of them work.

The reason is that an app is a shell. Inside it is a way of talking to the server — a protocol. There are only a handful of protocols in circulation, and dozens of apps use the same ones. A filter in the network does not look at the program's name or its icon — it looks at what the first packet looks like when the app says hello to the server. That look is identical across every app using that protocol.

Hence the picture: once one way of speaking is recognised, everything that uses it stops on the same day. Your app is intact, the service's server is alive, your money is untouched — and “Connecting…” hangs.

So the “change the port” advice you will get on any forum usually misses. A port is the number on the door. You are recognised not by the door, but by how you knock.

What we know about other services — and what we do not

Plainly, so there is no misunderstanding later. We have measured no third-party app and no third-party server. We do not have their keys, their subscriptions or their logs. Everything we can say about someone else's service is what that service says about itself — and we write it that way: they say.

• Some of them describe themselves as clients for the v2ray and vless protocols.
• Others name IKEv2 and L2TP/IPsec on their own site.
• Several are built around “take an access key from a Telegram bot and paste it into the app”.

The difference between “a v2ray/vless client” and “IKEv2/L2TP” is exactly the difference in the way of speaking. It explains why apps stop in groups rather than all at once: one day the ones speaking one way go down, another day the ones speaking another. If you have two apps on your phone and one works while the other does not, that split is what you are looking at.

What we do not know and will not invent: what the carriers changed and when, and what happens inside somebody else's service. We cannot see their settings. Anyone who names you the exact date and the exact cause of someone else's outage is guessing.

What our own log shows for those days

We cannot speak for other people's apps, but we can speak for ours, with numbers. This is our connection log: our people, our app, our servers. It begins on 21 August 2026 — we promise nothing deeper than that.

Three things follow from that table, and all three disagree with what is usually written on days like these.

• Connecting does work. When a person presses the button themselves, 557 attempts out of 566 succeed — 98.4 %, against almost the same 98.9 % in August. Our numbers do not support the picture of “nothing connects”.
• What breaks is the life of the tunnel. Attempts to revive an already-established but silent connection tripled — 344 against 123 — and they succeed noticeably less often: 61 % against 77 %. A person sees this as “connected but nothing loads” and as “it worked for half an hour and dropped”.
• Every eighth successful connection in September did not take the direct route. 97 of them came up only because the app moved to a backup path on its own: 81 times over a bridge, 16 times through a transit inside Russia. For an app with a single route, those 97 connections would have looked like “not working”.

One more small but relevant number: the flag “another such app was already running on the phone at the moment of the attempt” arrived 10 times from 6 people in September. A tiny sample — no percentages can be built on it — but the phenomenon is real, and it is exactly what the next section is about.

Android has one slot, and a forgotten app is holding it

Android allows exactly one connection of this kind on a phone. While the slot is held by another app — the one you installed six months ago, tried once and forgot to remove — a new one will never come up. Not “slowly”, not “sometimes”, but never. And the person sees exactly what they see: “Could not connect”.

This is the most common reason why “the new app does not work either”. You installed the second app because the first one stopped — and the second will not come up, because the first one is still holding the slot.

What to do. Disable or delete what you do not use and try again. In our app the same thing is reported by the “Check connection” button in settings: it walks every step and names the one that failed. The full write-up of “it connected but there is no internet” is a separate article; “it drops by itself after half an hour” is this one.

“But I paid for it”: keys, subscriptions and money

Paying does not buy an exemption from a filter. It buys an uncrowded server, support and updates — honest things worth paying for. But money cancels none of the three mechanisms above: the Android slot stays single, the shape of the first packet stays the same, a weak signal stays weak. The full write-up is “A paid VPN is not working”.

On the “key from a bot” model specifically: if access is granted by a key with an expiry date, then “it stopped on one particular day” has the dullest possible explanation — the term ran out. Before you switch services, look into the bot that gave you the key.

And on buying blind. Whether a particular service works for you is a property of your network: your SIM, your neighbourhood, your evening hour. That can only be checked on the spot and in advance. This is why our trial is free and needs no card — so that “it will not come up” happens before the payment, not after.

What to do, in order

1. Try again. Dull, but it works: in our log for 3–8 September, of 91 failed attempts 60 ended in success on the very next attempt by the same person, without a single setting changed.
2. Run the Wi-Fi check (point 1 at the top). It halves the causes in a minute.
3. Remove the second such app from the phone — there is one slot.
4. Check the expiry of your key or subscription where you got it.
5. Update the app. A way of speaking that the network has learned to recognise can only be changed by a new build — in the old one it physically does not exist.
6. Take something that can try several routes. One route is one point of failure; in our September numbers a backup path saved every eighth successful connection. How the ladder works — three routes to the server.

What these numbers do not say

We try to make sure nothing more can be read out of our numbers than is in them.

• This is not a ranking of apps. We did not compare other services with each other and cannot say which is better: we are not able to measure someone else's app.
• Our log is our people. 29 people in September is few. Shares built on such a sample show a direction, not a verdict.
• The network measurements are Moscow, late July 2026, one phone. We never tested Tele2 at all — why that matters.
• We do not know what the carriers changed. A coincidence in time is a coincidence in time, not a proven cause.

Short answers

My VPN app stopped working — what should I do? First check the same app over Wi-Fi and look for a second such app holding the Android slot. If your access comes as a key from a bot, check its expiry too.

Why did several different VPN apps stop on the same day? Because there are many apps and few ways of speaking. Once one protocol is recognised, everything using it goes down together.

Will reinstalling the app help? On its own, almost never. What helps is updating — a new build may change the shape of the first packet, which the old one simply does not have. Reinstalling the old version changes nothing, and if the reinstall refuses to go through at all, the reason is usually the file or its signature rather than the connection.

What about moving to port 443? We tested that separately on three networks: it does not help. What decides is not the number on the door but how you knock  — the measurement.

It works for a friend on the same network, but not for me. Then the network is not the cause. Compare app versions and check whether your slot is taken by another app.

Do your numbers hold everywhere? No. The attempt shares come from our own log for 21–31 August and 1–10 September 2026, for our people and our app. The network measurements are Moscow, late July 2026. We have never measured anybody else's app.