For the IPv6 address as mentioned above, - “2a06:98c1:3121::a”, you’ll see:
2a03:3da::5:9649:10 is currently unallocated.
I’ll happily take it on my coat, that I failed to mention “IPv6” above, which I actually intended to do, regarding what was interesting about the traffic that went over unallocated IP(v6) space.
The IPv4 address, “195.191.97.62”, is a bit interesting as well, as that is a part of an IP address range, which is currently held by “National Media and Infocommunications Authority”.
→
The routing mess you see, that is actually causing (partially) good connectivity, … it is happening within the network of AS5483 Magyar Telekom.
Whether it’s currently on AS5483 Magyar Telekom’s TODO list to correct this, isn’t anything that I can answer.
If AS5483 Magyar Telekom decides to “correct” it though, then you have my bet that you will (unfortunately) see the traffic for these IP ranges to rotate back, to be sent over their parent, AS3320 Deutsche Telekom, which would also mean towards the United States again.
Great findings, thank you.
(Please, point me resources where I can learn how to investigate things like this myself - TY)
So practically, for zendorka, I should now either give up on Hetzner (or any host using Deutsche Telekom) or Cloudflare.
For aug, I do nothing, and if I am lucky, DTAG-CF peering will be a thing before the routing mess you discovered gets cleaned up.
But wait… what still pops up question marks around my head, why is that routing mess affects only one domain? Shouldn’t it affect all traffic between the same two IPs irrevelant of the domain name???
Out of curiosity, I’ve moved the server from Falkenstein to Helsinki.
Same result, aug routed fast, zendorka routed slow.
I start realizing that changing the server host would not make any difference, as anyone whose ISP is DTAG (a lot in Hungary) will be routed to Ashbourn… well, at least for this domain sight.
Sure, I can move the server to Ashbourn but given our target audience is in Hungary, that could only be a last resort attempt to keep CF.
Well well, from this https://mtpeering.pages.dev/ it looks like only domains with the free CF plan are affected.
That might explain why aug is fast, perhaps because it was created long ago and grandfathered in.
Switched zendorka dot com from Free to Pro.
For $25 my troubles are gone, ping immediately went down from 160ms to 15ms (same values I see for aug dot hu and invictus dot com, two sites that are on free plan but brought to Cloudflare a good while ago)
but given our target audience is in Hungary, that could only be a last resort attempt to keep CF.