The Best VPN Setup for My India Business Trip Wasn’t an India Server

The client portal displayed Unfamiliar sign-in detected for the third time while my board pack sat at 92 percent uploaded. I was in a Bengaluru hotel, trying to deliver a revised pricing proposal before a 9:30 supplier call. The trip was approved, the client knew I was in India, and the deadline was real. I blamed an expired authentication session, entered a new verification code and restarted the upload. Then my VPN reconnected through a different route, the portal signed me out, and the progress bar returned to zero.

The file itself was not complicated.

It contained a presentation, two spreadsheets and the final contract wording the client wanted to discuss on the call. Once the upload finished, I needed to open the secure data room, share my screen and walk three executives through the revised numbers.

I had twenty-two minutes.

The hotel Wi-Fi showed more than enough speed. My laptop was working. The client portal was online.

The problem was that my connection kept becoming a new connection.

Business travel had become a chain of digital approvals

Companies are sending more people back onto the road while moving more of the trip into digital systems. A 2026 Thomas Cook India and SOTC report found that many surveyed companies expected business-travel volumes to rise and were increasing their use of digital tools for booking, approvals and expenses. (Thomas Cook India and SOTC Travel)

That combination described my morning.

The flight, hotel and meeting had all been approved through separate online systems. The client workspace used another identity platform. The expense app was on my phone. Every part of the trip depended on a login recognising me quickly enough to let the work continue.

My location was not a secret.

The repeated changes in my network identity were the problem.

An India flag did not tell me enough

Before the trip, I had assumed the sensible setup would begin with the nearest server.

I was already in India, so I selected India.

That choice was less straightforward than it looked.

India’s CERT-In directions require covered commercial VPN providers to retain specified customer information. The official FAQ distinguishes those public consumer services from enterprise and corporate VPNs. (CERT-In) Several privacy-focused providers responded by removing physical Indian servers while continuing to offer Indian IP addresses through infrastructure elsewhere.

That did not make a virtual India location useless.

It did mean the flag in the app did not fully describe the route behind it.

For ordinary browsing, I might never have noticed. The client’s sign-in system noticed every change.

My laptop and browser stayed the same.

The network did not.

That was enough to turn a legitimate business trip into a sequence of “unfamiliar” logins.

The established provider kept introducing me again

I had used my major VPN provider for years.

It had a long public history, a large support operation and far more locations than I normally needed. Choosing it for an important business trip seemed reasonable.

The first India connection opened the client portal.

I completed the additional verification, entered the data room and started the upload.

The file reached 54 percent.

Then the hotel Wi-Fi paused for several seconds.

The VPN reconnected. The portal refreshed and asked me to sign in again.

I checked the connection details. The provider had moved me to another endpoint.

The country label still said India.

The client system saw a different network.

I verified again and restarted the upload.

This time, I manually selected the same location rather than relying on the automatic option. The board pack reached 71 percent before another brief interruption broke the session.

I tried a nearby Singapore route.

The connection was fast, but the portal treated it as another unfamiliar sign-in. After one more verification prompt, I reached the data room and discovered that the second upload had also been discarded.

The provider was protecting my traffic.

It was not preserving the working session.

That changed the comparison.

I no longer cared which server produced the best speed test. I needed the portal to stop meeting me for the first time.

Mobile data gave me the right country and the wrong stability

I disconnected from the hotel Wi-Fi and turned on my phone’s hotspot.

The portal recognised an Indian mobile network. After one verification, it opened normally.

The upload moved quickly through the first third.

For a moment, abandoning the hotel connection seemed like the answer.

Then the mobile signal weakened inside the room.

The progress bar slowed.

My test call began dropping words from every sentence. Moving the phone closer to the window improved the signal, but I could not leave it there and carry it into the meeting room at the same time.

People working around Bengaluru describe the same practical frustration: a phone may show service while calls and data still become unreliable. (Reddit) That matched what I needed to solve. The hotspot was useful, but it was not strong enough to carry the upload, video call and screen share alone.

