Ping times Jan 28 onwards

[David]

http://www.kitz.co.uk/routers/netgeardg834_interleaving.htm

Have you tried this bridgej ?

[bridgej]

Well somehow I manage to increase the number of pings so I could copy and paste it while it was still going through the motions, they seem a bit all over the place to me:


Reply from 212.69.36.10: bytes=32 time=138ms TTL=59
Reply from 212.69.36.10: bytes=32 time=130ms TTL=59
Reply from 212.69.36.10: bytes=32 time=127ms TTL=59
Reply from 212.69.36.10: bytes=32 time=132ms TTL=59
Reply from 212.69.36.10: bytes=32 time=170ms TTL=59
Reply from 212.69.36.10: bytes=32 time=163ms TTL=59
Reply from 212.69.36.10: bytes=32 time=171ms TTL=59
Reply from 212.69.36.10: bytes=32 time=161ms TTL=59
Reply from 212.69.36.10: bytes=32 time=143ms TTL=59
Reply from 212.69.36.10: bytes=32 time=99ms TTL=59
Reply from 212.69.36.10: bytes=32 time=89ms TTL=59
Reply from 212.69.36.10: bytes=32 time=109ms TTL=59
Reply from 212.69.36.10: bytes=32 time=100ms TTL=59
Reply from 212.69.36.10: bytes=32 time=92ms TTL=59
Reply from 212.69.36.10: bytes=32 time=95ms TTL=59
Reply from 212.69.36.10: bytes=32 time=138ms TTL=59
Reply from 212.69.36.10: bytes=32 time=153ms TTL=59
Reply from 212.69.36.10: bytes=32 time=139ms TTL=59
Reply from 212.69.36.10: bytes=32 time=145ms TTL=59
Reply from 212.69.36.10: bytes=32 time=175ms TTL=59
Reply from 212.69.36.10: bytes=32 time=157ms TTL=59
Reply from 212.69.36.10: bytes=32 time=169ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=116ms TTL=59
Reply from 212.69.36.10: bytes=32 time=119ms TTL=59
Reply from 212.69.36.10: bytes=32 time=140ms TTL=59
Reply from 212.69.36.10: bytes=32 time=147ms TTL=59
Reply from 212.69.36.10: bytes=32 time=111ms TTL=59
Reply from 212.69.36.10: bytes=32 time=128ms TTL=59
Reply from 212.69.36.10: bytes=32 time=123ms TTL=59
Reply from 212.69.36.10: bytes=32 time=112ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=159ms TTL=59
Reply from 212.69.36.10: bytes=32 time=149ms TTL=59
Reply from 212.69.36.10: bytes=32 time=132ms TTL=59
Reply from 212.69.36.10: bytes=32 time=104ms TTL=59
Reply from 212.69.36.10: bytes=32 time=152ms TTL=59
Reply from 212.69.36.10: bytes=32 time=130ms TTL=59
Reply from 212.69.36.10: bytes=32 time=124ms TTL=59
Reply from 212.69.36.10: bytes=32 time=120ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=93ms TTL=59
Reply from 212.69.36.10: bytes=32 time=144ms TTL=59
Reply from 212.69.36.10: bytes=32 time=147ms TTL=59
Reply from 212.69.36.10: bytes=32 time=163ms TTL=59
Reply from 212.69.36.10: bytes=32 time=137ms TTL=59
Reply from 212.69.36.10: bytes=32 time=154ms TTL=59

[bridgej]

http://www.kitz.co.uk/routers/netgeardg834_interleaving.htm

Have you tried this bridgej ?

That's getting tooooooo deep for me, thanks anyway

[David]

Your welcome 

[Rik]

Well somehow I manage to increase the number of pings so I could copy and paste it while it was still going through the motions, they seem a bit all over the place to me:

They're not good, Bridge. How far are you from London, do you know if your line is interleaved or if your exchange is congested? I suspect the best thing you can do is have a word with support and see what they can do to help you.

[bridgej]

They're not good, Bridge. How far are you from London, do you know if your line is interleaved or if your exchange is congested? I suspect the best thing you can do is have a word with support and see what they can do to help you.

