@Dornul @Tunes @thezoikkeli (and others),
It appears that this is actually a known issue, due to the way we are currently processing location lookups and that we’re not updating the GeoIP database automatically. We have fixes for both of these issues – you can track progress here:
1 Like