I believe the linx issue is resolved so if the problem still exists it could be something to do with ntl or another point of failure.
__________________
seems to be a problem with hop 16 tho
14 163 ms 168 ms 162 ms p14-0.core01.san01.atlas.cogentco.com [66.28.4.6
]
15 171 ms 166 ms 180 ms p4-0.core01.lax01.atlas.cogentco.com [66.28.4.77
]
16 273 ms 246 ms 258 ms filefront-allyance.dmarc.cogentco.com [38.112.29
.134]
17 248 ms 247 ms 276 ms node.
www.la.ioerror.com [66.117.8.41]
__________________
Quote:
|
Originally Posted by IanUK
I'm not 
I have a 3meg NTL connection, and use the AOL client in 'Bring your own access' mode on the top. Using that client routes all content through AOL's proxies rather than NTL's, all sites work at full speed through it, which is much better than the NTL Poplar Proxies which are quite frankly awful. |
Sounds interesting, what url is it to use that and do you need to be an aOL customer?
I did speedtests for you full speed on both ntl auto proxy and my own proxy.