Nildram users

MajorPart · 1 May 2006 at 20:22

Can someone who has nildram broadband please ping the folowing sites for me.

www.bbc.co.uk
www.multiplay.co.uk
www.nildram.net

And post what you got, no need for a load of yous to do it tho.
Thanks.

Pulsedriver · 1 May 2006 at 20:37

Pinging www.bbc.net.uk [212.58.224.121] with 32 bytes of data:

Reply from 212.58.224.121: bytes=32 time=13ms TTL=248
Reply from 212.58.224.121: bytes=32 time=13ms TTL=248
Reply from 212.58.224.121: bytes=32 time=13ms TTL=248
Reply from 212.58.224.121: bytes=32 time=13ms TTL=248

Ping statistics for 212.58.224.121:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 13ms, Average = 13ms

_________________________________________________________

Pinging core1.multiplay.co.uk [85.236.96.22] with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=14ms TTL=122
Reply from 85.236.96.22: bytes=32 time=15ms TTL=122
Reply from 85.236.96.22: bytes=32 time=15ms TTL=122
Reply from 85.236.96.22: bytes=32 time=12ms TTL=122

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 15ms, Average = 14ms

__________________________________________________________

Pinging www-v.nildram.net [195.149.33.68] with 32 bytes of data:

Reply from 195.149.33.68: bytes=32 time=14ms TTL=60
Reply from 195.149.33.68: bytes=32 time=13ms TTL=60
Reply from 195.149.33.68: bytes=32 time=13ms TTL=60
Reply from 195.149.33.68: bytes=32 time=14ms TTL=60

Ping statistics for 195.149.33.68:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms

tolien · 1 May 2006 at 20:41

It's probably worth pointing out that for any of the (more) decent ISPs (and Nildram's been one of those thus far), 99% of the latency you see is going to be between you and Nildram's side of the BT Centrals.

For example (picking Jolt as an example, not on Nildram nor in Aberdeen, but ho hum):

2 gauss-dsl.zen.net.uk (62.3.82.18) 30.478 ms 31.468 ms 32.568 ms
3 deleuze-ge-0-1-0-1.hq.zen.net.uk (62.3.80.161) 30.185 ms 30.070 ms 27.074 ms
4 suarez-so-0-0-0-0.te.zen.net.uk (62.3.80.62) 32.941 ms 42.967 ms 42.816 ms
5 g2-3.cr01.tn5.bb.pipex.net (195.66.224.29) 47.808 ms 41.742 ms 46.555 ms
6 ge-0-2-0.lon1-9.nildram.net (62.72.141.38) 42.128 ms 43.862 ms 40.309 ms
7 jolt-gw.nildram.net (195.149.20.214) 43.566 ms 39.864 ms 38.810 ms
8 secure.jolt.co.uk (82.133.85.65) 36.940 ms 37.414 ms 36.811 ms

So 6ms between Zen's Home Gateway and jolt versus 30ms between me and Zen's Home Gateway. I know which I'd be more concerned with.

MajorPart · 1 May 2006 at 23:10

Thanks!

malccy · 2 May 2006 at 09:26

My speed after the 13 day max trials concluded as 8mb with 6mb fail safe point - yesterday though everything went slow and now I can't get more than 3mb. Spoke to nildram and have to do the obligatory 4 speed tests at BT as well as email ping results.

Anyone know why this could have suddenly happened and whether anything will in reality be able to be done about it?

tolien · 2 May 2006 at 11:24

Just throughput, or has your sync rate dropped too?

malccy · 2 May 2006 at 17:44

Still says 8mb for line - today was only just getting over 1mb.

digitalis · 2 May 2006 at 17:50

Pinging www.bbc.net.uk [212.58.224.82] with 32 bytes of data:

Reply from 212.58.224.82: bytes=32 time=29ms TTL=249
Reply from 212.58.224.82: bytes=32 time=25ms TTL=249
Reply from 212.58.224.82: bytes=32 time=25ms TTL=249
Reply from 212.58.224.82: bytes=32 time=24ms TTL=249

Ping statistics for 212.58.224.82:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 29ms, Average = 25ms

---------------------------------------------------------------------------
Pinging core1.multiplay.co.uk [85.236.96.22] with 32 bytes of data:

Reply from 85.236.96.22: bytes=32 time=30ms TTL=123
Reply from 85.236.96.22: bytes=32 time=25ms TTL=123
Reply from 85.236.96.22: bytes=32 time=24ms TTL=123
Reply from 85.236.96.22: bytes=32 time=25ms TTL=123

Ping statistics for 85.236.96.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 30ms, Average = 26ms

---------------------------------------------------------------------------
Pinging www-v.nildram.net [195.149.33.68] with 32 bytes of data:

Reply from 195.149.33.68: bytes=32 time=29ms TTL=61
Reply from 195.149.33.68: bytes=32 time=24ms TTL=61
Reply from 195.149.33.68: bytes=32 time=24ms TTL=61
Reply from 195.149.33.68: bytes=32 time=24ms TTL=61

Ping statistics for 195.149.33.68:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 29ms, Average = 25ms

Hope this is of some use.

S.