I don't think the network operators can do anyting. RIPE displays the network origin correctly.

I guess you need to contact the GeoIP database maintainers, so that they refresh their data. This, for example: https://geoiptool.com/en/?ip=145.14.208.0

On Tue, Aug 29, 2017 at 8:54 AM, Philippe Maechler plcmaechler@gmail.com wrote:

Hi Swinog

We (AS61174) have some problems with a newer ip range 145.14.208.0/20. Customers are complaining that they access the content (e.g. Teleboy, Swisscom TV, and many more) from Netherland and therefore the access is denied.

Can you check your filters and make sure that this range "belongs" to switzerland?

If you have any questions, please feel free to contact me offlist

tia

Philippe

---

swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog

Hi,

On 29/08/2017 08:54, Philippe Maechler wrote:

We (AS61174) have some problems with a newer ip range 145.14.208.0/20 http://145.14.208.0/20. Customers are complaining that they access the content (e.g. Teleboy, Swisscom TV, and many more) from Netherland and therefore the access is denied.

That's because from what I can see, until February, that prefix had been announced for about a year from Verizon Nederland.

Can you check your filters and make sure that this range "belongs" to switzerland?

It's not that simple. For example, I see that MaxMind reports the prefix as being 100% in Dübendorf (https://stat.ripe.net/widget/geoloc#w.resource=145.14.208.0%2F20), but the situation might be different for other Geolocation providers. I see that you have a series of more specific objects in the RIPE database. What I can suggest, in order to help the other providers to pick up the new location is to add a geoloc: attribute to all of them. This would _help_ but won't completely fix the situation. As they already suggested, try to go and force the update on all the relevant GeoIP databases.

Ciao!