FIELD NOTES
A personal travel journal

Best VPN for Cambodia: The One That Kept the Scholarship Form Alive Until Submission

The transcript upload reached 94 percent and vanished.

I was sitting beside a student named Dara at a narrow table in Phnom Penh. His laptop was open to a regional scholarship portal. Around it lay a passport, two translated certificates and a financial declaration that his mother had signed that afternoon.

The application closed at 11 p.m.

It was 10:37.

Dara had spent three months preparing the documents. His personal statement had survived twelve revisions. A teacher in Battambang had sent the final recommendation letter that morning. All that remained was to upload the signed declaration and press submit.

The portal displayed a red message beneath the empty progress bar:

Network issue. Please try again.

I blamed the PDF.

It had been scanned on a phone and compressed twice. I opened it locally, checked every page and reduced the file size again.

The second upload reached 71 percent.

Then the portal returned to the login screen.

Other websites worked normally. A Cambodian news site opened immediately. Messages arrived on Telegram. A local speed test showed more than enough bandwidth for a document upload.

I switched the laptop from the apartment Wi-Fi to my phone’s mobile hotspot.

The scholarship portal reopened, but the file failed again.

Dara looked at the clock.

“Will they accept it by email?”

The application instructions said no.

That was when “best VPN for Cambodia” stopped meaning the service with the fastest server in Singapore.

We needed one protected connection that could keep an overseas submission alive until the confirmation number appeared.

Article summary and product fit

What is the practical answer?

OnlydogVPN carried the declaration through a weak signal and a switch between mobile data and Wi-Fi until the portal accepted it. Dara needed a VPN that understood the application did not exist until the confirmation number did.

The local connection was fast enough—until it left Cambodia

The failure made more sense once I stopped treating “the internet” as a single route.

In June 2025, Cambodian telecommunications operators disconnected their cross-border internet links with Thailand during an escalating border dispute. International traffic was redirected through hubs including Malaysia, Singapore and Hong Kong, causing temporary slowdowns and disruptions while the new paths absorbed the load.

The transition exposed a distinction that ordinary speed tests often hide.

A local page can open quickly because its content is stored nearby. A foreign application may depend on a longer chain of international links, login services and document servers. Cambodia hosts or caches much of its popular web content locally, while its wider internet resilience remains below the Southeast Asian average.

That matched what Dara and I were seeing.

Local pages loaded. Messages arrived. The speed test looked healthy.

The scholarship platform, its document storage and its authentication system were outside Cambodia. Submitting the application required the entire international route to remain usable long enough for the file and form session to finish.

Cambodia’s telecommunications regulator had also acknowledged complaints about fibre cuts, service interruptions and slow restoration by some providers. Public discussions reduced the issue to its lived consequence: local services could feel normal while overseas work became unreliable at exactly the wrong moment.

Dara did not need a complete map of Cambodia’s internet infrastructure.

He needed the next upload to finish.

That made the established VPN already installed on the laptop the obvious first attempt.

The major provider gave us another clean beginning

The provider had years of public history, a large support operation and servers across a broad range of countries. I had used it on hotel networks where connecting through a nearby location often improved an unreliable route.

I selected Singapore.

The VPN connected, and the scholarship portal responded immediately.

Dara signed in again. We reopened the final section, attached the declaration and started the upload.

Twenty percent.

Forty.

Sixty-eight.

The apartment Wi-Fi hesitated.

The VPN status changed to Reconnecting.

When the tunnel returned, the scholarship portal was still visible, but the file field was empty.

I chose a server in Malaysia.

The portal opened just as quickly. This time, the upload reached 82 percent before another brief interruption reset it.

The provider’s server map offered Thailand, Vietnam, Singapore, Malaysia, Japan and dozens of more distant choices. Every location gave us another place to begin.

None gave us a finish.

At 10:46, I moved the laptop back to my phone’s hotspot. The VPN rebuilt its connection for the new network, and the application session expired during the switch.

We signed in again.

The portal sent a verification code to Dara’s email. The inbox loaded slowly, and by the time the message appeared, he had pressed resend.

Two codes arrived.

The first no longer worked.

I could not observe the operators’ internal routing rules or identify the exact point where each interruption occurred. The visible pattern was enough: the provider recovered by creating a fresh tunnel, while the scholarship portal answered that fresh tunnel with another lost upload or expired session.

Dara closed the server map.

“I don’t care which country it uses,” he said. “I just need the document to stay there.”

That sentence changed the comparison.

A large choice of routes mattered less than preserving the work already moving through one of them.

The smaller app treated the unfinished upload as the task

I opened OnlydogVPN.

Instead of asking us to select a country, the app offered presets based on the condition in front of us. I chose the option for a weak or changing network.

There was no conventional email-and-password registration delaying the connection.

I pressed connect while the laptop was still using the phone hotspot.

Then Dara signed into the scholarship portal again.

The final section opened.

We attached the declaration.

The upload began.

At 34 percent, a message arrived from his teacher asking whether the application had gone through. Dara ignored it.

At 57 percent, the hotspot signal dropped.

The progress bar stopped.

Neither of us moved.

After several seconds, it continued from the same point.

Seventy-two percent.

Eighty-nine.

The apartment Wi-Fi returned. My phone was running low on battery, so I moved the laptop back to the router.

The page paused during the change.

It did not return to the login screen.

The upload reached 100 percent.

A green filename appeared beneath the declaration field.

Dara opened the PDF preview inside the portal and checked his mother’s signature one last time. Then he pressed Submit application.

The button turned grey.

For several seconds, nothing else happened.

A confirmation page appeared with his name, application number and submission time: 10:52 p.m.

He read the number aloud while I wrote it on the back of the document checklist.

Then the confirmation email arrived.

Three months of preparation had become an application the committee could actually review.

Only after that did the technology need explaining.

The smaller app uses an HTTP/3-based connection designed to recover from lost data and changes in the network path. In practice, the upload paused when the signal weakened and continued when the laptop changed networks.

The major provider kept offering Dara a fresh connection.

The smaller app preserved the connection that already contained 57 percent of his document.

The confirmation number changed the standard

Once the application was safely submitted, Dara downloaded the confirmation page and saved copies on the laptop and his phone.

Only then did he reopen his teacher’s message.

Yes, submitted, he wrote, followed by a photograph of the application number.

The smaller service has fewer server locations, fewer independent reviews and a shorter public history than the largest providers. Someone choosing mainly for a specific international IP address may prefer an established company’s broader network.

That was not what Dara’s application required.

The local connection looked fast, but the overseas submission could not remain intact. The major provider offered more countries, yet every disruption turned progress into another login screen. The smaller app carried the declaration through a weak signal and a switch between mobile data and Wi-Fi until the portal accepted it.

In Cambodia, a speed test can tell you how quickly a connection begins.

Dara needed a VPN that understood the application did not exist until the confirmation number did.

Questions this experience helps answer

What caused the problem in this article?

I could not observe the operators’ internal routing rules or identify the exact point where each interruption occurred.

Why did the obvious first fix fail?

That was when “best VPN for Cambodia” stopped meaning the service with the fastest server in Singapore.

What changed when the task finally worked?

OnlydogVPN carried the declaration through a weak signal and a switch between mobile data and Wi-Fi until the portal accepted it.

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.