Pings gone wild

Started by DarkStar, May 07, 2010, 17:59:21

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

DarkStar

After several months of my pings creeping along at between 30-35 I have this today. Only started PingGraph because browsing was a bit sluggish and a game I play was not working as usual. Anyone else seeing ping problems again or is it just me ???


[attachment deleted by admin]
Ian

Rik

Things are absolutely normal for me, Ian. Have you tried re-booting the router?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Lance

Mine look pretty normal too:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Lance>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=23ms TTL=58
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms 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 = 18ms, Maximum = 23ms, Average = 20ms

C:\Users\Lance>ping idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms 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 = 18ms, Maximum = 20ms, Average = 19ms

C:\Users\Lance>

Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

DarkStar

A bit late back, I've been for my tea  :food2:
I thought it had settled down but it's a bit erratic again now. My router was rebooted by BT  :eyebrow: just before midnight on Wednesday, the router internet connection light went out for about a minute and then came back on, bright red for 30 secs or so and then when I reconnected my connection speed had gone up. That was the third time at just before midnight since my exchange was WBC enabled that it has happened. The good thing is that my connection speed increases slightly each time, have moved up one BRAS profile so far but quite a long way to go to the next one.
I did wonder if BT playing about in the exchange could have upset the pings. The SNR is fairly stable, no problems there.
I am using OpenDNS so will change to the default settings to see if that makes any difference.
Watch this space  ;D

[attachment deleted by admin]
Ian

Steve

It could be just local congestion i.e iplayer use etc, post election.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Bill

http://www.thinkbroadband.com/news/i/4240.html


My speed and packet loss suffered yesterday during office hours (except during the lunch hour), and went back to normal at 5:15pm.

Flippin' office workers who want to track the election updates  :mad:
Bill
BQMs-  IPv4  IPv6

DarkStar

Back to normal this morning. As Bill and Steve have pointed out this could well have been due to congestion. I have noticed a couple of times in the last month or so that my pings were a little bit erratic but nothing like yesterday. What may be making the situation worse is that my exchange is in a rapidly expanding town 3 miles away where several thousand houses have been built over the last few years (building still ongoing) without any apparent increase in exchange capacity. Since the exchange went WBC just over a month ago people tell me they are downloading and using iplayer on a much increased scale. If BT haven't increased the bandwidth available through the exchange I suppose that would account for it.
Should find out for sure come the football world cup  :po:

[attachment deleted by admin]
Ian

Rik

I think we'll find out a lot about the network then, Ian.  :fingers:
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.