The hotel Wi-Fi had the capacity.

The mobile network had the cleaner local identity.

I needed both without turning every switch between them into another login.

The backup started with the business task

I had installed OnlydogVPN^↗ before leaving home but had not made it my default.

The established provider had more ratings, more locations and a much longer public record. The smaller app’s shorter history was why I had kept it as a backup.

But the backup did not begin by asking me to choose another city.

It asked what I was trying to do.

I selected the option for sensitive work accounts on an unreliable public network.

The service established one route through the phone hotspot.

I signed in to the client portal.

It requested verification once.

I entered the code, opened the data room and started the upload again.

The file passed 25 percent.

Then 50.

Then the point where both previous attempts had failed.

At 94 percent, the mobile signal weakened.

The laptop rediscovered the hotel Wi-Fi and moved back to it.

The upload paused.

The VPN kept the working route in place.

A few seconds later, the progress bar continued.

It reached 100 percent and displayed a receipt with the file name and upload time.

I sent the receipt to the client.

Two minutes remained before the call.

The meeting completed the test

I opened the meeting link from the same browser session.

The client’s finance director joined first.

Then the procurement lead.

Then the managing director appeared and asked whether the revised figures were ready.

“They’re in the data room now,” I said.

I shared my screen.

The presentation opened without another login. I moved through the revised schedule, the currency assumptions and the final pricing table.

Halfway through the call, the hotel Wi-Fi stalled again.

The video froze.

This was the moment that had broken every earlier setup.

The laptop moved to the phone hotspot.

The call paused, then returned.

I was still in the meeting.

The data room remained open.

The presentation stayed on the same slide.

“Sorry,” I said. “The hotel network changed underneath me.”

The finance director nodded.

“Your screen is back. Continue.”

I reached the final page.

The managing director approved the proposal and asked procurement to begin the signature process.

That completed the task.

The board pack had arrived, the meeting had survived and the client had made the decision I had travelled to India to secure.

One consistent route mattered more than the nearest one

The service uses an HTTP/3-based connection designed to recover when the network underneath the device changes.

The result required little further explanation.

The established provider gave me many routes, but its reconnections repeatedly created new sign-ins.

The direct hotspot produced a straightforward Indian mobile connection, but it could not reliably carry the complete workflow.

The backup kept one work session intact while the laptop moved between them.

I could not observe the client identity platform’s internal risk-scoring rules. I could compare the visible result: one setup repeatedly demanded verification, while the other allowed the upload and meeting to continue.

For this trip, a consistent work identity mattered more than selecting the server geographically closest to the hotel.

The phone handled the smaller task that followed

After the client approved the proposal, the procurement lead sent a message asking me to confirm the legal entity name on the contract.

I had already closed the laptop and was walking toward the hotel lobby, where a car was waiting to take me to the airport.

The backup was installed on my phone but had not been configured.

Before packing the laptop, I displayed a device-verification code. I entered it on the phone and connected without creating another conventional email-and-password login.

The client message refreshed.

I confirmed the company name, approved the correction and received the signature notification before the car reached the main road.

That did not rescue the board meeting. The primary work was already complete.

It removed the next delay from the same trip.

The laptop had carried the proposal.

The phone kept the contract moving after the laptop was back in my bag.

The setup was not about hiding India

Nothing about the morning required pretending I was somewhere else.

The client knew I was in Bengaluru. My calendar showed the trip. The hotel and flights had been approved.

The goal was not to defeat company travel policy.

It was to stop ordinary network changes from making one legitimate business session look like a series of unrelated logins.

That was why the India server had been the wrong starting point.

The established provider remained the more familiar company. It had more locations, more reviews and years of public history.

The mobile hotspot remained an essential fallback.

Neither kept the complete workflow intact.

The smaller backup had fewer locations and a shorter record. It was also the setup that completed the upload, carried the client call and stayed usable when the laptop changed networks.

The best VPN setup for my business trip in India was not the route nearest Bengaluru.

It was the route that stopped my work identity from traveling while I was trying to finish the work.