Why Route 53 geolocation routing is not accurate?

Purpose of the document

This article will show you why Route 53 geolocation routing is not accurate at times. In this situation, how we can troubleshoot that and how we can fix it.

Background

Route 53 Geolocation routing lets you choose the resources that serve your traffic based on the geographic location of your users, meaning the location that DNS queries originate from.

For example, when you have create two resources in US and EU. You would like to let the users from US to access the resource in US and let the users from EU to access the resource in EU.

With Route 53 Geolocation routing, the users can resolve to different IP from different continent.

You can set the Route 53 record as following

The record of geolocation routing to US resource.

The record of geolocation routing to TW resource.

Then we can use third-party tool(RIPE Atlas) and probes in US and TW to check DNS resolver result.

Probes in US