I'm in Stratford, east London, E15, on the Stratford exchange. I don't know if the line is interleaved or if the exchange is congested I'm afraid. Here are my latest results now I know how to do it without the window closing:

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=62ms TTL=59
Reply from 212.69.36.10: bytes=32 time=85ms TTL=59
Reply from 212.69.36.10: bytes=32 time=68ms TTL=59
Reply from 212.69.36.10: bytes=32 time=74ms TTL=59
Reply from 212.69.36.10: bytes=32 time=96ms TTL=59
Reply from 212.69.36.10: bytes=32 time=117ms TTL=59
Reply from 212.69.36.10: bytes=32 time=132ms TTL=59
Reply from 212.69.36.10: bytes=32 time=145ms TTL=59
Reply from 212.69.36.10: bytes=32 time=101ms TTL=59
Reply from 212.69.36.10: bytes=32 time=128ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 62ms, Maximum = 145ms, Average = 100ms

[David]

Im on the Upton Park,which although is a different exchange I can walk to your place bridgej ? I would have thought they would have been better 

[davej99]

Routerstats full version from John Owen provides one button access to "Telnet Router" and gives an automatic statement of Netgear interleaving status, when you click "Connect." No install needed just run the .exe.

[bridgej]

Im on the Upton Park,which although is a different exchange I can walk to your place bridgej ? I would have thought they would have been better 

I blame the 2012 Olympics, they've probably cut through one of the cables on the building site.

[Rik]

On the public data (often wrong), Bridge, your exchange is not congested. I note, though, that it's just been enabled for WBC which may just be having an effect. Let support have your figures and mention that you are on a WBC-enabled exchange, they may be able to offer you a chance to test the new 'up to 24Mbps' service.

[David]

That did occur to me you are right in the midst of it there bridgej

[bridgej]

seems better now:


Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=40ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=33ms TTL=59
Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59
Reply from 212.69.36.10: bytes=32 time=34ms TTL=59
Reply from 212.69.36.10: bytes=32 time=32ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 42ms, Average = 35ms

[Rik]

That could be a sign of backhaul congestion at the exchange, Bridge. See if there's a pattern over the next few days.

[JB]

Well after a good few days mine are all over the place again. I am in Cheshire with an interleaved line on an uncongested exchange. Mine normally sit at about 32ms due to the interleaving and distance from London. Although I have a max speed profile and a downstream noise margin of 9db I never bothered to have interleaving turned off as I don't play games.

However, I am noticing (again) that web browsing is becoming sluggish.


[attachment deleted by admin]

[Rik]

This is my latest plot, JB. I can only suggest you have a word with support to see if they can do anything to help.

[attachment deleted by admin]

[ducky22]

Well after a good few days mine are all over the place again. I am in Cheshire with an interleaved line on an uncongested exchange. Mine normally sit at about 32ms due to the interleaving and distance from London. Although I have a max speed profile and a downstream noise margin of 9db I never bothered to have interleaving turned off as I don't play games.

However, I am noticing (again) that web browsing is becoming sluggish.

Ping statistics for 212.58.224.138:
    Packets: Sent = 43, Received = 42, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 62ms, Maximum = 184ms, Average = 128ms

I signed a contract with NTL:Telewest Business this morning... Rock solid (and 20mbit) from past and current experience. Unfortunately IDNet's issues haven't been resolved :-(.

[uxbod]

Just on another note :- http://www.theregister.co.uk/2009/02/18/sky_london/

[Rik]

Just goes to show it happens to everyone, Ux.

[Sebby]

Even so, I think that's the first major outage they've had, so not bad, all things considered.

[Rik]

Apologist.

[Sebby]

[Mohux_Jnr]

 

Another day down the swanny!. 3 reboots no change!.



[attachment deleted by admin]

[Rik]

Have you had a word with support?

[Mohux_Jnr]

No Rik, it just makes me feel a whole lot better moaning to you  .

I will give it another week before I get on the phone, I am sure they have enough on their plate!.

[Rik]

Most people have had their problems resolved now, so it would be worth a word to see what could be done to help you. My latest plot is below, you can see I'm averaging 23ms, with interleaving, and I don't game so it's not an issue to me.

[attachment deleted by admin]