If you know the physical and network location of their routing boxes and you keep polling some (e.g. static) resource on their servers you can eliminate all cloud providers that are further away than the response time as being the hidden backend.
Let's say you narrow it down to 10 candidates and 5 of them experience some sort of network issue that gets reflected in the response times of TPB, you've now narrowed it to 5.
I wonder what they're doing to mitigate these sort of timing attacks meant to discover their hidden backend.
I wouldn't bother just taking the load balancers down. I'd go upstream of them to see where the traffic is going, and then take down those hosts at the same time as the load balancers.
... only for The Pirate Bay to spin up more instances elsewhere and point a domain or two at it.
Imagine trying to detect copyrighted songs from Youtube if users could upload code bundled with the videos and load balance requests.
I will assume fingerprints of detected instances will travel between cloud provides, and that pirate bay will then add code to prevent that.
It's pretty much what you'd expect, though: The web site is now running on VMs on two unnamed cloud providers, accessed through a load balancer. All traffic is still routed through servers they control. The cloud providers apparently don't know that they're hosting the pirate bay, or pirate cloud as it were. If a cloud provider goes away, they can move to the VMs to another one. If their own transit routers go down, no data is lost and it's easy to get back and running.