@Gargron hey, thanks for the clarification. I found the reason why it happens. It appears that mastodon.social and concert.io are depending upon fastly.net for CDN services and hence there is an overlap of IP address which #TrackerControl identifies as an outgoing request to the Advertising portal concert.io.

Apologies for the trouble @Gargron. I will take this as an issue with #TrackerControl to see what can be done.

What's up with mastodon.social instance @Gargron?
Yesterday it was cdn.concert.io and today it's admanager.concert.io.

There is absolutely no explanation over why they are integrated with the instance. Once again thanks to #TrackerControl which exposed these integrations.

It's time to ditch the mastoson.social instance.