@jab1 wrote:
@wkglrn As has been explained in this topic previously, your public IP address is one from a range recently transferred from BT America to BT UK, and a certain IP location base service - used by Netflix, Disney (and others) has not updated their databases. PN are aware, and I understand, are trying to resolve the issue, although it is not really their responsibility.
What do you mean by 'transferred'?
The ARIN database for 150.143.0.0/16 hasn't been updated since Dec '21:
$ whois --host whois.arin.net 150.143.0.0/16
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#
# start
NetRange: 150.143.0.0 - 150.143.255.255
CIDR: 150.143.0.0/16
NetName: PLUSNET
NetHandle: NET-150-143-0-0-1
Parent: APNIC-ERX-150 (NET-150-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: BT Americas, Inc (BA-346)
RegDate: 1991-05-16
Updated: 2021-12-14
Ref: https://rdap.arin.net/registry/ip/150.143.0.0
OrgName: BT Americas, Inc
OrgId: BA-346
Address: 910 Hastings Ave. Suite 120
City: Newport
StateProv: MN
PostalCode: 55055
Country: US
RegDate: 2014-12-16
Updated: 2021-10-15
Ref: https://rdap.arin.net/registry/entity/BA-346
With RIR data almost certainly being the starting point for all geolocation service providers, supplemented by other information sources of course, it is unsurprising there will be issues when an allocation has been done in this way. Even though the allocation has been recorded in the ARIN DB as being made against 'PLUSNET' this is simply a human-readable name included for convenience. It is still recorded against 'BT Americas, Inc' as the operating 'Organisation' which is a formal object class carrying, amongst other information, location information and from which geolocation providers will begin their assumptions about where the address range resides.
Assuming Plusnet are not a registered LIR with ARIN then ideally the allocation would be made as an inter-RIR transfer to Plusnet's LIR with RIPE. If that would be considered a step too far for BT Americas as the holding organisation (which it might even for the fact that this address range will likely be considered a non-tangible asset with financial value) then they could still put in some legwork with the respective geolocation providers to fine tune their location information beyond the legal administrative information served up by the RIR databases. This is precisely what so-called 'geofeeds' are for - standardised (or defacto standard at least as whilst the format hasn't been ratified by the IETF it is in common use) representations of geolocation data. These can either be submitted manually to geolocation providers with accompanying self-declared authorisation (so even Plusnet could do this, it doesn't have to be BT Americas) or BT America can help geolocation providers do this automatically by publishing links to geofeeds in the RIR database (as structured comments rather than formal records types as described here).
If these actions aren't taken then there should be no surprise if sometimes geolocation providers are serving up erroneous information for subnets used outside of the service region that they are registered in.
Better still get us all on to IPv6 as we're starting from a clean slate there when it comes to what is being used and where! 😀
Edit: If it's of interest, here is Google's published geofeed which can be used by anyone to override the administrative location information contained within the RIR DBs (most of which likely suggests it all resides in Mountain View, California where the HQ is).
