Sea Current Tech
Connectivity, gadgets and digital life for people who work at sea

VoIP Apps That Survive Satellite Latency at Sea

Updated 24 August 2026 · connectivity, voip, starlink, crew-life

VoIP Apps That Survive Satellite Latency at Sea

Some links on this page are affiliate links. If you buy through them we may earn a commission at no extra cost to you — it never changes which product we recommend.

If you want VoIP apps that survive satellite latency, the honest answer is that the app matters far less than the link it runs on. On a low-earth-orbit link like Starlink, where published latency figures sit in the 20 to 70 ms range, almost every mainstream calling app behaves normally: Zoom, Microsoft Teams, Google Meet, WhatsApp, Skype and SIP-based business phone systems. On an older geostationary VSAT, where the round trip runs past half a second, no app fixes that. You pick a different tool for the job, usually text or voice notes.

That single split explains most of the frustration in a crew mess. Two engineers on the same ship, same app, wildly different experience, because one was calling during a quiet watch on the LEO terminal and the other was on the legacy VSAT while forty people streamed.

The number that decides everything: 150 ms

VoIP feels natural below roughly 150 ms of one-way latency and falls apart above it. RingCentral's QoS guidance says 150 ms is barely noticeable and generally acceptable, that anything above 150 ms adversely affects call quality, and that above 300 ms is generally unacceptable. A SonicWall configuration document published through RingCentral's support library recommends one-way latency under 150 ms, jitter under 100 ms and packet loss under 3 percent for usable voice.

Voice itself is cheap. A Starlink VoIP test article puts a voice stream at roughly 100 kbps and notes that voice tolerates latency up to about 150 ms before a conversation starts to feel delayed. That is why voice often works on a link that cannot load a web page: you need almost no bandwidth, you need consistency.

So "surviving satellite latency" has a concrete meaning. Can the app hold end-to-end delay under about 150 ms, with jitter and packet loss inside the numbers above? If yes, the call sounds like a call. If no, you get the classic satellite conversation where both people talk over each other and apologise for ten minutes.

Why jitter hurts more than raw latency

Steady latency is survivable, and variable latency is what makes people hang up. Your brain adapts to a consistent 120 ms gap within a minute or two. It cannot adapt to a link that runs at 40 ms, spikes to 300 ms when the dish is obstructed, then drops back. That variation is jitter, and it produces the clipped syllables and robot voice that crew blame on the app.

A Starlink and VoIP support article from Fusion IT describes exactly this pattern: latency typically 40 to 80 ms that can occasionally spike higher because of signal quality, congestion or dish positioning, producing slight delays, occasional voice clipping and echo. The same article notes blurry video, out-of-sync audio and brief dropouts in Teams, Zoom and Meet during congestion or obstruction, and points out that group meetings are more sensitive to packet loss and jitter than one-to-one calls.

Read that last part twice. A one-to-one WhatsApp call to your wife and a fourteen-person Teams meeting are not the same load on the link, even though both are "a call".

Latency by satellite type, and what it means for calling

Here is the comparison that actually decides which apps are worth installing. Every figure below comes from published third-party measurements, with the publisher and date named in the notes column.

Link type Reported latency Voice calls Video meetings
Starlink (LEO) 20 to 70 ms across multiple 2024 to 2026 reports Works, natural-sounding Works for most users
Legacy GEO VSAT (Viasat, HughesNet class) Beyond the 150 ms threshold, high enough to cause echo and delay Difficult Rated unusable

The Starlink numbers are consistent across sources. A Starlink latency guide from EarthSIMs reports average latency of 20 to 50 ms under normal conditions and typical VoIP calls landing at 25 to 45 ms, which it describes as sounding natural without perceptible delay or echo. A June 2026 review of Zoom over Starlink cites Ookla and Viasat data showing median latency of 48 to 70 ms in North America and Europe in early 2024, and concludes Starlink meets or exceeds Zoom's recommended requirements for high-quality video calling. A March 2026 satellite comparison from Orbital Radar lists Starlink latency at 25 to 60 ms. A February 2026 analysis from Packetstorm reports median latencies of 25 to 50 ms with 99th-percentile peaks under 65 ms. A hands-on VoIP test from Protek IT Solutions measured 40 to 60 ms.

Different testers, different continents, same broad answer. That is the kind of agreement worth trusting.

The GEO side is equally clear and much less pleasant. The Orbital Radar comparison table, published March 2026, rates Viasat and HughesNet as unusable for video calls such as Zoom and Teams because latency sits beyond the 150 ms threshold. A June 2026 remote-work article from Sattvforme describes GEO satellite as producing noticeable echo and delay that make VoIP difficult. Nothing in the app settings menu changes physics.

One caveat before you plan around this. These are consumer and business-market measurements taken ashore. A ship adds a moving platform, a shared terminal, a company firewall and possibly forty other people on the same pipe. Treat the shore numbers as the ceiling and expect your cabin experience to sit below it. If you want the onboard side of that story, the honest write-up of living with Starlink Maritime onboard covers what the terminal actually feels like on a working vessel.

Which apps hold up on a low-earth-orbit link

