Shared logins and restreamers: how to spot them, and what to do

By the Minimus team · · 3 min read

Every operator finds one sooner or later. A line bought for one household, watched from four countries. Or a line that never sleeps, pulling the same twenty channels day and night: someone else's server, reselling your streams.

Both cost you money. The second one can also cost you provider connections, because it holds them all day long.

What sharing looks like

The giveaway is one line showing up in places that can't all be one home. Two connections from the same city, one on home broadband and one on a phone, is a normal family. The same line in three countries in one evening is not.

Home, United Kingdomwatching Ch AfineMobile network, United Kingdomone address, many customersfineRented server, another countrysame channel, 24 hours a daylook closerDownload toolasks like a script, not a playerlook closer One line limit: 2 connections
The same line, four places. Two of them are people.

Look at a line's recent connections: the address, the country, the network it comes from and the app it says it is. Most panels log these. Sort your lines by how many different addresses each used in the last week and read the top of the list. It's usually obvious.

What a restreamer looks like

A restreamer connects from a rented server in a data centre rather than a home or a mobile network. It watches the same channels around the clock and never stops for the night. Its requests often name a download tool or a script instead of a player app. And it sits at its connection limit all the time, because it's serving other people.

None of these proves anything on its own. Two or three together nearly always mean the same thing.

Rules that work

Limit connections per line. It's the oldest rule and still the most useful. A household needs two or three. A restreamer wants as many as it can get.

Make links expire. If the address a player gets for a channel only works for a few minutes, a link copied into someone else's system stops working by itself.

Block rented servers, with exceptions. Very few real customers watch from a data centre, so blocking hosting networks catches a lot of restreamers in one go. The big exception is VPNs: plenty of real customers use one, and a VPN exit sits in a data centre too, so leave the well-known VPN networks out of the rule. Keep a short list of other exceptions, like a hotel system or your own monitoring.

Look hard at download tools. Most player apps say what they are when they connect, and requests from command-line tools deserve attention. Test before you block anything wholesale, though. We once blocked a perfectly normal app by mistake, because the networking library it used introduces itself the same way some scripts do, and people using it could sign in but couldn't load their channel lists.

Don't punish mobile networks. Mobile operators put thousands of people behind a handful of addresses, and so do big apartment blocks and hotels. If you block an address because several lines use it, you'll block real customers. An address with several of your customers on it is almost always fine.

Most of these rules are built into Minimus: connection limits per customer, links that expire in minutes, and rules that catch rented servers and download tools. Its automatic blocks for password guessing and floods never touch an address where two or more of your customers are watching, so people on mobile networks keep watching.

When you find one

For sharing, a message usually does it. Most people know exactly what they've done, and plenty will happily pay for a second line.

For a restreamer, disable the line and leave everything else as it is. The connection log is your evidence if a reseller turns out to be involved, and if the same reseller keeps coming up, that's a conversation worth having.

Start with that list of lines sorted by how many addresses they've used. It takes ten minutes. Read the top ten before you change a single rule.

More from the blog