Starlink Keeps Dropping During Video Calls: What to Check

A fast download test does not guarantee a clear meeting. Video calls depend on a steady connection in both directions, and a short interruption can freeze speech even when ordinary browsing appears normal. Work through the checks below in order so you can distinguish a dish interruption from weak Wi-Fi, competing uploads or a problem on one computer.

Start with a useful record

Before restarting anything, note the time, meeting app, device, room and symptoms. Did the other person lose your voice, did you lose theirs, or did the whole meeting disconnect? Did another device lose internet at the same moment?

Open the Starlink app and check its status, outage history and obstruction information around that time. Save screenshots privately. An event matching the dropped call is useful evidence; an unrelated event hours earlier is not a diagnosis.

Do not factory reset the router as a first step. It removes settings and can make comparison harder. Preserve evidence before a deliberate restart.

Understand the measurements

Download speed describes how quickly you can receive data; upload speed describes sending it. A call uses both. Three other measurements help explain why a high speed-test result can still feel poor:

• Latency: the travel time for data. Higher delay can make people talk over one another.
• Jitter: variation in that delay. Uneven arrival can make speech sound broken.
• Packet loss: missing pieces of the data stream. The application may conceal a small gap, but larger or repeated gaps become noticeable.

Use the meeting application's connection statistics if available. Compare a quiet test with a problem period on the same device. A speed test can itself consume bandwidth, so run it between test calls rather than during an important meeting. Do not treat one favourable reading as proof of reliable service.

Step 1: Test the same device beside the router

Make a short call using the same laptop or phone, the same application and a willing test partner. Move close to the main router and pause large downloads and backups elsewhere in the household.

If the problem disappears, repeat from the normal desk. A consistent difference points towards local coverage or interference. Improve router or access-point placement before buying a different Starlink dish. A mesh node needs a good connection back to the network; placing it in the existing dead spot may not solve the problem.

If nearby calls still fail, continue to a wired test where your hardware supports one.

Step 2: Compare Ethernet with Wi-Fi

Connect the test computer through the Ethernet connection appropriate to your kit. Some generations need an adapter; identify the equipment before buying one. Temporarily disconnect the computer from Wi-Fi to make the test path unambiguous.

Use the same call application and location. If Ethernet is consistently good and Wi-Fi is not, investigate the local wireless network. If both fail at matching times, look beyond Wi-Fi.

When Ethernet itself will not connect, follow our Ethernet troubleshooting guide. Do not assume a wired connection is a valid comparison until it is working correctly.

Step 3: Check uploads and household activity

Cloud-photo uploads, off-site backups and file synchronisation can compete with outgoing call traffic. Record which devices are active when a call breaks up.

For a controlled comparison, pause non-essential uploads, make a test call, then resume one workload at a time. If this repeatedly reproduces the fault, schedule that workload outside meeting hours or use the application's bandwidth controls. A third-party router may offer traffic management, but verify its capabilities before changing the network.

Our upload troubleshooting guide covers the next checks. Additional download capacity alone may not fix a busy upstream connection.

Step 4: Correlate interruptions with the dish

Check whether recorded outages or obstructions coincide with the call symptoms. Inspect the app's sky assessment and consider seasonal changes such as growing foliage.

Changing the router will not remove a tree from the dish's view. Equally, a clear obstruction map does not rule out a local Wi-Fi fault. Match evidence to the affected part of the connection.

Inspect only safely accessible equipment. Do not climb onto a roof to reproduce an intermittent fault. Ask an installer to assess a location or mount that requires work at height. Follow the kit's instructions before disconnecting cables.

Step 5: Isolate the computer and application

If only one device fails, check its microphone, speaker, headset and application permissions. Confirm that the correct audio devices are selected. Try another headset and then another calling application.

If you use a personal VPN or filtering service, a brief controlled test without it can identify an interaction. Restore protection afterwards. For a managed work computer, ask IT before changing security settings; do not disable an employer's controls.

If mobile Wi-Fi Calling is the problem, use the separate Wi-Fi Calling guide. Carrier registration and phone settings add different checks from a laptop meeting.

Worked example: a call breaks up during a backup

This is an illustrative diagnosis, not a measured Starlink Tips test. A home worker notices that colleagues stop hearing them each afternoon. Browsing still works. A wired test does not improve the call, and no matching obstruction event appears.

They pause a scheduled cloud backup and repeat a test call. Speech improves. Restarting the backup reproduces the symptom. The practical next step is to limit or reschedule the upload and repeat the comparison, rather than immediately replace the dish.

If stopping the backup makes no difference, that result is still useful: continue checking the other branches instead of treating the first guess as proven.

Prepare for calls that cannot wait

Keep a tested alternative such as a mobile hotspot, with adequate coverage and data. Switching connections can interrupt an active meeting, so know how to rejoin and keep dial-in details where available.

Automatic failover and bonding are different approaches. Ordinary switching does not promise an uninterrupted call. Specialised systems can help maintain sessions, but require compatible equipment, configuration and testing. Start with our backup-internet guide.

What to send to support

Provide the affected times and timezone, hardware model, whether all devices were affected, wired-versus-Wi-Fi results, relevant app events and the changes that made a repeatable difference. Share account information only through official support.

Ask the meeting provider or workplace IT for help when one application or managed device fails. Contact Starlink when app evidence or repeated tests point to the service or kit. Avoid posting passwords, private meeting links or account identifiers publicly.

Sources and review

Starlink intermittent-connection troubleshooting · Starlink calling troubleshooting · Peplink explanation of bonding and failover.

Reviewed 26 September 2026. Menus and features can vary with equipment and software.

Questions to explore next

• Why can the other person hear me on a Starlink VoIP call, but I cannot hear them?
• Will switching Starlink to backup internet interrupt an active call?
• What should I check if Starlink develops problems after a software update?