Pings Dire!

Jeff · Apr 03, 2006, 15:06:54

Sync speed good, throughput good but pings dire! Not that I`m much bothered, just wondered if anyone else has noticed?

Pinging www.idnet.co.uk [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=153ms TTL=62
Reply from 212.69.36.10: bytes=32 time=126ms TTL=62
Reply from 212.69.36.10: bytes=32 time=149ms TTL=62
Reply from 212.69.36.10: bytes=32 time=124ms TTL=62

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

sobranie · Apr 03, 2006, 15:16:00

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\wiggy>ping 212.69.36.10

Pinging 212.69.36.10 with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=17ms TTL=62
Reply from 212.69.36.10: bytes=32 time=17ms TTL=62
Reply from 212.69.36.10: bytes=32 time=16ms TTL=62
Reply from 212.69.36.10: bytes=32 time=19ms TTL=62

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

Jeff · Apr 03, 2006, 15:31:29

That`s better Rick ... my pings have never been tremendous though I might add

Jeff · Apr 03, 2006, 23:29:17

Better now:

Pinging www.idnet.co.uk [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=25ms TTL=62
Reply from 212.69.36.10: bytes=32 time=26ms TTL=62
Reply from 212.69.36.10: bytes=32 time=25ms TTL=62
Reply from 212.69.36.10: bytes=32 time=26ms TTL=62

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

Bill · Apr 03, 2006, 23:37:09

Pinging www.idnet.co.uk [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=13ms TTL=62
Reply from 212.69.36.10: bytes=32 time=12ms TTL=62
Reply from 212.69.36.10: bytes=32 time=12ms TTL=62
Reply from 212.69.36.10: bytes=32 time=12ms TTL=62

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

Danni · Apr 04, 2006, 23:21:39

danni@Matilda:~$ ping idnet.co.uk -c 4
PING idnet.co.uk (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=62 time=43.6 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=62 time=45.0 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=62 time=43.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=62 time=44.4 ms

--- idnet.co.uk ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 43.541/44.171/45.096/0.637 ms
danni@Matilda:~$

Not bad considering I'm on wireless, and much better than they used to be.

I'm sure if I used the downstairs computer it would be better. I did have some problems viewing websites earlier, but that seems to have resolved itself.

MarkZX12R · Apr 05, 2006, 08:19:39

PING 212.69.36.10 (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=63 time=20.0 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=63 time=20.0 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=63 time=10.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=63 time=20.0 ms

--- 212.69.36.10 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 10.0/17.5/20.0 ms

Coopes · Apr 05, 2006, 08:38:23

Pinging 212.69.36.10 with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=43ms TTL=62
Reply from 212.69.36.10: bytes=32 time=37ms TTL=62
Reply from 212.69.36.10: bytes=32 time=40ms TTL=62
Reply from 212.69.36.10: bytes=32 time=36ms TTL=62

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0%
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 43ms, Average = 39ms

Adam · Apr 06, 2006, 14:39:19

My pings have also recently jumped up a bit, I'm getting about 40ms to idnet.net now, whereas before I was getting ~20ms. Just wondering here, but perhaps interleaving is ON?

Adam

Coopes · Apr 06, 2006, 15:24:12

This is the read out from my router
DSL Status
Connection Status Connected
Upstream Rate (Kbps) 448
Downstream Rate (Kbps) 2720
US Margin 21
DS Margin 0
Modulation MMODE
LOS Errors 0
DS Line Attenuation 52
US Line Attenuation 60
Path Mode Interleaved

MarkZX12R · Apr 06, 2006, 15:29:52

ADSL Link      Downstream      Upstream
Connection Speed 4320 kbps      448 kbps
Line Attenuation    53 db      15.5 db
Noise Margin      7 db      21 db

And still pinging IDNet at 20ms and speed is 3431 kbps

Adam · Apr 06, 2006, 15:35:11

I'm not really bothered either way, I'm just looking for an explanation for the ping rises.

Adam

[Edit]: Called and was informed it is off, back on the hunt for the problem.

kuja · Apr 06, 2006, 16:55:43

Yeah my pings went up too earlier. A router reboot seemed to fix it. I traced the server where I was playing and I was getting 156ms on the first hop (idnet one)..

Jeff · Apr 06, 2006, 23:55:55

But look at the last line of Coopes stats

Or is each individual different?

div0 · Apr 13, 2006, 12:37:10

Quote from: Bill on Apr 03, 2006, 23:37:09
Pinging www.idnet.co.uk [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=13ms TTL=62
Reply from 212.69.36.10: bytes=32 time=12ms TTL=62
Reply from 212.69.36.10: bytes=32 time=12ms TTL=62
Reply from 212.69.36.10: bytes=32 time=12ms TTL=62

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

NICE

now where do i have to move to exactly?

Bill · Apr 13, 2006, 12:58:39

Quotenow where do i have to move to exactly?

Abingdon area of South Oxfordshire, 01235 code. That's as close as I'm saying.

div0 · Apr 13, 2006, 14:06:17

had to be down south tbh!

Jeff · Apr 13, 2006, 22:37:00

Aye, there`s always a down side