All the mainstream calling apps work on a LEO link, and the published testing names them individually. That is the useful part, because "it should work" and "someone measured it working" are different claims.

The EarthSIMs Starlink guide states plainly that VoIP services including Skype, WhatsApp calls, Google Voice and SIP-based business phone systems work well on Starlink, with clear calls and no perceptible delay at typical latencies. The Sattvforme remote-work article, June 2026, says Zoom, Microsoft Teams, Google Meet and Webex all function normally on Starlink and that Starlink supports VoIP calling with acceptable call quality for most users. A Starlink latency explainer from Spacekits lists Zoom meetings, WhatsApp video calls, Google Meet and Microsoft Teams as supported, citing latency often under 50 ms.

So the practical shortlist for a crew member on a LEO-equipped ship looks like this.

WhatsApp is the default for most crews for a reason. It is named in the published Starlink testing, everyone at home already has it, and voice calls are cheap on bandwidth. If your ship allows only one calling app through the firewall, this is usually it.

Zoom has the most specific evidence behind it. The June 2026 Zoom-over-Starlink review concluded that Starlink's latency meets Zoom's requirements for high-quality video calling, and the Protek IT hands-on test concluded Starlink will work for VoIP calls and meetings, especially with Zoom. If you are sitting a remote exam or joining a company meeting from the cabin, Zoom is the safest pick.

Microsoft Teams and Google Meet are both confirmed working in the same sources. Teams matters if your company runs on it, and the Fusion IT support article is worth remembering here: group meetings suffer more from packet loss and jitter than one-to-one calls, so a big Teams call is the first thing to break when the link degrades.

Skype and Google Voice are named specifically in the EarthSIMs guide as working well. They stay relevant for anyone who still keeps a shore number tied to those services.

SIP-based business phone systems also get an explicit mention in that same guide. That covers the desk-phone-style services a company might issue, and it matters mostly for officers and superintendents rather than general crew.

Notice what this list does not contain: a magic satellite-optimised calling app. There isn't one in any of the published testing. The gains come from the link and from how you use it.

Honest cons, because none of this is smooth

Three problems show up repeatedly in the published testing, and all three will happen to you.

Spikes ruin calls even when the average is excellent. Fusion IT's support documentation describes latency that typically runs 40 to 80 ms but occasionally spikes higher because of signal quality, congestion or dish positioning. An average of 45 ms tells you nothing about the twenty seconds when it hit 400. Your call quality is set by the worst moments, not the median, and every marketing figure quotes the median.

Group video is the weak link. The same source reports blurry video, out-of-sync audio and brief dropouts on Teams, Zoom and Meet during congestion or obstruction, and flags group meetings as more sensitive to packet loss and jitter. A one-to-one voice call that sounds perfect gives you no guarantee about a twelve-person video call an hour later.

It is still worse than a wired connection, and you will notice. The Protek IT VoIP test describes Starlink latency as technically okay but higher than ideal, and warns that higher latency produces noticeable delays between video and audio. Nobody who has used fibre will mistake a satellite call for one. Long pauses, small collisions, the occasional lip-sync drift.

Two more caveats specific to ship life, and I flag these as my own judgement rather than published data. First, crew bandwidth is shared and usually shaped, so the terminal spec is not what reaches your cabin. Second, company IT often blocks or throttles calling apps regardless of link quality, which means your problem may be a firewall rather than a satellite. Test which apps pass before you build a routine around one.

Who should not bother with any of this

If your ship still runs a legacy geostationary VSAT, do not spend a contract chasing the right VoIP app. The Orbital Radar comparison rates that class of link as unusable for video calling because of latency, and the Sattvforme article describes the echo and delay that make VoIP difficult on it. Switch strategy instead of switching apps: use text, use voice messages, and save real conversations for port calls. The guide to cheap calls home from foreign ports is a better use of your money in that situation.

Also skip this if your calling problem is really an allowance problem. If the ship gives you a small monthly data quota, video calling will eat it in days regardless of latency, and the fix is bandwidth discipline rather than app choice. In port, the cleaner fix is skipping the ship's allowance entirely for the call: Airalo on a local eSIM gives you a full-speed connection for the call itself, with none of it coming out of the vessel's shared plan. The practical tactics in making the most of slow crew WiFi apply directly, because congestion and jitter cause the same symptoms as high latency.

And if you are hoping a VPN will improve call quality, it will not. A VPN adds a hop and some overhead. It has legitimate uses on a ship, privacy and access being the obvious ones, but it makes latency worse rather than better. Turn it off before an important call and back on afterwards.

Six things that actually help on a satellite link

