I've been doing a bit of testing and here's the results. All tests were done within 10 mins and on the same line with the i-choice platform. All are 1024/128 services.
As you can see, my speed is way down from the 1024 I should be seeing, but this must be due to the line as all are down. To my surprise, netway is performing particularly poorly. Wavespeed is by far the best.
I have played around 1hr of Battlefield 2 on a uk server on all these connections. All of them are crap and unplayable, but Wavespeed managed to stay connected without getting autobooted for a bad ping.
I would try OTEnet as well, but after over 48hrs they have not yet replied to my email and I find that totally unacceptable for an ISP company.
Pinging 195.78.82.62 with 32 bytes of data:
Reply from 195.78.82.62: bytes=32 time=173ms TTL=115
Reply from 195.78.82.62: bytes=32 time=133ms TTL=115
Reply from 195.78.82.62: bytes=32 time=140ms TTL=115
Reply from 195.78.82.62: bytes=32 time=135ms TTL=115
Ping statistics for 195.78.82.62:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 133ms, Maximum = 173ms, Average = 145ms
Pinging 195.78.82.62 with 32 bytes of data:
Reply from 195.78.82.62: bytes=32 time=146ms TTL=114
Reply from 195.78.82.62: bytes=32 time=131ms TTL=114
Reply from 195.78.82.62: bytes=32 time=131ms TTL=114
Reply from 195.78.82.62: bytes=32 time=137ms TTL=114
Ping statistics for 195.78.82.62:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 131ms, Maximum = 146ms, Average = 136ms
Pinging 195.78.82.62 with 32 bytes of data:
Reply from 195.78.82.62: bytes=32 time=139ms TTL=114
Reply from 195.78.82.62: bytes=32 time=125ms TTL=114
Reply from 195.78.82.62: bytes=32 time=125ms TTL=114
Reply from 195.78.82.62: bytes=32 time=126ms TTL=114
Ping statistics for 195.78.82.62:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 139ms, Average = 128ms