How to Keep Google Meet Stable While Traveling Internationally

Quick answer: A stable Google Meet call abroad depends on four things, in this order. You need decent signal, a short data route, enough bandwidth for your call type, and the right Meet settings. Most dropped calls on the road come from the route or the pipe, not the app. Plan for about 90 MB per hour for audio and 1–1.5 GB per hour for HD video. Keep a backup connection live during important calls.

Why Google Meet breaks when you travel

At home, your Meet calls run on a connection you’ve already tuned. Abroad, every part of that chain changes at once.

Your phone now rides a foreign network. Your data may travel to another country before reaching Google. Hotel Wi-Fi is shared with hundreds of guests. And your plan may slow down after a daily cap.

Most guides tell you to “check your internet.” That’s not much help at 7 a.m. in a Bangkok hotel with a client call in ten minutes. A better approach is to check each layer in turn.

The four-layer Meet check: Signal, Route, Pipe, Platform

I use this order because each layer depends on the one before it. Fixing your Meet settings won’t help if your data is taking a detour through Madrid.

Layer	What goes wrong abroad	Quick test	Fast fix
Signal	Weak indoor coverage, congested towers	Bars plus a speed test at your desk	Move near a window, or switch to Wi-Fi
Route	eSIM traffic exits in a far-away country	Speed test ping (latency)	Pick an eSIM that exits closer to you
Pipe	Not enough upload, or a throttled plan	Upload speed and plan status	Drop to lower video, or audio only
Platform	VPN, blocked UDP, wrong app settings	Meet’s “Troubleshooting and help” panel	Turn off VPN, update app, change network

Layer 1: Signal

This is the obvious one. Thick hotel walls and basement meeting rooms kill mobile signal fast.

Run a speed test from the exact spot where you’ll take the call. Not the lobby. Not the street. Your desk.

If signal is weak indoors, sit by a window. On Android and iPhone, you can also check which local network your eSIM has joined. Many travel eSIMs can switch partner networks manually in your phone’s network settings.

From my own trip: In Singapore on 12 October 2026, my eSIM first connected to M1. The speed test looked fine on paper: 96 Mbps download. But latency was 116 ms unloaded and 173 ms under load. That’s enough delay to make people talk over each other on a call.

So I switched to SingTel manually in my phone’s network settings. Same city, same eSIM, different partner network. The difference was dramatic.

Metric	Starhub	SingTel
Download	96 Mbps	150 Mbps
Latency (unloaded)	116 ms	18 ms
Latency (loaded)	173 ms	37 ms
Upload	~13 Mbps (test still running)	26 Mbps

Latency dropped by roughly 85%. Download speed only rose by about half. For Meet, the latency drop is what matters.

The lesson: a big download number tells you little about call quality. Check latency, and if your eSIM lets you pick another local network, try it before you blame the app.

Layer 2: Route (the problem almost nobody talks about)

Here’s what most Meet guides miss. With many travel eSIMs, your data doesn’t go straight to the internet in the country you’re in. It’s carried to an “exit point” first, which can be on another continent.

That detour adds delay. Ookla’s 2026 analysis of travel eSIM performance found a striking example in Japan. On the same local network, latency ranged from 54 ms with a local exit to 543 ms when traffic went via Madrid (Ookla).

Half a second of delay is brutal on a video call. People talk over each other. You answer questions that were asked a moment ago.

Ookla also found latency ranged from 1.5 to 30 times local levels across the brands it measured (ISPreview summary). Its conclusion was simple. The best travel eSIM for a trip is the one whose exit door is closest to where you are.

How to check your route in 30 seconds:

• Open a speed test app on your eSIM connection.
• Look at the ping or latency figure, not just download speed.
• Under 100 ms feels natural on a call.
• Between 150 and 300 ms is workable but noticeable.
• Over 300 ms, expect people to talk over each other.

For reference, the ITU’s G.114 guidance treats one-way delay under 150 ms as good for live conversation (ITU-T G.114).

Layer 3: Pipe (bandwidth and your data plan)

Meet needs more upload than most people expect. Your camera sends video up, and hotel and mobile connections are often weakest on upload.

Google publishes these per-person bandwidth figures for individuals and small teams (Google Workspace Help):

Call type	Upload	Download
Audio only	100 Kbps	100 Kbps
720p video	Up to 1.7 Mbps	Up to 1.7 Mbps
1080p video	Up to 3.6 Mbps	Up to 3.6 Mbps
Group meeting	250 Kbps and up	Up to 4.0 Mbps

If your network can’t keep up, Meet lowers the video quality on its own. That’s why calls often go blurry before they freeze.

How much data does Google Meet use per hour abroad?

I converted Google’s bandwidth figures into hourly data. These are ceilings, so real use is usually lower.

Call type	Worst-case data per hour	Hours per 1 GB (approx.)
Audio only	~90 MB	~11 hours
720p one-to-one video	~1.5 GB	~40 minutes
Group video (receiving up to 4 Mbps)	~1.9 GB	~30 minutes
1080p video	~3.2 GB	~20 minutes

Real-world tests land lower. Techloy ran the same scripted call across apps on one iPhone. Meet used data at a rate of about 585 MB per hour (Techloy).

My planning rule: budget 1 GB per hour of video meetings and 100 MB per hour of audio calls. Then add 20% for screen sharing and reconnects.

So a work trip with five one-hour video calls needs roughly 6 GB just for Meet. That’s before maps, email and everything else. Check our guide on how much data you need for travel before you pick a plan.

The unlimited plan trap: what happens after you’re throttled

This one catches business travellers out. Many “unlimited” travel plans have a fair-use limit.

BazTel’s unlimited plans, for example, give 2 GB a day at full speed. After that, speed drops to 512 Kbps until the next day. Other providers use similar caps, so read the fine print on yours.

