If you or others are not receiving a satisfactory reply from us (Netflix) on this issue, please feel free to reach out directly and I'll make sure it gets handled.

So far as we know, we handle CGNAT (and IPv6) appropriately. Sometimes ranges get reassigned and the data that we have gets stale - this happens quite often since formal runout, and so sometimes we're behind the ball on it, but be assured that we take this seriously.

Thanks,

-Dave

On Thu, Jun 25, 2020 at 11:42 AM Mark Tinka <mark.tinka@seacom.com> wrote:

On 25/Jun/20 16:45, Christian wrote:
> wow. blaming support for IPv6 rather than using cgnat is a huge
> stretch of credibility

I have no idea what's going through Netflix's mind - it's all, as my
American friend would say, conjecturbation on my part.

CG-NAT isn't new, and if Netflix are still not able to consider it a
"fixed issue", there is probably a reason why that is.

Ultimately, reaching out to them and asking their position on the matter
seems like a path to an answer.

Mark.