Apparently this is one of those “black hole” issues. Linode says they have contacted their upstream providers, but it’s been impossible for me to get in touch with anyone relative to Percona servers blocking Linode. They all seem to want money from me to talk about this…
So, my only recourse is to delete a server I spent hours setting up and try to get a Linode server on a different IP segment that is, hopefully, not being blocked by Percona and try it all again.
Update: I tried setting up servers in all the USA datacenter locations for Linode and in each case I am assigned the 45.56.x.x IP segment. The only Linode datacenters not being blocked by Percona are located in London and Tokyo. So, Percona has effectively blocked all new Linode servers located in the USA.
And, there seems to be no way to contact anyone at Percona about this.
Apparently, they aren’t reading this forum, either.
I just want to inform you that your update repositories are inaccessible from all new USA Linode servers and any existing within the 45.56.64.0/18 IP range.
I’ve been unable to contact anyone at your end about this issue. Linode support is aware of the issue and is working with their upstream providers, but it is obvious that the issue is at your network: fw01.bm.percona.com
Below are 2 mtr reports from Linode servers. One, located within Linode’s 96.126.96.0/19 IP range, is successful. The other, within 45.56.64.0/18, is not.
Please help as this issue has been happening since, at least, Jan 27.
I tried filing tickets at Linode, but they closed the first one summarily saying “It’s a Percona issue; contact them”. Hopefully Linode will be a little more pro-active once they see I won’t stop filing tickets. Obviously Percona must have banned their IPs for a reason, and Linode will probably need to do something before the ban is lifted.