Ping Problems......same time of day, every day?.

[Mohux_Jnr]

 For 90% of the day my pings are fine and completely acceptable but between the hours of 4-6pm EVERY day without fail they rise from my normal 20-25 to over 100. This has been going on ever since the upgrade and wondered if we just have to live with it or can somebody explain why?. I cannot believe it is just down to congestion with the post school and works traffic coming online, as it is regular as clockwork.........4pm without fail.

A reboot of the router sorts it out but having to do this everyday and disconnect from gameplay etc is becoming tiresome.

I will run a ping-graph tomorrow between 3.30pm-4-30pm and you will see my problem.

[Rik]

Have a word with support, Mo, they may be able to see something from their end (though it does sound like exchange congestion). Fwiw, my pings have been very stable for weeks now.

[Lance]

Indeed if it was a widespread problem we would have had lots of posts on here by now. Are you sure there isn't something scheduled to check for updates at that time?

[Glenn]

Or an automated back up etc

[Sebby]

I think it just sounds like exchange congestion, but it's worth checking with IDNet.

[davee]

we had this a few months back...and its BACK!   what is going on plz?   before it was a new pipe/something with bt new equipment causing too many logins to a pipe.   And lately for the last week again my pings have been bouncing high.   for gaming its ruining it for me.
Can anyone in the know tell me if this is an "issue" again like before.   if this ping cruising high is gonna become a regular occurancy every so often i think i should move back to entanet!

[LesD]

I have just pinged IDNet with this result:

C:\Users\Les>ping www.idnet.com

Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms 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 = 26ms, Maximum = 36ms, Average = 29ms

C:\Users\Les>

This is pretty much in line with what I am used to seeing from here in  Stafford.

Just done another and it is much the same.

[Simon]

This is what I'm getting, which is pretty usual for my line:

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

C:\Documents and Settings\Simon>ping www.idnet.com

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

Reply from 212.69.36.10: bytes=32 time=45ms TTL=59
Reply from 212.69.36.10: bytes=32 time=45ms TTL=59
Reply from 212.69.36.10: bytes=32 time=44ms TTL=59
Reply from 212.69.36.10: bytes=32 time=43ms 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 = 43ms, Maximum = 45ms, Average = 44ms

C:\Documents and Settings\Simon>ping bbc.co.uk

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

Reply from 212.58.224.138: bytes=32 time=46ms TTL=121
Reply from 212.58.224.138: bytes=32 time=43ms TTL=121
Reply from 212.58.224.138: bytes=32 time=44ms TTL=121
Reply from 212.58.224.138: bytes=32 time=43ms TTL=121

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

[Lance]

I think the ping issues being reported are isolated cases and most likely down to the BT infrastructure. I make this assumption on the basis that when there is a problem at IDNet we normally get several people complaining, not just the odd one or two.

The only advice I can offer is, if you think your pings are poor, contact support and ask them to look into it for you.

[LesD]

C:\Documents and Settings\Simon>ping www.idnet.com

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



C:\Documents and Settings\Simon>ping bbc.co.uk

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

Why is it that you ping www.idnet.com but not www.bbc.co.uk

It is just the same for me so I have been having a bit of a play as follows:

C:\Users\Les>nslookup www.bbc.co.uk
Server:  home
Address:  192.168.1.254

Non-authoritative answer:
Name:    www.bbc.net.uk
Address:  212.58.251.195
Aliases:  www.bbc.co.uk


C:\Users\Les>ping www.bbc.net.uk

Pinging www.bbc.net.uk [212.58.251.195] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 212.58.251.195:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Les>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=26ms TTL=122
Reply from 212.58.224.138: bytes=32 time=25ms TTL=122
Reply from 212.58.224.138: bytes=32 time=26ms TTL=122
Reply from 212.58.224.138: bytes=32 time=25ms TTL=122

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

C:\Users\Les>nslookup bbc.co.uk
Server:  home
Address:  192.168.1.254

Non-authoritative answer:
Name:    bbc.co.uk
Address:  212.58.224.138


C:\Users\Les>


All a bit of a mystery to me! 

[Simon]

Why is it that you ping www.idnet.com but not www.bbc.co.uk

I don't know, Les.  You don't need the www, but I guess I just automatically wrote it.   

[LesD]

I am as    you are!

Maybe Rik wll know tomorrow. 

[Simon]

Rik knows everything! 

[Steve]

Presumably the address is not ping able?

[Rik]

The BBC blocks pings if you put the www in, but not if you don't. Seems weird but it's been happening for about six weeks now.

[Simon]

Told you Rik would know! 

[esh]

I tend to get my peak around the 4pm mark too interestingly but it's not as high as that.



I've been monitoring the pings every 5 minutes for 240+ days now and the nasty period a while back is certainly over now, it's actually 5ms or so better than before the incident for me now, but I suspect it varies from exchange to exchange depending on traffic and so on.

[Rik]

I'm sure you're right, Esh. I average 22ms now, where it was 24ms.