High pings again

cmeerw · Jul 29, 2009, 18:50:43

Just wanted to mention that I am also occasionally getting high pings here (although it appears to be fine at the moment) - currently around 26 ms, but was >100 ms just an hour ago.

Rik · Jul 29, 2009, 18:52:03

Hi and welcome to the forum.

Is this a regular occurrence, does it tend to happen at specific times?

cmeerw · Jul 29, 2009, 18:59:45

So far I have seen these high ping times only in the early evening (5.30 pm to maybe 7 pm), probably 3 days per week for the last couple of weeks (since 22nd June).

Rik · Jul 29, 2009, 19:01:16

Have you talked to support at all? It might be worth a word, to check that you're not on a congested pipe, but given the timings, my hunch would be exchange congestion.

Glenn · Jul 29, 2009, 19:01:20

cmeerw · Jul 29, 2009, 21:12:02

Rik, I did contact support on the 22nd of June (even pointing out that it could be some kind of congestion), but I then didn't follow up when support requested a couple of BT speedtests (partly, because I couldn't get the BT speedtester working at all and partly because the problem then disappeared for the next couple of days).

I was kind of hoping that someone could easily check congestion levels in the exchange (or whereever - at specific times of the day). I mean, there must be better ways to analyse a problem than to use a dodgy Java speedtester applet in a web browser.

Simon · Jul 29, 2009, 22:16:43

You can check for exchange congestion yourself, here, but I think it's general, not specific to times. The BT Speedtests are a good indicator for IDNet, as to the status of your line, although, we all know what a pain they can be sometimes.

dujas · Jul 29, 2009, 22:23:03

Pings quite bad as I type to www.idnet.net, averaging 115ms.

*edit* It has resolved itself without router reboot, but remains a tad 'spikey'.

Lance · Jul 29, 2009, 22:58:08

It's BT who require the speedtests I believe.

Sebby · Jul 29, 2009, 23:42:27

Ray · Jul 30, 2009, 08:32:23

Rik · Jul 30, 2009, 08:39:58

Quote from: cmeerw on Jul 29, 2009, 21:12:02
I was kind of hoping that someone could easily check congestion levels in the exchange (or whereever - at specific times of the day). I mean, there must be better ways to analyse a problem than to use a dodgy Java speedtester applet in a web browser.

The speed tests do a bit more than that, and are the only evidence BT accept of a problem, unfortunately.

netn00b · Jul 30, 2009, 13:16:47

Quote from: Simon on Jul 29, 2009, 22:16:43
You can check for exchange congestion yourself, here, but I think it's general, not specific to times. The BT Speedtests are a good indicator for IDNet, as to the status of your line, although, we all know what a pain they can be sometimes.

looking at my exchange it says something called Virtual Paths are Red.....see below

--------------------------------------------
BT is reporting that some of the virtual paths at this exchange are not operating within BT Wholesale's planning guidance, although they are still operating within the product specification.

At busy times, your ADSL connection may operate at a reduced speed, although not all customers on your exchange may be affected. You should only contact support if there is no current ETA date set.

The ETA fix time is: 18 Jun 09

Record last updated: 12 Jun 09
--------------------------------------

Given my connection and speed recently seem poor, plus numerous disconnections whilst online should I moan ? The ETA is long gone by a month ?

Rik · Jul 30, 2009, 13:18:04

You can try, but BT do things at their own speed come what may. That said, there are signs that things are beginning to happen.

Glenn · Jul 30, 2009, 17:23:34

I'm a happy chappie sort of. On Brian's request he asked for a ping graph with the laptop in safe mode, it gave the same results

So I swapped the laptop for another I have here with a broken screen, I ran the ping graph on there and it works.

All I need to do now is rebuild this W7rc laptop.

Thanks again Brian.

Rik · Jul 30, 2009, 17:26:55

So it was the laptop, Glenn?

Glenn · Jul 30, 2009, 17:28:25

It looks to be the case yes, no idea what is causing it though. I'm now only getting an odd spike every now and then.

Rik · Jul 30, 2009, 17:28:48

Was the lappy on mains power?

Glenn · Jul 30, 2009, 17:41:51

