Your Plex server has gigabit internet, your remote user has 200 Mbps down, but streams still buffer at 1080p. Before blaming your server, consider this: your ISP might be throttling Plex traffic. Some ISPs actively identify and slow down streaming traffic, especially high-bandwidth video streams from residential connections.
How ISP Throttling Works
ISPs can identify Plex traffic through deep packet inspection (DPI). Even though Plex uses HTTPS, the SNI (Server Name Indication) in the TLS handshake reveals the destination. Some ISPs also throttle based on traffic patterns — sustained high-bandwidth streams from a residential IP look like a streaming server, which is exactly what they want to limit.
Signs of Throttling
- Streams buffer at the same time every day (peak hours: 7–11 PM)
- Speed tests show full bandwidth, but Plex streams can’t sustain even 10 Mbps
- Local playback (same network as server) works perfectly at any quality
- Buffering affects all remote users, not just one person
- VPN fixes the buffering immediately (strongest indicator)
Testing for Throttling
The VPN Test
This is the definitive test. Have your remote user connect through a VPN (any reputable VPN like Mullvad, ProtonVPN, or Windscribe), then try the same stream. If it plays smoothly through the VPN but buffers without it, your ISP is almost certainly throttling.
Why Speed Tests Don’t Catch It
ISPs know which servers run speed tests (Ookla, fast.com, Google) and exclude them from throttling. Your speed test will show 500 Mbps while Plex struggles at 8 Mbps. This is intentional — it makes throttling harder to prove.
Wehe App
The Wehe app (developed by researchers at Northeastern University) specifically tests for differentiated treatment of streaming traffic. It replays traffic patterns from various services and compares throughput. It can detect throttling with statistical confidence.
Fixing Throttling
Option 1: VPN on the Server
Run a VPN on your Plex server so all outgoing traffic is encrypted. The ISP can’t identify it as Plex traffic and can’t throttle it specifically. Downsides: adds latency, may reduce overall throughput by 10–20%, and you need a VPN provider that allows port forwarding for remote access.
Option 2: Cloudflare Tunnel
Route Plex through a Cloudflare Tunnel. All traffic appears as regular HTTPS to Cloudflare’s IP addresses, which ISPs are unlikely to throttle (too much legitimate traffic goes through Cloudflare). This also gives you a custom domain and free HTTPS.
Important caveat: Cloudflare’s Terms of Service technically prohibit using their free tier for large media streaming. Enforcement is inconsistent, but be aware of the risk. Cloudflare Tunnel paid tier has no such restriction.
Option 3: Reverse Proxy with Custom Port
Put Plex behind an nginx or Caddy reverse proxy on port 443 (standard HTTPS). This makes Plex traffic look like any other HTTPS web traffic. Combined with a custom domain, it’s indistinguishable from normal browsing to DPI systems.
Option 4: Change ISPs or Plans
Some ISPs throttle residential plans but not business plans. If throttling is persistent and confirmed, a business-tier plan from the same ISP often eliminates it — though at a higher price. In areas with ISP competition, switching providers may solve it entirely.
Server-Side Mitigation
Even if you can’t fix the ISP throttling, you can reduce its impact:
- Lower remote stream quality: Set the remote stream default to 4 Mbps 720p. If the ISP is capping streams at 10 Mbps, a 4 Mbps stream won’t trigger the throttle
- Enable transcoding: Force transcoding for remote users so the server controls the bitrate, keeping it under the throttle threshold
- Plex Relay: As a last resort, Plex’s relay service routes traffic through Plex’s own servers. It’s capped at 2 Mbps on free accounts and 8 Mbps with Plex Pass, but it bypasses ISP throttling since traffic goes through Plex’s infrastructure
Documenting Throttling
If you want to file a complaint with your ISP or regulators:
- Run the Wehe test and save results
- Log speed test results alongside Plex streaming performance at the same times
- Document the VPN bypass test (timestamps, VPN on vs off, same content)
- In the US, file an informal complaint with the FCC through their consumer complaint portal