Blog
Party chat and Discord cutting out on Starlink while the game is fine
Game traffic and voice traffic often travel different routes. When only the voice breaks, look at NAT, IPv6, Wi-Fi and lost packets before you blame the plan.
- Voice chat can take a different route from the game, through a relay server or a direct link between players, so it can fail while gameplay holds.
- Microsoft says some Xbox games need a Teredo IP address for party chat, and recommends IPv6, which Starlink provides natively on every plan.
- Microsoft says double NAT can stop you hearing other players; on Starlink, make sure only one router does the routing.
- Robotic or choppy voice from everyone usually means lost packets on your side: wire the device and check the Starlink app for interruptions.
Voice often takes a different path from the game, through a relay server or a direct link between players, so a NAT or IPv6 problem can break chat while the match runs fine. Start with the console’s own network test, then look at Wi-Fi and lost packets.
Why voice and the game take different paths
A matchmade game on the publisher’s servers is the easy case. Your console opens the connection, the server answers, and Starlink’s network passes the replies back. That’s why most online games work on a Starlink home plan even when the console’s NAT label looks poor.
Voice is less predictable. Console makers don’t publish exactly how their party systems route audio, but parties commonly try a direct link between players first and fall back to a relay server when that fails (our reading). Discord works differently again: everyone in a call connects to one of Discord’s own voice servers.
On a Starlink Residential plan, three facts from Starlink’s help center (read Nov 3, 2026) set the scene:
- Starlink’s default IPv4 setting uses carrier-grade NAT, so your router doesn’t get a public IPv4 address of its own.
- That default setting allows no inbound IPv4 connections.
- IPv6 is native on every Starlink router, kit version and service plan.
A direct link between two players needs one side to accept an incoming connection. Over IPv4, a Starlink home can’t, so the voice either finds another way through (IPv6 or a relay) or fails. Microsoft describes what the failure looks like from the player’s side. When two devices in a home both do NAT, it says, “you may have trouble hosting or joining multiplayer games and parties, or hearing other players.”
Xbox: Teredo, IPv6 and the network test
Microsoft’s NAT troubleshooting page (read Nov 3, 2026) has the lines that matter for party chat:
- “If your console encounters an issue obtaining a Teredo IP address, you can’t use party chat or connect to multiplayer games for some XBOX titles.” In plain words, Teredo carries IPv6 connections inside IPv4 traffic.
- If the console reports its NAT as Unavailable, Microsoft says you won’t be able to use party chat or join multiplayer for some titles.
- On IPv6, Microsoft’s separate page says the expansion “removes the need for Network Address Translation (NAT), which can interfere with multiplayer gaming and chat over IPv4 networks.” Both your router and your provider must support IPv6. Starlink covers the provider half.
What to do, in order:
- Run the console’s network test. Settings, then General, then Network settings, then Test NAT type. Note the NAT result and any Teredo message.
- Leave IPv6 on. If you run your own router, check IPv6 is enabled there too.
- Allow the two router options Microsoft names, if you use your own router: “Allow Teredo tunneling” and “Allow IPv6 tunneling”. Router makers label them differently, so look in the firewall or advanced settings.
- Check for double NAT. If you plugged a second router in behind the Starlink router without bypass mode, two devices are translating addresses. Starlink warns about double NAT in its own setup notes. Pick one router to run the network; the console setup guide shows both ways to do it.
- Test again, then start a party with one friend before you bring the whole group in.
PlayStation party chat
Sony publishes less about this. Its NAT definitions come from the PS4 user’s guide: Type 1 means the console connects straight to the internet, Types 2 and 3 mean it connects through a router, and with Type 3 communication with other consoles “might be impossible” or network features may be limited. Sony also says PS5 supports IPv6 but not IPv6-only connections, so the console still relies on IPv4. On Starlink Residential, that’s the shared address.
- Run the test. Settings, then Network, then Connection Status, then Test Internet Connection. Note the NAT type.
- If you see Type 3, party trouble is most likely when you meet other players on strict connections (our reading). Ask a friend on cable or fiber to start the party and invite you; joining an open host is easier than being the host.
- If you run your own router, remove double NAT and switch on UPnP. That tidies the house side. It can’t open the shared address at Starlink’s end.
The NAT type guide lines up the Xbox, PlayStation and Switch scales side by side and explains what each result allows.
Discord: voice server and connection checks
Discord calls run through Discord’s voice servers, so Starlink’s blocked inbound connections rarely stop them outright (our reading). When Discord breaks on Starlink, the usual sign is robotic or choppy voice, which means voice packets arrive late or not at all. Discord’s own community has a long thread on robotic voice from other users, and the replies show how often the cause is one person’s connection rather than the server.
Checks, quickest first:
- Read Discord’s connection panel during a call. Clicking the voice connection status shows your ping and packet loss to the voice server. Loss on your side points to your Wi-Fi or the dish. No loss on your side points to the other speaker.
- Look at the voice region. Server admins can set a region override on a voice channel. A far-off region adds delay for everyone in the call.
- Toggle Discord’s Quality of Service setting. Under Voice & Video, Discord offers a high packet priority option. Switching it off, or on, is a standard step when voice breaks on some home routers.
- Leave the call and rejoin before changing anything bigger.
Wi-Fi or cable for the device that carries the headset
Your headset is only as steady as the device it plugs into. On a console, the voice rides the console’s connection. On PC Discord, it rides the PC’s. On a phone, it rides the phone’s Wi-Fi.
- Wire consoles and PCs where you can. The lag guide covers which cable to use and where the ports are.
- Use 5 GHz if a cable can’t reach. Starlink tells customers to put gaming consoles and computers on the 5 GHz band.
- Watch the phone. If you chat on a phone in the next room while playing on a wired console, the phone’s weak Wi-Fi can be the weak link. Move it closer to the router, or chat through the console.
- Keep the Starlink router in charge unless you have a reason not to. Its built-in queue management keeps one person’s download from crowding out small, time-sensitive traffic; the lag guide explains what you lose in bypass mode.
When spikes are the cause
Some voice dropouts come from the connection itself. Starlink says a dish switches satellites many times per minute and that a brief switch is often not noticed. Obstructions are another matter: Starlink says one that stays in the dish’s view “can still cause intermittent outages, dropped packets, and lower speeds.” A game can hide a short gap by predicting movement; a voice stream can’t fill in a missing half-second of speech (our reading).
If the Starlink app shows a “Recent interruptions” alert, or its Event Log lines up with the moments chat dropped, work through the lag guide, which starts with the cable and the obstruction map.
Symptom, likely cause, fix
| Symptom | Likely cause | Fix |
|---|---|---|
| Xbox can’t get a Teredo address, or NAT shows Unavailable | Teredo or IPv6 blocked, or double NAT | IPv6 on, allow Teredo and IPv6 tunneling, one router |
| You hear some friends but not others | Your strict NAT meeting theirs | Let a friend on cable or fiber host the party |
| Chat broke right after you added a router | Double NAT | Bypass mode, or set your router to access-point mode |
| Everyone sounds robotic to you, game fine | Packet loss on your side | Wire the device; check the app for interruptions |
| Only one person sounds robotic | Their connection | Ask them to check theirs |
| Drops bunch up in the evening | Busy network | Note the times; Starlink’s peak hours are 6 pm to 11 pm local time |
| Discord only, consoles fine | Discord region or settings | Check the connection panel and Voice & Video settings |
Most households fix party chat with the first three rows: IPv6 on, one router, and a cable to the console. If the NAT test still shows the strictest result after that, the NAT type guide explains what a Residential plan can and can’t change.
What gamers and cord-cutters ask
Why does party chat fail on Starlink when online games work?
Matchmade games connect your console out to the publisher's server, which works through Starlink's shared IPv4 address. Party chat may try a direct link between consoles, and Starlink's default setting blocks incoming IPv4 connections, so chat can fail where the game doesn't (our reading).
How do I fix Xbox party chat on Starlink?
Run the console's NAT test, leave IPv6 on and make sure only one router does NAT. If you use your own router, Microsoft names two settings to allow: Teredo tunneling and IPv6 tunneling.
Why does Discord sound robotic on Starlink?
Robotic voice usually means voice packets arrive late or not at all. Wire the PC, check the Starlink app for recent interruptions, and remember the cause can be on the other speaker's line rather than yours.
Does Starlink block voice chat ports?
Starlink publishes a short list of blocked ports, and the common Xbox and PlayStation ports don't appear on it. The limit on Residential plans is that incoming IPv4 connections are blocked, not particular ports.
Will a gaming router fix party chat on Starlink?
Only on the home side. Your own router can remove double NAT and run UPnP inside the house, but it can't open the shared IPv4 address at Starlink's end.
Sources
- Troubleshoot NAT errors and multiplayer game issues (XBOX Support) (retrieved Nov 3, 2026)
- IPv6 on XBOX (XBOX Support) (retrieved Nov 3, 2026)
- What IP address does Starlink provide? (Starlink help center) (retrieved Nov 3, 2026)
- DHCP Configuration (Starlink help center) (retrieved Nov 3, 2026)
- Test Internet Connection, PlayStation 4 User's Guide (retrieved Nov 3, 2026)
- How to connect your PlayStation console to the internet (PlayStation Support) (retrieved Nov 3, 2026)
- Robotic voice from other users (Discord community) (retrieved Nov 4, 2026)
- How do obstructions affect my Starlink connection? (Starlink help center) (retrieved Nov 3, 2026)
- Intermittent Internet - Troubleshooting (Starlink help center) (retrieved Nov 3, 2026)
- What are the alerts on my Starlink App? (Starlink help center) (retrieved Nov 3, 2026)
- What is the Event Log? (Starlink help center) (retrieved Nov 3, 2026)
- Why are my speeds slow outside or during peak hours? (Starlink help center) (retrieved Nov 3, 2026)
Every figure keeps the date we last looked it up; our fact rules say how. When one turns out wrong or stale, the fix is dated on the corrections page.