I agree with Mr Hawker, that the operative phrase is "trust, but verify." I understand Mr. DevRel's need to verify locations so his customers have some assurances, but the data broker will never know or care as much about that being accurate--for good actors--as the provider's customers and therefore the provider. I suspect the providers here would be happy if GeoIP companies defaulted to the Geofeed and used their proprietary tracking systems to confirm the information (and maybe even report to the provider if there is a mismatch, so they have an opportunity to cure or explain any discrepancy) instead of defaulting to their proprietary systems. They should only default to the proprietary system if there is evidence of subterfuge on the part of the provider. Doing otherwise is bound to lead to inaccurate information. For example, we have IP blocks that cover a half dozen zip codes in central Illinois, while our upstream providers are in Chicago and St Louis--all three culturally a very different locations. The IPs are all static so we produce Geofeeds that give the correct zip code of each IP accurately. Unfortunately, more often than not that information is ignored and instead all of our IPs show up as coming from a small town 20 miles from our main customer concentration (I have no idea why the GeoIP people chose that town...), or from Chicago (perhaps because they have test servers in Chicago?). Both of those can lead to real problems for customers. For example, the wrong local TV channels may be offered on a TV streaming platform, or even worse the wrong sports teams! It is a source of frustration for many of our users, and they blame us for it. Peter Folk, Volo.net Internet+Tech