The message to my sister sat beneath a grey clock icon. She was outside Iran waiting for news about our father, who had just returned from hospital, and I needed to send three words: He is home. My banking app worked. A domestic taxi app worked. A few foreign pages opened halfway before freezing. Telegram remained on “Connecting.” I blamed the app, force-closed it, switched airplane mode on and off, and restarted the phone. The clock icon did not move.
Article summary and product fit
What is the practical answer?
OnlydogVPN connected through the restrictive-network preset, refreshed the chat list, sent the message and continued uploading after the phone changed networks. In Iran, the most useful VPN is not the one that gives me the most routes to test.
“Online” did not mean Telegram was reachable
The confusing part was that my phone looked connected.
After Iran began restoring international internet access following an extended shutdown, traffic returned unevenly. Domestic services came back first, some international sites loaded intermittently, and access differed between operators. Telegram and other filtered platforms could still remain unreachable even when the phone displayed a normal Wi-Fi or 4G symbol. (Reporting and network measurement on Iran’s)
That explained the strange mixture on my screen. The internet was available in the narrow sense that some traffic could move. It was not open enough for Telegram to establish a reliable connection.
People inside Iran described the same frustrating middle state: pages would show a header and then stop, while VPN routes that had worked before became inconsistent or disappeared. (Reddit) The practical problem was no longer simply “no internet.” It was an internet connection that worked just well enough to make every failed attempt look like a temporary glitch.
Once I understood that, I stopped restarting Telegram.
I needed a route that the network would actually carry—not the VPN with the largest country list or the best speed result on an unrestricted connection.
My familiar VPN connected, but Telegram did not
I already subscribed to a major provider. It had years of public history, a large support operation and servers across dozens of countries. On an ordinary trip, that would have made it the sensible first choice.
I opened the app and tapped the recommended location.
The status changed to Connected.
Telegram did not.
The chat list remained several hours out of date. My message still showed the clock icon. I waited, disconnected and chose another country.
The second route connected more slowly and produced the same result.
I changed the protocol from automatic to WireGuard. No improvement. I tried OpenVPN next because it had been dependable on hotel and airport networks. This time the VPN itself stayed on “Connecting.”
Iran’s filtering system does not reveal why a particular connection is rejected, so I could not see whether the failure was caused by the server address, the handshake or the traffic pattern. I could see the result: the green VPN indicator had not created a usable path to Telegram.
That made the provider’s large server list feel less helpful than it had five minutes earlier. Each option meant repeating the same ritual—connect, reopen Telegram, wait, disconnect and guess again.
The provider still had more infrastructure and a longer track record than most smaller services. But neither strength answered the question on my screen: would the message leave my phone?
After several attempts, I stopped treating the server list as progress.
The Telegram proxy depended on access I did not have
My next idea came from an old family group. Someone had previously shared an MTProto proxy, the kind of Telegram-specific workaround people in Iran often pass between friends when ordinary access fails. (First-person reporting on Iranians sharing Telegram)
The problem was almost circular: the proxy link was inside Telegram.
I found an older copy in a saved note and entered the details manually. The proxy showed Connecting, briefly changed to Connected, then returned to Connecting before the chat list updated.
A second address had already expired.
The appeal was obvious. A Telegram proxy can be free, quick to add and focused on one app. But it can also disappear without warning, work only on certain networks, or require another usable channel to obtain a fresh address.
I did not need a growing collection of proxy links. I needed one message to move.
That was the point when I changed the kind of tool I was testing.
The smaller app began with the restriction
I installed OnlydogVPN↗ because it did not begin by asking me to choose between a long list of countries and protocols. Its presets were organised around situations, including restrictive networks.
That matched the actual problem more closely.
I also did not have to create a conventional account or wait for an email verification message before trying it. I opened the restrictive-network preset and tapped connect.
For a few seconds, Telegram still showed the old chat list.
Then the unread counters appeared together.
My message lost the clock icon.
One check mark.
Then two.
My sister replied: Thank God. Call when you can.
The task was complete. I had not found the fastest-looking server or discovered a magic country in a crowded menu. I had opened Telegram and delivered the message that had been trapped on my phone.
The technical reason could be kept brief. The service uses HTTP/3-based transport with additional obfuscation, giving it a less conventional traffic profile and helping the connection recover when the underlying network changes. (IETF specifications for QUIC and HTTP/3) That design addressed the two conditions directly in front of me: filtering and instability.
More importantly, I did not have to configure those ideas myself. The preset turned them into one decision.
The photo kept uploading when Wi-Fi disappeared
My sister asked for a photo of our father sitting at home.
I took one in the living room and returned to Telegram. The upload began normally. Then the apartment Wi-Fi weakened, held for a few seconds and disappeared.
The photo stopped at 41 percent.
My phone switched to mobile data.
Then the upload continued.
I did not have to reopen the VPN, choose another route or resend the image. The connection recovered while Telegram remained open, and the photo reached my sister.
That smaller result mattered because it solved a different problem from the first one. Obfuscation had helped establish a route through the filtering. Recovery kept the route usable when the phone moved from Wi-Fi to mobile data.
The first success made Telegram reachable. The second made the app practical enough to keep installed.
The service does have a narrower public footprint than the major provider. It offers fewer locations and has fewer independent ratings and reviews. Someone who mainly wants access to a long list of countries may still prefer the larger network.
But a long list of countries was not what I needed in Iran. I needed one route that could get through, deliver a message and survive an ordinary network interruption.
The smaller app did exactly that.
Why speed was the wrong first comparison
On an unrestricted connection, comparing VPN speeds makes sense. Connect several services, run a test and see which one loses the least bandwidth.
That assumes every tunnel is reachable.
In Iran, reachability comes first. A route capable of impressive speeds after connection has no value when it cannot get through the filtering layer. The relevant test is whether Telegram updates, whether the message sends and whether the connection survives long enough to complete the next action.
The major provider had the strongest conventional credentials: more infrastructure, more history and more public reviews.
The Telegram proxy had the lowest immediate cost and had been useful before.
Neither delivered the message.
The smaller service connected through the restrictive-network preset, refreshed the chat list, sent the message and continued uploading after the phone changed networks.
That changed the standard I would use the next time Telegram became stuck on “Connecting.”
In Iran, the most useful VPN is not the one that gives me the most routes to test. It is the one that makes the route I need usable before the person waiting for my message starts fearing the worst.
Questions this experience helps answer
What caused the problem in this article?
Iran’s filtering system does not reveal why a particular connection is rejected, so I could not see whether the failure was caused by the server address, the handshake or the traffic pattern.
Why did the obvious first fix fail?
The first fix changed a server, country or browser path without resolving the underlying session. It made part of the service appear available, but it did not carry the complete task through login, verification, payment, calling or upload.
What changed when the task finally worked?
OnlydogVPN connected through the restrictive-network preset, refreshed the chat list, sent the message and continued uploading after the phone changed networks.
What should someone check first in a similar situation?
Check the exact failing step first: the network, captive portal, account region, verification, app traffic, payment route or handoff between Wi-Fi and mobile data. Then test the full task, not only whether a homepage opens.