Yes but so is the other one, it's sat on the docking station, the only difference between them is one is a Dell D630 with W7, the working one is a Dell D620 with XP, other than that they shared all the power etc.

Rik · Jul 30, 2009, 17:47:01

I was just thinking that maybe the power supply was noisy. There goes another theory.

cjenkins · Jul 30, 2009, 22:13:33

This is now a fairly persistent problem for me. I've called support before (about a month ago), it was on a Sunday and was told to leave a message but nobody ever got back to me.

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

Reply from 212.69.36.10: bytes=32 time=174ms TTL=59
Reply from 212.69.36.10: bytes=32 time=173ms TTL=59
Reply from 212.69.36.10: bytes=32 time=166ms TTL=59
Reply from 212.69.36.10: bytes=32 time=199ms 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 = 166ms, Maximum = 199ms, Average = 178ms

juiceuk · Jul 30, 2009, 22:53:13

Was just about to fire up my gaming PC but I guess I won't bother now.

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

Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=172ms TTL=59
Reply from 212.69.36.10: bytes=32 time=171ms TTL=59
Reply from 212.69.36.10: bytes=32 time=163ms TTL=59
Reply from 212.69.36.10: bytes=32 time=184ms TTL=59
Reply from 212.69.36.10: bytes=32 time=122ms TTL=59
Reply from 212.69.36.10: bytes=32 time=126ms TTL=59
Reply from 212.69.36.10: bytes=32 time=161ms TTL=59
Reply from 212.69.36.10: bytes=32 time=182ms TTL=59
Reply from 212.69.36.10: bytes=32 time=148ms TTL=59
Reply from 212.69.36.10: bytes=32 time=165ms TTL=59
Reply from 212.69.36.10: bytes=32 time=140ms TTL=59
Reply from 212.69.36.10: bytes=32 time=193ms TTL=59
Reply from 212.69.36.10: bytes=32 time=180ms TTL=59
Reply from 212.69.36.10: bytes=32 time=189ms TTL=59
Reply from 212.69.36.10: bytes=32 time=186ms TTL=59
Reply from 212.69.36.10: bytes=32 time=167ms TTL=59
Reply from 212.69.36.10: bytes=32 time=140ms TTL=59
Reply from 212.69.36.10: bytes=32 time=142ms TTL=59
Reply from 212.69.36.10: bytes=32 time=169ms TTL=59

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

Gary · Jul 30, 2009, 23:22:55

Mine are high yet again

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

C:\Users\>ping www.idnet.net

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=98ms TTL=59
Reply from 212.69.36.10: bytes=32 time=93ms TTL=59
Reply from 212.69.36.10: bytes=32 time=87ms TTL=59
Reply from 212.69.36.10: bytes=32 time=100ms 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 = 87ms, Maximum = 100ms, Average = 94ms

This is now getting boring and b*oody annoying

juiceuk · Jul 30, 2009, 23:40:33

I don't think my IDNet connection has been the same since that new pipe. I'm gonna leave the router off for 30min and see if things change for the better.

C:\Documents and Settings\deano>ping www.idnet.net

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

Reply from 212.69.36.10: bytes=32 time=72ms TTL=59
Reply from 212.69.36.10: bytes=32 time=118ms TTL=59
Reply from 212.69.36.10: bytes=32 time=119ms TTL=59
Reply from 212.69.36.10: bytes=32 time=162ms 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 = 72ms, Maximum = 162ms, Average = 117ms

Gary · Jul 30, 2009, 23:44:46

Quote from: juiceuk on Jul 30, 2009, 23:40:33
I don't think my IDNet connection has been the same since that new pipe. I'm gonna leave the router off for 30min and see if things change for the better.

C:\Documents and Settings\deano>ping www.idnet.net

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

Reply from 212.69.36.10: bytes=32 time=72ms TTL=59
Reply from 212.69.36.10: bytes=32 time=118ms TTL=59
Reply from 212.69.36.10: bytes=32 time=119ms TTL=59
Reply from 212.69.36.10: bytes=32 time=162ms 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 = 72ms, Maximum = 162ms, Average = 117ms

I think that makes things worse as you get on a new pipe and it unbalances things yet again, but to be honest who knows anymore

it should not be like this at this time of night