IP Geolocation Incorrect: Hosting Provider Subnet in Kazakhstan (KZ) Flagged as Russia (RU) by Microsoft

Question

Hello,

We are a hosting and VPS provider based in Kazakhstan. Microsoft's network mapping currently identifies our public IP address blocks as being located in Russia (RU) instead of Kazakhstan (KZ), which causes regional routing and service identification mismatches for our infrastructure.

Technical Details:

Affected IP Range / Subnet: 109.248.247.0/24

Autonomous System (ASN): AS215670

Current Incorrect Location: Russia (RU)

Correct Location: Kazakhstan (KZ)

Verification & Proof:

RIPE Database Record: https://rdap.db.ripe.net/ip/109.248.247.0/24

RFC 8805 Geofeed: https://fst.kz/geofeed.csv

Could a Microsoft network/routing engineer please review this telemetry and apply an internal backend geolocation override for our subnet? Thank you for your assistance.

Answer 1

This type of IP geolocation correction is handled by Microsoft on the back end. The documented resolution pattern in similar Entra and Azure sign-in geolocation cases is that the issue is escalated to the product team, which updates the IP address location mapping internally.

For the affected subnet 109.248.247.0/24, the supported outcome is an internal geolocation mapping update from RU to KZ after Microsoft review. There is no self-service admin setting in the provided material to override this mapping directly.

---

• Report wrong geolocation of IP addresses in Azure/Entra-ID - Microsoft Q&A
• How do I change GeoLocation on a public IP address showing wrong location/region in Azure Sign-in Logs? - Microsoft Q&A
• How do I change GeoLocation on a public IP address showing wrong location/region in Azure Sign-in Logs? - Microsoft Q&A
• Microsoft IP Geolocation - Microsoft Q&A
• How can I change the geolocation tied to our main office's IP address in Entra? - Microsoft Q&A