aroundLatLngViaIP and aroundPrecision

We noticed last week that our search queries with aroundLatLngViaIP = true seem to no longer respect the radius precision specified in aroundPrecision.

I also tried in the algolia dashboard that if I use IP-based location, it makes no difference in the ranking to change the radius precision, but if I specify an actual lat/lng, the radius precision suddenly becomes useful again.

This didn’t seem to be the case a few weeks ago, when we started to use algolia. Was it a recent change?