cancel
Showing results for 
Search instead for 
Did you mean: 

Ping = 100....

MickHowes1
Grafter
Posts: 137
Registered: 31-10-2013

Ping = 100....

Pinging bbc.co.uk [212.58.253.67] with 32 bytes of data:
Reply from 212.58.253.67: bytes=32 time=93ms TTL=120
Reply from 212.58.253.67: bytes=32 time=70ms TTL=120
Reply from 212.58.253.67: bytes=32 time=70ms TTL=120
Reply from 212.58.253.67: bytes=32 time=69ms TTL=120
Reply from 212.58.253.67: bytes=32 time=90ms TTL=120
Reply from 212.58.253.67: bytes=32 time=90ms TTL=120
Reply from 212.58.253.67: bytes=32 time=70ms TTL=120
Reply from 212.58.253.67: bytes=32 time=30ms TTL=120
Reply from 212.58.253.67: bytes=32 time=98ms TTL=120
Reply from 212.58.253.67: bytes=32 time=97ms TTL=120
Reply from 212.58.253.67: bytes=32 time=97ms TTL=120
Reply from 212.58.253.67: bytes=32 time=96ms TTL=120
Reply from 212.58.253.67: bytes=32 time=95ms TTL=120
Reply from 212.58.253.67: bytes=32 time=94ms TTL=120
Reply from 212.58.253.67: bytes=32 time=96ms TTL=120
Reply from 212.58.253.67: bytes=32 time=96ms TTL=120
Reply from 212.58.253.67: bytes=32 time=95ms TTL=120
Reply from 212.58.253.67: bytes=32 time=85ms TTL=120
Reply from 212.58.253.67: bytes=32 time=86ms TTL=120
Reply from 212.58.253.67: bytes=32 time=85ms TTL=120
Reply from 212.58.253.67: bytes=32 time=85ms TTL=120
Reply from 212.58.253.67: bytes=32 time=86ms TTL=120
Reply from 212.58.253.67: bytes=32 time=84ms TTL=120
Reply from 212.58.253.67: bytes=32 time=87ms TTL=120
Reply from 212.58.253.67: bytes=32 time=91ms TTL=120
Reply from 212.58.253.67: bytes=32 time=90ms TTL=120
Reply from 212.58.253.67: bytes=32 time=71ms TTL=120
Reply from 212.58.253.67: bytes=32 time=71ms TTL=120
Reply from 212.58.253.67: bytes=32 time=70ms TTL=120
Reply from 212.58.253.67: bytes=32 time=31ms TTL=120
Reply from 212.58.253.67: bytes=32 time=33ms TTL=120
Reply from 212.58.253.67: bytes=32 time=81ms TTL=120
Reply from 212.58.253.67: bytes=32 time=84ms TTL=120
Reply from 212.58.253.67: bytes=32 time=61ms TTL=120
Reply from 212.58.253.67: bytes=32 time=96ms TTL=120
Reply from 212.58.253.67: bytes=32 time=55ms TTL=120
Reply from 212.58.253.67: bytes=32 time=59ms TTL=120
Reply from 212.58.253.67: bytes=32 time=32ms TTL=120
Reply from 212.58.253.67: bytes=32 time=48ms TTL=120
Reply from 212.58.253.67: bytes=32 time=84ms TTL=120
Reply from 212.58.253.67: bytes=32 time=85ms TTL=120
Reply from 212.58.253.67: bytes=32 time=80ms TTL=120
Reply from 212.58.253.67: bytes=32 time=43ms TTL=120
Reply from 212.58.253.67: bytes=32 time=79ms TTL=120
Reply from 212.58.253.67: bytes=32 time=79ms TTL=120
Reply from 212.58.253.67: bytes=32 time=92ms TTL=120
Reply from 212.58.253.67: bytes=32 time=87ms TTL=120
Reply from 212.58.253.67: bytes=32 time=74ms TTL=120
Reply from 212.58.253.67: bytes=32 time=74ms TTL=120
Reply from 212.58.253.67: bytes=32 time=73ms TTL=120
Reply from 212.58.253.67: bytes=32 time=72ms TTL=120
Reply from 212.58.253.67: bytes=32 time=75ms TTL=120
Reply from 212.58.253.67: bytes=32 time=75ms TTL=120
Reply from 212.58.253.67: bytes=32 time=74ms TTL=120
Reply from 212.58.253.67: bytes=32 time=46ms TTL=120
Reply from 212.58.253.67: bytes=32 time=64ms TTL=120
Reply from 212.58.253.67: bytes=32 time=94ms TTL=120
Reply from 212.58.253.67: bytes=32 time=93ms TTL=120
Reply from 212.58.253.67: bytes=32 time=98ms TTL=120
Reply from 212.58.253.67: bytes=32 time=97ms TTL=120
Reply from 212.58.253.67: bytes=32 time=96ms TTL=120
Reply from 212.58.253.67: bytes=32 time=73ms TTL=120
Reply from 212.58.253.67: bytes=32 time=58ms TTL=120
Reply from 212.58.253.67: bytes=32 time=86ms TTL=120
Reply from 212.58.253.67: bytes=32 time=72ms TTL=120
Reply from 212.58.253.67: bytes=32 time=79ms TTL=120
Reply from 212.58.253.67: bytes=32 time=81ms TTL=120
Reply from 212.58.253.67: bytes=32 time=83ms TTL=120
Reply from 212.58.253.67: bytes=32 time=82ms TTL=120
Reply from 212.58.253.67: bytes=32 time=82ms TTL=120
Reply from 212.58.253.67: bytes=32 time=53ms TTL=120
Reply from 212.58.253.67: bytes=32 time=88ms TTL=120
Reply from 212.58.253.67: bytes=32 time=87ms TTL=120
Reply from 212.58.253.67: bytes=32 time=84ms TTL=120
Reply from 212.58.253.67: bytes=32 time=85ms TTL=120
Reply from 212.58.253.67: bytes=32 time=86ms TTL=120
Reply from 212.58.253.67: bytes=32 time=84ms TTL=120
Reply from 212.58.253.67: bytes=32 time=87ms TTL=120
Reply from 212.58.253.67: bytes=32 time=90ms TTL=120
Reply from 212.58.253.67: bytes=32 time=90ms TTL=120
Reply from 212.58.253.67: bytes=32 time=88ms TTL=120
Reply from 212.58.253.67: bytes=32 time=87ms TTL=120
Reply from 212.58.253.67: bytes=32 time=87ms TTL=120
Reply from 212.58.253.67: bytes=32 time=92ms TTL=120
Reply from 212.58.253.67: bytes=32 time=31ms TTL=120
Reply from 212.58.253.67: bytes=32 time=31ms TTL=120
Reply from 212.58.253.67: bytes=32 time=88ms TTL=120
Reply from 212.58.253.67: bytes=32 time=68ms TTL=120
Reply from 212.58.253.67: bytes=32 time=98ms TTL=120
Reply from 212.58.253.67: bytes=32 time=86ms TTL=120
Reply from 212.58.253.67: bytes=32 time=84ms TTL=120
Reply from 212.58.253.67: bytes=32 time=80ms TTL=120
Reply from 212.58.253.67: bytes=32 time=71ms TTL=120
Reply from 212.58.253.67: bytes=32 time=75ms TTL=120
Reply from 212.58.253.67: bytes=32 time=78ms TTL=120
Reply from 212.58.253.67: bytes=32 time=77ms TTL=120
Reply from 212.58.253.67: bytes=32 time=52ms TTL=120
Reply from 212.58.253.67: bytes=32 time=31ms TTL=120
Reply from 212.58.253.67: bytes=32 time=97ms TTL=120
Reply from 212.58.253.67: bytes=32 time=94ms TTL=120
Ping statistics for 212.58.253.67:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 98ms, Average = 77ms
My latest pingtest....
RANDOM SPIKES THAT LAST FOR LIKE 10-20 minutes at a time, fix it.
4 REPLIES
Plusnet Alumni (retired) orbrey
Plusnet Alumni (retired)
Posts: 10,540
Registered: 18-07-2007

