Request for information: ISPs and P2P throttling

[Horatium]

3 13 ms 11 ms 12 ms 213.75.64.117
4 7 ms 11 ms 11 ms 213.75.64.117
5 9 ms 10 ms 11 ms 213.75.64.166
6 6 ms 7 ms 6 ms 134.222.93.140
7 8 ms 8 ms 9 ms 134.222.224.4
8 8 ms 8 ms 9 ms 134.222.199.101
9 8 ms 9 ms 9 ms 130.117.15.97
10 9 ms 9 ms 9 ms 130.117.0.85
11 20 ms 20 ms 20 ms 154.54.58.62
12 93 ms 94 ms 93 ms 154.54.87.66
13 93 ms 93 ms 93 ms 38.122.42.34
14 * * * Time-out bij opdracht.
15 101 ms 100 ms 100 ms 192.34.76.2
16 104 ms 101 ms 102 ms 199.91.189.234
17 101 ms 102 ms 101 ms 199.91.189.74

This is pretty much what I get every tracert. #14 hop times out every time over 15 tracers. #15 times out on the 14th tracert.
Doing another now but going to let it run for a longer period of time.

that's not relevant, because the host from 14th hop maybe is setup to not respond to pings, that's why you see it not answering.
try winMTR, which show you packets lost. There you'll see, after you enter in their data center how many packets are lost on which host.