Unstable ping on gw5

Simon · Jul 13, 2009, 23:37:52

Sorry for poor spelling - bloody phone!

Wags · Jul 13, 2009, 23:41:26

Thanks for the welcome

My router stats:

DSL Status:           Up
              DSL Modulation Mode:       GDMT
              DSL Path Mode:         FAST
              Downstream Rate:       3552 Kbps
              Upstream Rate:         448 Kbps
              Downstream Margin:       9 db
              Upstream Margin:       22 db
              Downstream Line Attenuation:      36
              Upstream Line Attenuation:      20
              Downstream Transmit Power:      0
              Upstream Transmit Power:      0

I will do a speed test

Sebby · Jul 14, 2009, 00:08:12

Interleaving is off, which is good for pings. The sync seems low for the attenuation. It's probably not what's affecting the pings, but have you ever tried the test socket or removing ring wires?

MarkE · Jul 14, 2009, 00:20:36

yeh 12am superb pings here,oh the wonder of isps etc and Bt

thats multiplay.co.uk

Reply from 85.236.96.22: bytes=32 time=141ms TTL=124
Reply from 85.236.96.22: bytes=32 time=182ms TTL=124
Reply from 85.236.96.22: bytes=32 time=149ms TTL=124
Reply from 85.236.96.22: bytes=32 time=147ms TTL=124

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

Still wish yours was this dire Trophymick....joker

dujas · Jul 14, 2009, 00:38:49

gw5 ping had been fine earlier in the evening, but just tested at 12.30am and I'm averaging 135ms to www.idnet.net. Rebooted the router and the average dropped to 43ms but that's still high considering it's past midnight.

MarkE · Jul 14, 2009, 00:45:23

tried a router reboot,same problems here

dujas · Jul 14, 2009, 00:58:31

Seems to have settled now (12.56am), average is 21ms to Idnet and Multiplay

glen · Jul 14, 2009, 01:46:57

Same problems here too,but pings have dropped to about 50-60 for now, but it's been like this for weeks now.

Gary · Jul 14, 2009, 09:07:26

Well Pings are up for me this morning

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=142ms TTL=59
Reply from 212.69.36.10: bytes=32 time=177ms TTL=59
Reply from 212.69.36.10: bytes=32 time=174ms TTL=59
Reply from 212.69.36.10: bytes=32 time=124ms TTL=59

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 = 177ms, Average = 154ms

I guess this is part of the issues seen with IDnet at the moment

Throughput is not great either but not as bad as some

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 4321 kbps

Rik · Jul 14, 2009, 10:05:00

Quote from: bobleslie on Jul 13, 2009, 20:43:48
Interesting. I was told WBC was only on GW6. Presumably it's now been added to GW5 as well?

Yes.

Rik · Jul 14, 2009, 10:06:15

Quote from: Gary on Jul 14, 2009, 09:07:26
Well Pings are up for me this morning

One central failed for a few minutes overnight, which means everyone re-connected to the other one, so there is going to be congestion until the network is re-balanced. Re-boot your router, should do the trick...

quandam · Jul 14, 2009, 10:11:04

Worst it has ever been. Posted my BT test result yesterday, unable to get on it since then. Contacted support yesterday (see earlier post) no reply as yet.

Below is a speedtest.net result a few minutes ago.

Rik · Jul 14, 2009, 10:12:18

Re-boot your router, Q, see my post above.

quandam · Jul 14, 2009, 10:20:59

Rik

Apologies, missed your post while setting up mine. Yes, once again, you are right, see result below

Thanks

Rik · Jul 14, 2009, 10:21:35

That's better.

quandam · Jul 14, 2009, 10:23:09

A lot lot better

jameshurrell · Jul 14, 2009, 10:23:46

Quote from: Rik on Jul 14, 2009, 10:12:18
Re-boot your router, Q, see my post above.

Agreed. I had pings averaging 160 - 170 to idnet.com this morning. Just rebooted the router:

Pinging idnet.com [212.69.36.10] with 32 bytes of data:

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

Ping statistics for 212.69.36.10:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms

On GW6.

Rik · Jul 14, 2009, 10:24:00

It makes me wonder if there was a fault developing on GW5 which finally caused it to fail last night?

Gary · Jul 14, 2009, 10:30:01

Quote from: Rik on Jul 14, 2009, 10:06:15
One central failed for a few minutes overnight, which means everyone re-connected to the other one, so there is going to be congestion until the network is re-balanced. Re-boot your router, should do the trick...

Thanks Rik

pings are better now throughput still feels sluggish but I guess thats to be expected.

Gary · Jul 14, 2009, 10:32:04

Quote from: Rik on Jul 14, 2009, 10:24:00
It makes me wonder if there was a fault developing on GW5 which finally caused it to fail last night?

Sounds like its possible, what happened to GW6 Rik?

Rik · Jul 14, 2009, 10:34:37

Everyone connected to it.

Gary · Jul 14, 2009, 10:40:47

Quote from: Rik on Jul 14, 2009, 10:34:37
Everyone connected to it.

And that broke down last time.......

Rik · Jul 14, 2009, 10:41:15

So far so good, except for congestion/poor pings.

Gary · Jul 14, 2009, 10:42:07

Quote from: Rik on Jul 14, 2009, 10:41:15
So far so good, except for congestion/poor pings.

then Rik.

Simon · Jul 14, 2009, 11:01:05

My pings were also high this morning:

Pinging bbc.co.uk [212.58.254.252] with 32 bytes of data:

Reply from 212.58.254.252: bytes=32 time=165ms TTL=249
Reply from 212.58.254.252: bytes=32 time=167ms TTL=249
Reply from 212.58.254.252: bytes=32 time=176ms TTL=249
Reply from 212.58.254.252: bytes=32 time=177ms TTL=249

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

following a router reboot:

Pinging bbc.co.uk [212.58.254.252] with 32 bytes of data:

Reply from 212.58.254.252: bytes=32 time=34ms TTL=249
Reply from 212.58.254.252: bytes=32 time=30ms TTL=249
Reply from 212.58.254.252: bytes=32 time=31ms TTL=249
Reply from 212.58.254.252: bytes=32 time=32ms TTL=249

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