None of these are exotic. They come straight from the failure modes the sources describe.

  1. Choose voice over video whenever the call matters. Voice needs roughly 100 kbps according to the Protek IT test figures, while video needs orders of magnitude more. When a link is marginal, dropping video is the single biggest improvement available to you.
  2. Prefer one-to-one calls over group meetings. Fusion IT's documentation specifically identifies group meetings as more sensitive to packet loss and jitter. If you have a choice, call people individually.
  3. Call when the ship is quiet. Congestion is named in the same source as a cause of latency spikes. Watch changeover and evening are the worst windows on most vessels.
  4. Keep the sightline clean if you control the terminal. Dish positioning appears in Fusion IT's list of spike causes alongside congestion and signal quality. On a ship you rarely control this, but if you do, obstruction is a real and fixable cause.
  5. Close everything else on your device. Background sync, cloud photo backup and app updates compete for the same shaped bandwidth and add jitter to your call.
  6. Have a text fallback ready and agreed at home. When the call degrades, switching to text immediately beats five minutes of "can you hear me now". Agree this with family before the contract starts.

That last point is the one crew underrate. Half of satellite call frustration comes from refusing to abandon a call that has already failed.

What about bandwidth, not just latency

Latency decides whether a call feels natural, and bandwidth decides whether video holds together. For Starlink, the June 2026 Zoom review cites Ookla data showing upload of 10 to 20 Mbps and download of 40 to 100 Mbps across much of North America. The Orbital Radar table from March 2026 lists 25 to 220 Mbps down and 5 to 25 Mbps up. The Packetstorm analysis from February 2026 reports 100 to 400 plus Mbps with low latency and minimal packet loss.

Upload is the number that matters for calling, because your voice and your camera go up the link. Those upload figures are comfortable for voice with room to spare, and adequate for video.

Two honest limits on that. Those figures are shore measurements on consumer and business plans, and a shared shipboard terminal will not deliver them to your cabin. The Orbital Radar comparison also notes that Starlink has no hard data cap but deprioritises traffic after 1 TB, which is a fact worth knowing if you are on a vessel where the whole crew shares one account. That figure was published in March 2026 and plan terms change, so check the current official plan page before you rely on it. On pricing generally, I am not going to quote numbers I cannot date, and neither should anyone else.

FAQ

What latency do VoIP apps need to work properly?

Under about 150 ms one-way. RingCentral's QoS guidance describes 150 ms as barely noticeable and generally acceptable, states that latency above 150 ms adversely affects VoIP quality, and calls anything above 300 ms generally unacceptable. The same body of guidance recommends jitter under 100 ms and packet loss under 3 percent alongside that latency target.

Does WhatsApp calling work on Starlink at sea?

The published testing says WhatsApp calls work well on Starlink. The EarthSIMs Starlink guide names WhatsApp calls specifically among VoIP services that work well on the link, and the Spacekits explainer lists WhatsApp video calls as supported at latencies often under 50 ms. Onboard, your actual result also depends on how the ship shapes crew bandwidth and whether the company firewall allows the app.

Can I use Zoom or Teams for a meeting from my cabin?

Yes on a low-earth-orbit link, with a caveat about group size. A June 2026 review of Zoom over Starlink concluded that Starlink's latency meets or exceeds Zoom's recommended requirements for high-quality video calling, and a June 2026 remote-work article reports Zoom, Teams, Google Meet and Webex all functioning normally on Starlink. The Fusion IT support article warns that group meetings are more sensitive to packet loss and jitter than one-to-one calls, so expect the large meetings to break first.

Why do my calls sound fine one minute and robotic the next?

That is jitter, usually caused by congestion or a brief obstruction rather than by the app. Fusion IT's Starlink and VoIP article describes latency that typically sits at 40 to 80 ms occasionally spiking higher due to signal quality, congestion or dish positioning, producing voice clipping and echo. Reinstalling the app will not change it, and calling at a quieter hour often will.

Is there a VoIP app made specifically for satellite links?

Nothing in the current published testing points to one. The apps named as working over satellite are the ordinary ones: Zoom, Teams, Google Meet, Webex, WhatsApp, Skype, Google Voice and SIP-based business systems. The variable that decides your call quality is the link type and the congestion on it, so effort is better spent on when and how you call.

My ship has old geostationary VSAT. Is there anything I can do?

Not for real-time calling. The Orbital Radar comparison published in March 2026 rates Viasat and HughesNet class services as unusable for video calls, and a June 2026 remote-work article describes the echo and delay that make VoIP difficult on geostationary links. Build your communication routine around text and voice messages, then use port WiFi or a local data plan for proper conversations.

Verdict

Get the link right and the app question mostly answers itself. On a low-earth-orbit terminal with published latency in the 20 to 70 ms range, Zoom, Teams, Google Meet, WhatsApp, Skype, Google Voice and SIP business phones all have documented evidence of working, and your remaining job is managing congestion, avoiding big group video and dropping to voice when things wobble. On a legacy geostationary link, accept it and change tactics. If someone tells you a specific app is the secret, ask them which link they tested it on, because that is the only variable that has ever made a real difference.

About the author

I work as a marine engineer and I write this site between contracts. Everything here about ship life, shared crew bandwidth, firewall surprises and calling home at the wrong hour comes from doing it. Everything here about measured satellite latency comes from the published third-party testing named in the text, with the publisher and date attached so you can check it yourself. Where I gave an opinion rather than a measurement, I said so in the sentence. Figures move, so re-check any plan detail on the official page before you commit money to it, and treat shore-measured numbers as the best case rather than what will reach your cabin.

Related reading

Latest updates