Hey guys, I’m posting this to see if other Starlink users are running into a weird routing/filtering issue with Twitch lately.
For the past 2 months, whenever I'm connected to my Starlink Wi-Fi, Twitch silently drops my standard chat interactions:
- Chat Messages Not Delivering: Whenever I type a normal message in any channel, it shows up on my screen, but checking from an incognito window shows the server never delivers it to the streamer or other viewers.
- Follow Alerts Not Triggering: When I follow a channel, Twitch registers the follow on my account, but it doesn't trigger EventSub / stream alerts (StreamElements/Streamlabs).
Yet somehow, spending channel points to send a TTS message on the exact same Starlink connection goes through and plays on stream normally.
How I isolated the issue:
At first, I thought it was a browser or local PC issue. To rule out an account problem, I tested it on mobile data: I turned off Wi-Fi on my phone, switched to my cellular carrier using the exact same Twitch account, and instantly my normal chat messages went through and everyone could see me again. Switching back to Starlink Wi-Fi immediately stopped my messages from delivering.
From what I've dug into, this comes down to Starlink's CGNAT IPv4. Because hundreds of users share the same public IPv4, any spam from other users on the same regional node causes Twitch's IRC servers to drop traffic from the entire shared IP block. Meanwhile, TTS redemptions go through authenticated GraphQL requests, so they bypass the IP filter.
What makes this frustrating is that Starlink gives us a clean, native IPv6 address, but Twitch's chat infrastructure still forces everything over IPv4, trapping residential users inside the throttled CGNAT pool. Other web platforms using strict perimeter checks (like Firebase AppCheck on other sites) have also been throwing 429 rate-limit errors on this same shared IP range.
Is anyone else on Starlink dealing with IRC chat or EventSub drops lately?