Netsource vs NTL : The Pings & Traceroutes!

LumoColor

Just got my Netsource DSL turned on today

I was so annoyed with NTL's bad customer service, downtime and downright ignorance so I got a second DSL connection.

Still have the NTL Cable on so I thought I would do a little test. Both connections are through routers with 1 pc connected. Tests were run at same time on freshly rebooted machines & routers.

Ping & Traceroutes to www.jolt.co.uk from both connections: -

NTL Cable 3MB
==================================================================================

Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:

4 40 ms 10 ms 31 ms dbln-t2core-a-ge-220-0.inet.ntl.com [82.9.145.21]
5 8 ms 8 ms 8 ms dbln-bb-a-ae1-0.inet.ntl.com [213.105.174.53]
6 14 ms 21 ms 13 ms ren-bb-b-so-100-0.inet.ntl.com [213.105.174.41]
7 14 ms 14 ms 13 ms ren-bb-a-ae0-0.inet.ntl.com [62.253.185.185]
8 39 ms 37 ms 24 ms bre-bb-b-so-110-0.inet.ntl.com [62.253.185.166]
9 25 ms 24 ms 22 ms win-bb-a-so-400-0.inet.ntl.com [213.105.172.233]
10 51 ms 43 ms 35 ms win-bb-b-ae0-0.inet.ntl.com [213.105.172.162]
11 57 ms 42 ms 24 ms pop-bb-a-so-010-0.inet.ntl.com [62.253.185.201]
12 58 ms 56 ms 22 ms pop-bb-b-ge-000-0.inet.ntl.com [213.105.174.230]
13 32 ms 72 ms 23 ms tele-ic-2-so-700-0.inet.ntl.com [62.253.184.6]
14 46 ms 46 ms 56 ms 212.250.14.42
15 24 ms 35 ms 44 ms ge-0-2-0.lon1-9.nildram.net [62.72.141.38]
16 25 ms 23 ms 59 ms jolt-gw.nildram.net [195.149.20.214]
17 36 ms 25 ms 23 ms secure.jolt.co.uk [82.133.85.65]

Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=45ms TTL=50
Reply from 82.133.85.65: bytes=32 time=33ms TTL=50
Reply from 82.133.85.65: bytes=32 time=43ms TTL=50
Reply from 82.133.85.65: bytes=32 time=39ms TTL=50
Reply from 82.133.85.65: bytes=32 time=38ms TTL=50
Reply from 82.133.85.65: bytes=32 time=36ms TTL=50
Reply from 82.133.85.65: bytes=32 time=35ms TTL=50
Reply from 82.133.85.65: bytes=32 time=34ms TTL=50
Reply from 82.133.85.65: bytes=32 time=52ms TTL=50
Reply from 82.133.85.65: bytes=32 time=24ms TTL=50
Reply from 82.133.85.65: bytes=32 time=36ms TTL=50
Reply from 82.133.85.65: bytes=32 time=53ms TTL=50
Reply from 82.133.85.65: bytes=32 time=44ms TTL=50
Reply from 82.133.85.65: bytes=32 time=36ms TTL=50
Reply from 82.133.85.65: bytes=32 time=35ms TTL=50
Reply from 82.133.85.65: bytes=32 time=25ms TTL=50
Reply from 82.133.85.65: bytes=32 time=43ms TTL=50
Reply from 82.133.85.65: bytes=32 time=70ms TTL=50
Reply from 82.133.85.65: bytes=32 time=26ms TTL=50
Reply from 82.133.85.65: bytes=32 time=54ms TTL=50

Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 70ms, Average = 40ms

Netsource Origin Plus DSL 3MB
==================================================================================

Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:

4 27 ms 12 ms 11 ms 208.50.25.109
5 22 ms 21 ms 21 ms so0-0-0-2488M.ar3.LON2.gblx.net [67.17.71.25]
6 22 ms 23 ms 22 ms te1-3.cr05.tn5.bb.pipex.net [195.66.224.29]
7 23 ms 21 ms 22 ms ge-0-2-0.lon1-9.nildram.net [62.72.141.38]
8 23 ms 22 ms 21 ms jolt-gw.nildram.net [195.149.20.214]
9 24 ms 23 ms 26 ms secure.jolt.co.uk [82.133.85.65]

Trace complete.

Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=21ms TTL=56
Reply from 82.133.85.65: bytes=32 time=25ms TTL=56
Reply from 82.133.85.65: bytes=32 time=23ms TTL=56
Reply from 82.133.85.65: bytes=32 time=22ms TTL=56
Reply from 82.133.85.65: bytes=32 time=22ms TTL=56
Reply from 82.133.85.65: bytes=32 time=22ms TTL=56
Reply from 82.133.85.65: bytes=32 time=22ms TTL=56
Reply from 82.133.85.65: bytes=32 time=23ms TTL=56
Reply from 82.133.85.65: bytes=32 time=23ms TTL=56
Reply from 82.133.85.65: bytes=32 time=22ms TTL=56
Reply from 82.133.85.65: bytes=32 time=22ms TTL=56
Reply from 82.133.85.65: bytes=32 time=25ms TTL=56
Reply from 82.133.85.65: bytes=32 time=22ms TTL=56
Reply from 82.133.85.65: bytes=32 time=22ms TTL=56
Reply from 82.133.85.65: bytes=32 time=22ms TTL=56
Reply from 82.133.85.65: bytes=32 time=24ms TTL=56
Reply from 82.133.85.65: bytes=32 time=24ms TTL=56
Reply from 82.133.85.65: bytes=32 time=24ms TTL=56
Reply from 82.133.85.65: bytes=32 time=23ms TTL=56
Reply from 82.133.85.65: bytes=32 time=25ms TTL=56

Ping statistics for 82.133.85.65:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 25ms, Average = 22ms



Not exactly scientific in any way, but intresting to see the difference in pings, NTL is all over the place whilst Netsource is stable and low - ideal for Gaming

The funny thing is the routing, 9 hops on Netsource, 17 on NTL, no wonder I was getting a lot of packet loss and dropouts on games, sometimes 5-7% reported in game, now its so stable with 0% packetloss.

zilog_jones

IIRC cable broadband is a lot more prone to packet collisions, hence the erratic latency and packet loss.

That's very good pings for Netsource there! The best I usually get from UK game servers on BT is about 35-45ms.

bk

That is funny, I use to be with Netsource before moving to NTL. I did a similar test and found the opposite. NTL was significantly faster for me, but that was over a year ago so maybe Netsource has significantly improved. However it is rather expensive.

I use to absolutely hate the way that Netsource made you pay for a domain name, even if you didn't use it, I lost all trust in them after that.