Tracert on IP vs domain name

[staffsync]

What is the name of the domain?

staffsync.nz

What is the issue you’re encountering

We have been having a lot of our users calling up saying our web application is going very slow for the past couple of days, at times they get a connection has been closed error, at other times it performs as usual. If I do a basic GET request using cURL on the website it is usually around 400ms to get a reply, but at times can go up to 50s +. If I do a tracert on the same URL is shows it going off to the USA where it just stops. We are in New Zealand (and the server is hosted here in NZ), so have 2 local Cloudflare sites, plus Australia none of which are showing an issues, so I don;t understand why it is going off to the USA which is when we get the big lag. If I do a tracert on the IP address that the domain is proxied to in Cloudflare it goes straight to it in only 3 hops, but when I tracert the domain so its going via Cloudflare its getting lost in the USA, any ideas why? Thanks

What feature, service or problem is this related to?

DNS records

What are the steps to reproduce the issue?

Do a tracert on apps.staffsync.nz

Screenshot of the error

[DarkDeviL]

I’ll quote two previous posts I made:

@DarkDeviL

As one single IP address can only have one single set of information (e.g. country, state, city, …) attached at a time, any attempts to use such “geolocation” to determine the actual “destination country” on IP addresses used with anycast, or other sort of multi-homing as well, will always be whacky, if ever successful in any way.

With Anycast, or other kind of multi-homed IP addresses, the most common would be to see the IP addresses as showing up with the country code of the person/organisation that the IP addresses are allocated to.

&&

@DarkDeviL

Anycast and Geolocation does not go hand in hand.

IP addresses does only have one single location assigned in such IP location databases, and as such, it would be quite impossible for IP space that is running anycast - running in dozens to hundreds of locations worldwide, to be showing any sort of useful location information ever.

On top of that it does also depend on the individual IP location database, and how they do things.

For IP space that is running anycast, I wouldn’t expect any other location than the headquarters of the company holding the IP space, which would be United States (US) in your situation, because that’s where Cloudflare has it’s headquarters.

That said, -

@staffsync

so I don;t understand why it is going off to the USA which is when we get the big lag.

The traffic is not going outside of your own country.

As you can see in your screenshot, you have a latency of 17, which wouldn’t be possible for traffic leaving New Zealand and ending up in United States.

The IP address before the last hop, “2400:cb00:46:2::c629:ecfd” is also in Auckland, New Zealand.

So the tool you’re using with the screenshot you provided, - it is misleading you, due the geolocation issue with multi-homed IP addresses, as I quoted above.