On Sat, 23 Aug 2025, jay--- via NANOG wrote:
On 8/23/25 08:40, nanog--- via NANOG wrote:
It's a basic principle of a free market that you cannot force someone to provide service. If Netflix wants to ban certain IP ranges at random, they're allowed to do that and the only recourse is whining.
Customers in those random IP ranges who are paying for the service would beg to differ. They're paying for a service which Netflix intentionally is refusing to provide, based on erroneous data from a third party hired by Netflix.
Part of the problem is that the term "IP address" was chosen instead of "IP number" or "IP identifier". It leads to the false assumption that an "address" relates to a physical location.
Let's be honest. In most cases, an IP address is closely associated with gear in a relatively fixed physical location. That location might be a home (like my IP from Spectrum, or the homes of thousands of GPON customers served by my employer), a college campus, etc. These IPs don't migrate widely across states or countries. Even in the case of CGNAT, we found due to IP Geo, we had to define external pools regionally and map customers into the appropriate pool. So, in the case of CGNAT, you're not going to get accurate ZIP+4 IP geo for any affected customers, but those IPs/eyeballs still don't migrate beyond their DMA. It sounds like Digital Element has come up with their own methods for generating IP Geo data, largely from mobile devices. I find thier website particularly annoying in that it says so little about how their products work while saying so much buzzword BS. They don't even seem to have a test lookup function, as many other IP Geo providers do. You really have to wonder WTH anyone, much less large streaming providers, would pay for their service. It also sounds like their service works by publishing data sets on a regular schedule, so even if you can get to a person and spoon feed them corrected IP Geo data for your networks, it won't immediately fix anyone's issues. You have to wait for the next data dump/publish. ---------------------------------------------------------------------- Jon Lewis, MCP :) | I route Blue Stream Fiber, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________