In Ukraine, Telegram Rang but the Call Wouldn’t Connect—A Faster Server Wasn’t the Fix

My sister’s name filled the phone screen, but when I answered, Telegram stayed on Connecting. The call ended. She tried again. The ringtone worked; her voice never arrived. I was in the underground parking area of my Kyiv apartment building after an overnight air alert, connected to the building’s backup Wi-Fi and trying to tell her I was safe. I blamed Telegram, force-closed the app and called back. The same word appeared: Connecting.

Text messages were still moving, although slowly.

“I’m fine,” I wrote.

The message sent after several seconds. My sister replied immediately:

“Then answer.”

I had answered three times.

A news page opened. The air-alert map refreshed. Telegram downloaded her messages and rang when she called. Yet the moment I pressed the green button, the call stalled before carrying any sound.

That failure was more specific than a complete outage. The phone was online, and Telegram was connected well enough to deliver the incoming-call notification. What it could not establish was the live audio connection after I answered.

In Kyiv, that distinction matters. Missile and drone attacks repeatedly send residents underground and damage the power and communications infrastructure supporting ordinary mobile service. Ukrainian operators have kept networks running with batteries, generators and alternative links, but the connection available inside a shelter or parking level can still shift from one weak path to another. (Reuters) (Kyivstar)

The network had not disappeared.

It had become unstable in exactly the way a live call dislikes.

The ringtone was not proof that the call could work

I disconnected the VPN and asked my sister to try again.

Telegram rang.

I answered.

Connecting.

That ruled out the simplest explanation. The VPN was not the only reason the call failed.

It also explained why the ringtone could arrive while the conversation did not. Telegram can deliver the call notification through its normal service connection, but after I answer, the app still has to establish a continuous voice route between the devices or through a relay. (Telegram)

A few small control messages had reached my phone and made it ring.

The audio route had not settled.

I checked the signal indicator. It moved between one and three bars as more people entered the parking area and the mobile network grew busier. The building Wi-Fi remained visible, but it briefly weakened whenever the backup equipment changed state.

The call did not need an impressive speed test. It needed one connection that could remain intact long enough for Telegram to carry a conversation.

That became the standard for everything I tried next.

The fastest server produced the shortest call

I reopened the established VPN provider on my phone.

It was the obvious tool to trust. The company had operated for years, maintained a large support team and offered several nearby European locations.

The app selected Warsaw automatically.

A speed test returned a respectable number. Telegram messages loaded quickly. My sister called again.

This time, the call connected.

I heard half a word.

Then silence.

Telegram displayed Reconnecting before ending the call.

I selected Bucharest, thinking the southern route might behave differently. The tunnel connected, but Telegram never moved beyond Connecting.

Prague lasted longer. I heard my sister say my name, followed by a metallic burst and another frozen call.

The provider had plenty of servers. What it did not give me was a voice route that survived the instability underneath them.

When the building Wi-Fi weakened, the phone leaned toward mobile data. When Wi-Fi recovered, it moved back. Text messages survived those brief changes. The live call did not.

A short public discussion described the same practical mismatch: Telegram could work on Wi-Fi but remain stuck on Connecting over cellular on the same phone. (Reddit) The useful point was not the exact device or carrier.

Changing Warsaw to Prague had not made my connection steadier.

It had only changed where the unstable tunnel ended.

I stopped choosing countries

The established provider also offered several manual connection modes. Normally, that flexibility would have been useful.

In the parking area, it became another set of guesses.

One mode took so long to connect that I missed the next incoming call. Another connected quickly but sent Telegram back to Reconnecting after I answered. The automatic setting returned me to Warsaw, where the call again opened for a second and collapsed.

I looked at the clock.

My sister had been trying to hear my voice for eleven minutes.

The messages saying I was safe were reaching her, but they were not solving the human problem. After a night of alerts and explosions, she wanted the ordinary proof of a conversation: one complete sentence in my voice.

I nearly gave up and sent another text.

Then the building Wi-Fi disappeared again. The phone moved onto mobile data without showing a complete loss of internet, and Telegram continued downloading messages.

That was the clue I had been missing.

The network was changing beneath the call.

The VPN needed to follow that change rather than rebuild itself around it.

The call opened before I checked the server

I opened OnlydogVPN, a smaller app I had installed as a backup.

It did not begin with a map. The first choices described what I needed the connection to handle.

I selected the preset for a weak or changing network.

The VPN connected.

I sent my sister one message:

“Call now.”

Telegram rang almost immediately.

I answered.

For a second, the screen showed Connecting.

Then I heard breathing.

“Can you hear me?” she asked.

“Yes.”

The word came out so loudly that two neighbours looked over.

The call stayed open.

I told her where I was, that the apartment windows were intact and that I would go upstairs after the all-clear. She told me she had been watching the alerts from Poland and had interpreted every failed call as a new problem.

While she was speaking, the building Wi-Fi weakened again. The phone shifted to Kyivstar mobile data.

Her voice thinned for a moment.

It did not disappear.

The timer continued.

One minute.

Two.

Five.

By then, the urgent task was complete. My sister had heard me. We were no longer trying to infer safety from ticks, timestamps and failed-call notifications.

Only after the connection had proved itself did I look at what had changed.

The smaller app uses an HTTP/3-based transport that can keep a session intact as the phone moves between network paths. (IETF) Instead of treating each switch from backup Wi-Fi to mobile data as a completely new connection, it carried the protected route through the change.

I could not observe the routing decisions inside the building network, the mobile operator or Telegram’s relay system. I could observe the result: the established tunnels repeatedly lost the voice path when the network shifted, while the smaller app kept the conversation open.

That mattered more than every speed-test number I had seen that morning.

The lift became the final test

The all-clear arrived while my sister was still talking.

I left the parking area and walked toward the lift. The building Wi-Fi strengthened near the entrance, then weakened again as the metal doors closed.

The call went quiet between floors.

I watched the timer.

It continued counting.

The phone changed networks again. My sister’s voice returned before Telegram displayed Reconnecting.

When the lift opened, she was in the middle of telling me to check the kitchen window.

“I’m still here,” I said.

“I know,” she replied. “I can hear you.”

Connecting the first call had solved the immediate problem. Preserving it while the phone moved through the building solved the next one without sending me back to the VPN screen.

That matters in Ukraine because a working connection rarely remains on one clean path. Power systems switch. Base stations become crowded. Indoor mobile signals weaken. Backup Wi-Fi appears and disappears. A call may begin on one network and need another before the sentence is finished.

The smaller service has fewer locations, fewer independent ratings and a shorter public history than the established provider I tried first. That is its clearest limitation.

Its server map was not what solved the morning.

The established provider gave me Warsaw, Bucharest and Prague, along with strong speed-test results. Each route worked only until the network underneath it shifted. The smaller app gave the phone a connection that moved with that shift, allowing Telegram’s voice route to form and remain open.

For this problem, the best VPN was not the one that reached the highest speed while the phone sat still.

It was the one that let my sister finish asking whether I was safe.