The VPN said I was connected to India.
Telegram still would not open.
I was in Bengaluru, trying to download a clinical revision file from a private study group before an early hospital shift. The archive contained annotated scans from a teaching session I had missed, and the group administrator planned to remove it that evening.
Telegram had been temporarily restricted across India after authorities linked parts of the platform to scams surrounding the NEET medical entrance re-examination.
I opened a major VPN provider and chose India because it appeared first in the location list.
The app connected immediately.
Telegram remained on Connecting.
I switched from Wi-Fi to mobile data and tried again.
Nothing changed.
Then I opened an IP-checking page. It showed an Indian address, exactly as the VPN had promised.
That left me with a strange question:
If the provider offered India, why could it not give me a reliable server there?
The short answer
India’s 2022 cybersecurity directions required VPN providers operating local infrastructure to retain specified customer information for five years. ( Org ) Several major providers responded by removing their physical servers from the country while keeping India in their location menus.
The country label preserved the problem
The temporary Telegram restriction began on June 16, 2026, ahead of the NEET re-test. Authorities said fraudsters were using Telegram channels to sell fake exam papers and spread misinformation. (Techcrunch)
VPN demand rose almost immediately. Downloads of major VPN apps in India jumped from a recent daily average of about 139,000 to 208,000 on the day the restriction was announced. (Techcrunch)
Many people were making the same hurried move I had made: choose a country from the list, connect, and expect the blocked app to return.
My mistake was choosing India.
The VPN had encrypted the connection, but it had also given me an Indian IP address. To the network enforcing the restriction, I still looked like a connection from inside India.
The tunnel was active.
The location choice preserved the condition causing the block.
Once I understood that, the green Connected label stopped looking like proof that the route was useful.
“India” did not necessarily mean a server in India
The connection also felt slower than it should have. Its latency was unusually high, and one location tool briefly placed the same address in Singapore.
That led to the second part of the answer.
India’s 2022 cybersecurity directions required VPN providers operating local infrastructure to retain specified customer information for five years. (Org) Several major providers responded by removing their physical servers from the country while keeping India in their location menus.
They did this through virtual locations.
A physical server can operate in Singapore or the UK while assigning users an IP address recognised as Indian. Major providers describe this arrangement openly in their own support material. (Expressvpn)
For someone abroad who needs an Indian IP address, that can be useful.
For me, it created the wrong combination:
- the route could travel through another country;
- the address still appeared Indian;
- and the Indian restriction still applied.
The country tile was not answering, “Will Telegram work?”
It was answering, “What country will this IP appear to belong to?”
Those were very different questions.
I needed to leave the restriction, not appear local
I disconnected from India and selected Singapore.
Telegram’s chat list appeared.
For about thirty seconds, I thought I had solved it.
Then the messages stopped updating.
The 286-megabyte scan archive remained at zero. A voice note played for two seconds and returned to the loading animation.
I tried a second Singapore server.
The file reached 11 percent and failed.
The major provider offered plenty of alternatives, so I continued: the United Arab Emirates, Germany, the Netherlands, and the UK.
One route never connected.
Another loaded text but not media.
A third worked until I locked my phone, then failed to recover when I reopened it.
The provider itself had real strengths. It had years of public history, mature apps, extensive support, and a broad network.
But the country list had become a troubleshooting burden.
Every flag represented another possible route. None told me whether Telegram would remain usable long enough to finish the download.
Public discussions about virtual Indian locations often reduce the confusion to one practical question: is the server actually in India, or does it merely provide an Indian address? (Reddit)
For the file in front of me, that difference was decisive.
I did not need the correct flag.
I needed the archive.
A nearby country was not automatically a usable route
I had assumed Singapore would work because it was geographically close.
Internet traffic does not follow the neat lines suggested by a map. It follows the relationships between local providers, international links, and data centres.
A nearby server can still have a poor path. A more distant route can work better.
The restriction added another layer. When the local network recognised or disrupted the VPN connection itself, the server’s country mattered less than how the traffic reached it.
That was what my repeated attempts were showing.
The major provider had servers in the countries I selected. Under the connection mode available to me, none delivered a stable path for the Telegram file.
The green icon confirmed that a tunnel existed.
It did not mean the task could pass through it.
By then, the archive had failed four times.
The group administrator posted that the teaching materials would be removed in forty minutes.
That was when I stopped choosing countries.
The smaller app asked what I was trying to do
I disconnected the first provider and opened OnlydogVPN.
The interface did not begin with a world map. Its choices were organised around situations.
I selected the preset for a service being restricted or challenged by the current network.
Then I reopened Telegram.
The chat list updated immediately.
Three missing messages appeared at once. The voice note played from beginning to end.
I tapped the scan archive.
The download moved past 11 percent, then 20, then 50.
I left the phone on the desk and watched the progress bar continue without another server decision.
At 100 percent, I opened the archive and checked the first scan.
The annotations were present.
The task was complete.
Only then did the technical explanation matter. The smaller app used an obfuscated, HTTP/3-based route that passed where the familiar connections had stalled.
The visible result was simpler:
Telegram connected, the media loaded, and the file arrived before it was removed.
The route survived the next network change
A few minutes later, I packed my laptop and left the apartment.
The Wi-Fi disappeared in the lift, and my phone switched to 5G.
I expected Telegram to stall again.
The connection paused briefly, recovered, and continued synchronising without sending me back to a server menu.
That smaller moment gave me another reason to keep the app installed.
My problem had never been limited to finding a country outside India. I needed the connection to remain usable while an ordinary mobile device moved between networks.
The established provider repeatedly connected me to places.
The smaller app kept me connected to the task.
The India location still had a purpose
The virtual Indian option in the major provider was not meaningless.
Someone abroad may need an Indian IP address for a local account portal, news service, or streaming site. Operating the physical infrastructure elsewhere also lets a provider avoid keeping local servers under India’s retention rules.
The problem was the expectation created by the country name.
A location in a VPN menu tells you where the assigned IP appears to be. It does not tell you:
- where the physical server sits;
- how the traffic reaches it;
- whether the local network recognises the tunnel;
- or whether the destination will accept the route.
Those details become visible only when the connection fails.
That is how a provider can truthfully offer a country while providing no reliable server there for the task you actually need to complete.
The location exists.
The useful path does not.
A complete map was not the same as a working connection
The smaller service has fewer country locations, a shorter public history, and fewer independent ratings than the established provider I tried first.
Someone who regularly needs a precise national IP may still prefer the larger network.
That was not my problem that evening.
The major provider gave me an Indian address that preserved the restriction, followed by several foreign routes that could not keep the file moving.
The smaller app removed the country-selection guesswork, established the route Telegram accepted, and maintained it when the phone changed networks.
A VPN country is often only a label for where an address appears to be.
For the archive disappearing in forty minutes, reliability began when I stopped asking for a country and started asking for a connection that could finish the job.
Questions this experience may leave you with
What was actually causing the problem?
India’s 2022 cybersecurity directions required VPN providers operating local infrastructure to retain specified customer information for five years. ( Org ) Several major providers responded by removing their physical servers from the country while keeping India in their location menus. (Org)
Why did the obvious fixes fail?
The restriction added another layer. When the local network recognised or disrupted the VPN connection itself, the server’s country mattered less than how the traffic reached it.
What should you check first?
Every flag represented another possible route. None told me whether Telegram would remain usable long enough to finish the download.
What finally changed the result?
Only then did the technical explanation matter. The smaller app used an obfuscated, HTTP/3-based route that passed where the familiar connections had stalled.
What is worth remembering?
The smaller app removed the country-selection guesswork, established the route Telegram accepted, and maintained it when the phone changed networks.