The easiest thing to do is to put up caching reverse proxies on big providers that respond immediately and only slow down on "dynamic" content, which we all assume to be slower anyway.
A more non-conventional approach would be to break the embedded OS of an intermediate router or network device (can you count how many transparent filtering network devices there are between you and a random website?) and have it return false data or provide static NAT to establish connections before they actually reach the destination.
The spoofed packets seems the most likely explanation. It's just not the only possibility :-)
rrbone UG (haftungsbeschraenkt)
Leibnizstr. 8a
44147 Dortmund
GERMANY
https://rdns.im/the-pirate-bay-north-korean-hosting-no-its-f...