Ping times Jan 28 onwards

[Rik]

Havn't posted a screeny of my ping results from the Command Prompt because I don't know how to do it. Do plenty of cut/copy and paste but cannot seem to figure this one out  

Right-click on the title bar of the CMD window, Ian, then Edit > Select All. That will highlight the text, hit Enter to copy it.

[Steve]

Seems to be poor across the board I'm on .net and ping times are up by at least a 100ms

[juiceuk]

Tracing route to www.idnet.co.uk [212.69.36.10]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  192.168.1.1
  2   215 ms   152 ms   154 ms  telehouse-gw4-lo2.idnet.net [212.69.63.97]
  3   147 ms   128 ms   126 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   137 ms   152 ms   149 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   132 ms   120 ms   112 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   124 ms   113 ms   108 ms  www.idnet.net [212.69.36.10]

Trace complete.

I normally get pings in the low twenties. Anyone know whats causing the delay to the first hop. When I'm doing a tracert from XP its between 2-3ms but doing it from vista 64bit it's sometimes 7-12ms. GW5 by the way.

[Rik]

No ideas at this time, Juice. The problem is affecting DSL4 and GW5, and has a wide geographical spread, so I'd suspect a router is acting up in some way - but I'm probably wrong.

[DarkStar]

where do you pings too?

A variety of places,
bbc.co.uk
idnet.net
thinkbroadband
several others as I think of them out of curiosity, all UK based.
Now have the PingGraph running, will leave it going for a while.

Ian

[Ray]

Here's my plot, Rik, for the last hour or so: -


[attachment deleted by admin]

[JB]

Not too good here either, on gw5 in Cheshire. Well above normal times and browsing is noticeably clunky.


[attachment deleted by admin]

[Rik]

Here's my plot, Rik, for the last hour or so: -

Thanks, Ray - looks very much like mine.

[Rik]

Not too good here either, on gw5 in Cheshire. Well above normal times and browsing is noticeably clunky.

I'm finding the forum quite sluggish, JB, and sites with multiple servers, eg ads, are taking a long time to complete.

[JB]

Just the same here Rik.

[Rik]

I've advised support, so it's sit back and wait now.

[juiceuk]

Sorry, by first hop I meant the delay to MY router IP. It's 2-3ms when I do a tracert from my XP PC and it's the same or sometimes 7-12ms from Vista 64bit. Just wondered if anyone knew why. I'm sure IDNet will have my pings back to normal soon. I'm just happy BT finally got to our new pipe.

[Rik]

Is it a Speedtouch, Juice?

[juiceuk]

It's a Zyxel P-660HWP.

[Rik]

Don't know, in that case. Speedtouches give a long first hop for some reason, I can only think it's similar for the Zyxel.

[cjenkins]

Just wanted to throw my name into the mix of people having problems.

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

Reply from 212.58.224.138: bytes=32 time=160ms TTL=121
Reply from 212.58.224.138: bytes=32 time=160ms TTL=121
Reply from 212.58.224.138: bytes=32 time=150ms TTL=121
Reply from 212.58.224.138: bytes=32 time=154ms 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 = 150ms, Maximum = 160ms, Average = 156ms

First time I've had this particular problem with IDNet. Ping times was the main reason I left Virgin for IDnet nearly 18 months ago so hope it gets sorted quickly.

[Rik]

I suspect it's an unexpected result of last week's upgrades, CJ, I'm sure it will be fixed asap.

[Philip]

for what it's worth, mine seem ok

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

C:\Users\Philip>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=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=30ms TTL=59
Reply from 212.69.36.10: bytes=32 time=44ms 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 = 30ms, Maximum = 44ms, Average = 34ms

[VaderDSL]

It's getting there

[DarkStar]

Seem to have improved

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

C:\Documents and Settings\Owner>ping idnet.net

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

Reply from 212.69.36.10: bytes=32 time=83ms TTL=59
Reply from 212.69.36.10: bytes=32 time=64ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59
Reply from 212.69.36.10: bytes=32 time=39ms 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 = 35ms, Maximum = 83ms, Average = 55ms

C:\Documents and Settings\Owner>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=41ms TTL=122
Reply from 212.58.224.138: bytes=32 time=36ms TTL=122
Reply from 212.58.224.138: bytes=32 time=36ms TTL=122
Reply from 212.58.224.138: bytes=32 time=34ms 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 = 34ms, Maximum = 41ms, Average = 36ms

Thanks for instructions Rik. 

Ian

[cjenkins]

Yep just now things are seeming a lot better:

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

Reply from 212.58.224.138: bytes=32 time=78ms TTL=121
Reply from 212.58.224.138: bytes=32 time=40ms TTL=121
Reply from 212.58.224.138: bytes=32 time=84ms TTL=121
Reply from 212.58.224.138: bytes=32 time=60ms 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 = 40ms, Maximum = 84ms, Average = 65ms

They were obviously waiting for me to post about it before acting 

[Rik]

I concur, times have returned pretty much to normal here.

[VaderDSL]

Would it be the new router doing some load balancing juggling while spinning plates and breathing fire that cause the higher than normal pings?

[Rik]

Something like that, I suspect, Vader. There's a lot going on with the Hostlink and the new central connecting to the network, and new routers to support them. It could be anything in that mix, I am not going to guess.

[Rik]

Latest result:

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

Very much what I'd expect to see.