Re: Ping = 100....

Hi there,
Sorry you're not happy with the ping times, but are they actually impacting your use of the broadband? I can see that interleaving is currently set to Auto on your line but it's running on fastpath so it's not that, as a result it'll take a while to track down and involve a fair amount of testing on both our and your parts to try and track it down, hence the initial question.
MickHowes1
Grafter
Posts: 137
Registered: 31-10-2013

Re: Ping = 100....

yes it affects the internet, everytime these spikes happen i get booted of XBL dc from skype, everything, happens between 5-7 everynight and does it randomly thru the day, monitor my line see when it5 spikes, go through my profile logs see whats happening at that time, change it.
Plusnet Alumni (retired) orbrey
Plusnet Alumni (retired)
Posts: 10,540
Registered: 18-07-2007

Re: Ping = 100....

If it was that simple, we would do - but as per my previous post unfortunately it's not. We can't see the pings as things stand, but if you set up a connection monitor on the thinkbroadband website (here: http://www.thinkbroadband.com/ping) we can take a look at that and see what we can do?
SuperZoom
Grafter
Posts: 353
Registered: 17-05-2013

Re: Ping = 100....

For me just now:
[tt]--- www.bbc.co.uk ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99127ms
rtt min/avg/max/mdev = 4.242/4.478/4.718/0.126 ms[/tt]

From that, it's fairly safe to conclude that it isn't the BBC and isn't PlusNet's network.
Probably either final mile or your exchange. Could be noise if it happens regularly as you describe. If you're on ADSL, that's something you can monitor for yourself.
I must say, Matt has been incredibly forgiving of your appalling attitude. Remarkable professionalism.