[Chrysalis]

Well you didnt do the traceroutes which would have helped to diagnose, its possible there is congestion problems with ntl's peering that affects some areas to newshosting since we know ntl do not route their entire userbase over the same external routes.

Here is my trace to the unlimited server.

1 8 ms 7 ms 8 ms UBR [10.8.143.254]
2 13 ms 13 ms 12 ms leic-t2cam1-b-ge914.inet.ntl.com [82.3.35.213]
3 21 ms 20 ms 30 ms leic-t2core-b-ge-210-0.inet.ntl.com [82.3.33.134
]
4 10 ms 48 ms 44 ms nth-bb-b-so-230-0.inet.ntl.com [62.253.188.114]

5 45 ms 12 ms 20 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]

6 15 ms 19 ms 24 ms pop-bb-b-ae0-0.inet.ntl.com [213.105.172.77]
7 122 ms 22 ms 19 ms amst-ic-1-as0-0.inet.ntl.com [62.253.188.94]
8 20 ms 19 ms 19 ms j1.ams.sc.net [195.69.145.42]
9 103 ms 105 ms 104 ms unknown.iad.scnet.net [205.234.191.253]
10 133 ms 106 ms 122 ms gw5-newshosting.iad.scnet.net [66.225.244.162]
11 117 ms 107 ms 103 ms 63.218.45.254

As you can see it goes to america but via amsterdam which isnt the most direct path which would possibly affect speeds to them. All the return routes look good but they are to my ntl proxy server and not myself so there is a small chance the routing is different.