Can my ISP see IPTV?
Yes. Your ISP can’t watch the picture — that’s inside TLS — but it sees the DNS lookups, the server names, the addresses you connect to, and the unmistakable traffic pattern of hours of sustained streaming. Whether it acts on that is a policy question, not a technical one.
What your ISP can see
Start with the plumbing. Unless you’ve switched to encrypted DNS, every hostname your player looks up goes through your ISP’s resolvers — a tidy, timestamped list of the servers you stream from.
Even inside HTTPS, the connection greeting usually names the server in the clear — the SNI field of the TLS handshake. Encrypted variants exist but aren’t the norm yet, so on most connections your ISP reads the hostname without breaking any encryption.
And every packet carries a destination address regardless. Pair the addresses with volume and timing — live television runs at a steady few megabits per second, for hours, at predictable times of day — and the signature is hard to mistake for anything else on a home connection.
One caveat that cuts the other way: a fair amount of IPTV still travels over plain HTTP, not HTTPS. There the ISP doesn’t need inference — it can read the stream URLs directly, including the credentials many providers embed in an M3U link.
What it can’t see
Inside a TLS connection the content is opaque: not the picture, not the sound, not the channel names your player requests. What’s left is metadata — who talked to whom, when, and how much. The catch is that for television, metadata is most of the story: hours of sustained traffic to one host says who watches, from where, and when.
What ISPs do with it
Two things, mostly. Some shape traffic: connections classified as video get slowed at peak hours so the network breathes easier — permitted in many places, invisible on your bill, and felt as evening-only buffering. And most keep connection records for as long as local law asks them to; how much and how long varies by country.
Throttling has a tell. Run a plain speed test, then a stream, at the same hour: if large downloads are quick while streams struggle — and the same streams behave once routed through a tunnel — the traffic is being classified and shaped. If everything is slow, that’s congestion, not policy.
The standard answer: a VPN
A consumer VPN fixes the visibility problem cleanly. The tunnel encrypts everything between you and the VPN’s servers, so your ISP sees one encrypted connection instead of DNS lookups, hostnames, and stream traffic. Shaping keyed on “this looks like video” loses its signal.
It’s fair to say what it costs and what it moves. It costs a monthly fee and a detour for all your traffic. And it moves trust rather than removing it: the VPN vendor now occupies the position your ISP held — same view, different company. Your IPTV provider, meanwhile, learns nothing new but forgets nothing either: it sees the VPN’s exit address now, and it still sees every request your account makes.
How Twiga changes what each party sees
Twiga is relay software you point at a subscription you already pay for, and it splits the picture differently. Your browser holds one TLS session to twiga.tv — that is the whole story your ISP gets. The streams are fetched on the provider side and leave from Twiga’s VPN exits; the TV guide is fetched over Tor.
So: your ISP sees a TLS session to twiga.tv; your provider sees Twiga’s exit IP. And the relay in the middle is a blind relay — no decoder on the box, so what you watch isn’t something it declines to record; it’s something it cannot know.
The honest limits: Twiga is in beta, it plays one stream per user, and it covers your IPTV — not the rest of your device’s traffic. For that, a VPN is still the right tool.
Quick answers
Can my ISP block IPTV?
It can block or slow traffic it can identify — by DNS name, by server address, or by the traffic pattern. Routing the stream through an intermediary it can’t classify, whether a consumer VPN or a relay like Twiga, removes the signals that make blocking easy.
Does HTTPS hide what I watch from my ISP?
Partly. HTTPS encrypts the content, so your ISP can’t see the picture — but the connection still reveals which server you talked to, for how long, and how much data moved. That’s usually enough to identify streaming, and often the service behind it.
How do I check if my ISP is throttling my streams?
Compare a plain speed test against streaming at the same hour. If large downloads run fast while streams struggle — and the same streams behave once routed through a VPN or a relay — traffic shaping is the likely explanation.
Does my IPTV provider see my IP address?
With a normal player, yes — every stream request arrives carrying your home IP. Through Twiga, streams are fetched on the provider side from Twiga’s VPN exits, so your provider sees an exit’s IP instead of yours.
What each party can and can’t see, in full: the manifesto