Here’s what 512 Kbps means for Meet:

• Audio-only calls: fine. Google’s figure is 100 Kbps each way.
• One-to-one video at low resolution: possible. A 180p video tile needs about 80–200 Kbps (Google).
• 720p video, group calls or screen sharing: expect freezing and blur.

The fix is timing. If your big call is at 4 p.m., don’t stream Netflix on the train at noon. Take your important calls early in the day, before your full-speed data is used up.

Layer 4: Platform (Meet’s own settings)

Once the network is sorted, Meet’s settings do the rest.

Use the built-in health panel. During a call, click the three dots, then “Troubleshooting and help.” It shows network stability over time and suggests fixes. A red dot on the menu button means Meet has spotted a problem (Google Meet Help).

Turn on “Limit data usage” on mobile. It’s in the Meet app settings. Google says it saves data, battery and processing power (Google Workspace Updates).

Switch off your VPN for the call. Google’s own network guide says VPNs add latency and can lower Meet’s audio and video quality. If your company requires one, ask IT about split tunnelling for Meet (Google Workspace Help).

Pick 5 GHz Wi-Fi. Google recommends 5 GHz over the busier 2.4 GHz band. Hotel networks often show both with similar names.

The hotel Wi-Fi problem (and why your eSIM can beat it)

Hotel Wi-Fi often looks fast on a download test but fails on calls. There are three common reasons.

First, it’s shared. At 8 a.m. every guest is uploading photos and joining calls.

Second, some networks block the UDP ports Meet prefers. When that happens, Meet falls back to TCP. Google notes this fallback can reduce overall meeting quality (Google Workspace Help).

Third, captive portals can log you out mid-call when your session expires.

A counterintuitive tip: leave mobile data on during Wi-Fi calls. Google says the Meet app uses a small amount of mobile data even on Wi-Fi. It does this to keep your call going if Wi-Fi drops (Google Meet Help). With an active eSIM, that safety net actually works.

Countries where Google Meet may not work

Some destinations restrict Google services or internet calling. Before you travel, check the rules for where you’re going.

• China: Google services are blocked on local networks. Plan ahead and confirm what your company allows.
• UAE: The UAE lifted restrictions on Google Meet and other work tools in 2020 (GSMArena). Traveller reports since then are mixed, so test before a critical call.
• Other Gulf states: Qatar and Oman have historically restricted consumer calling apps. Rules shift often.

Always follow local laws. If a work tool is restricted, ask your employer which approved alternative to use.

Your pre-call checklist (10 minutes before)

Print this or screenshot it. It’s ordered by what fixes the most calls first.

1. Run a speed test where you’ll sit. Check ping, not just download.
2. Confirm your plan status. Are you still on full-speed data today?
3. Close cloud backups, photo sync and streaming apps.
4. Turn off your VPN, unless your employer requires it.
5. Charge to at least 50%, or plug in. Video calls drain batteries fast.
6. Join from the green room first and check your camera and mic.
7. Have your backup ready: a hotspot from your phone’s eSIM, or the dial-in number from the invite.

What to do when a call starts breaking up

Don’t wait for the freeze. Step down early, in this order:

1. Turn off your camera. Audio keeps the meeting going.
2. Stop screen sharing and paste a link in chat instead.
3. Switch networks. Wi-Fi to eSIM hotspot, or the reverse.
4. Rejoin the call. A fresh connection often picks a better path.
5. Dial in by phone, if your invite includes a number.

Myth vs fact

Myth	Fact
Fast download speed means a smooth call	Latency and upload speed matter more for Meet
A VPN always makes calls safer and better	Google advises against VPNs for Meet because they add latency
Turn off mobile data on hotel Wi-Fi to save data	Meet uses a little mobile data as a backup if Wi-Fi drops
Two eSIMs on the same local network perform the same	Their exit points can differ, changing latency tenfold

How to choose an eSIM for video calls

Price per GB matters, but for Meet it’s not the first thing to check. Look for these, in order:

1. Exit point near your destination. Ask the provider, or test ping on day one.
2. A plan sized to your call schedule. Use the 1 GB per video hour rule above.
3. Clear fair-use terms. Know your daily full-speed limit before you rely on “unlimited.”
4. Quick setup. You don’t want to scan a QR code from a second screen at the airport.
5. Hotspot support, so your laptop can use it as a backup.

BazTel plans install with one tap, with no QR code needed, across 160+ countries. Browse eSIM plans for Japan, Thailand or Singapore, or see all destinations. Whichever provider you choose, test latency in your first hour on the ground.

Frequently asked questions

How much data does Google Meet use per hour?

Audio-only calls use roughly 90 MB per hour at most. Video calls typically use around 0.5–1.5 GB per hour, depending on quality and group size. Plan for 1 GB per hour of video.

What internet speed do I need for Google Meet while traveling?

For a 720p one-to-one call, Google lists up to 1.7 Mbps each way. Audio only needs about 100 Kbps. Latency under 100 ms matters as much as speed.

Why does Google Meet keep freezing on hotel Wi-Fi?

Usually it’s congestion, blocked UDP ports or weak upload speed. Try the 5 GHz network, turn off your VPN, or switch to your eSIM’s hotspot.

Is an eSIM good enough for Google Meet calls?

Yes, if it has good local coverage and a nearby exit point. Check the ping in a speed test. Under 100 ms is ideal for calls.

Should I use a VPN for Google Meet abroad?

Google recommends against it, because VPNs add latency. If your employer requires one, ask about split tunnelling for Meet traffic.

Does Google Meet work in China?

Google services are blocked on Chinese networks. Check your employer’s policy and local rules before you travel.