That doesn’t solve the issue because that is a node that is operated by blizzard as it has been delegated the IP block by that exchange in Amsterdam and said exchange says they take no responsibility for the operation of those nodes and responsibilities for it fall to the customer, in this case Blizzard
This is information that is available publicly on the IP blocks RIPE listing.
we’ve been trying to tell you that is the failing node for a while now.
I have a thread up myself on the forums for about 4 days now with a lot of diagnostic data for you on this specific issue too.
Edit: Should specify the issue is the block of IPs found in the IPs assigned to the hostnames under et-0-0-2. Not just that IP mentioned above. There are secondary issues including Bandwith Saturation, High Jitter, High Ping Spikes.
Another example would be the IP 137.221.65.18 where the issue is also observed.
These are all IPs leased by Blizzard from Amsterdam Internet Exchange B.V. some with pretty different IPs, which means the issue could be less specific to a single node and perhaps a more broader issue with infrastructure or implementation of handling of traffic in said infrastructure.