IssueTracker

I affirm that I have looked at all the other public issue templates at https://issuetracker.google.com/components/191657/manage#templates and restricted issue templates at https://issuetracker.google.com/components/191885/manage#templates and none of them apply.

Hi Googlers,

we run authoritative anycast for cdn77.com

1) First issue on IPv6
I'm seeing strange queries when Google's EU servers are asking our IPv6 resolvers in Singapore.
https://imgur.com/9dbfBUq
Google's 2a00:1450:4001:c05::103 is located somewhere around Prague and shouldn't be querying Singapore servers.
We tried fiddling around with IXes/communities, but didn't find out where you're picking up the routes exactly.

Can you check why it's happening?

There's no way for us to do a IPv6 traceroute from 15169 so we can't debug anything ourselves.
It'd be much easier with a public LG.

2) Second issue on IPv4 too
Example case: AS5610
Majority of DNS traffic from this AS is served by Vienna and Frankfurt, but sometimes our Seattle POP comes up.
Why would Google forward this traffic all the way to the US and increase latency? We see 8.8.8.8 Frankfurt via peering.cz and you should see 5610 directly too. So the traffic should turn around somewhere in your Frankfurt POP to Frankfurt anycast instead of being forwarded by Google and somehow hitting Seattle resolvers.
https://imgur.com/pRjo69O