Ping times Jan 28 onwards

[Philip]

reboot worked for me 

[Rik]

Same here, Philip.

[JB]

Can you run PingGraph, JB. If so, let IDNet have the results of that.

Will do Rik. I'm just about to go out for a few drinks and a curry with a group of friends and will be back late. I'll do it tomorrow if I detect problems then.

[davee]

thanks, wasn't sure to put my ip up or not there.

i have rebooted my router a number of times.  a few times it seemed to clear to thing momemtarily, but then the pings cruised up high again on me.    i shall wait a some amount of time for idnet to fix matters, but my gaming time is also effectly money to me - as i pay for co-location on a rack server for my clans servers, so i cannot play in what i am paying out a fair amount for elsewhere,  see my situ

[Rik]

Will do Rik. I'm just about to go out for a few drinks and a curry with a group of friends and will be back late. I'll do it tomorrow if I detect problems then.

Have you seen Simon's post about the central?

[Philip]

about normal now

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

C:\Users\Philip>

[Rik]

thanks, wasn't sure to put my ip up or not there.

i have rebooted my router a number of times.  a few times it seemed to clear to thing momemtarily, but then the pings cruised up high again on me.    i shall wait a some amount of time for idnet to fix matters, but my gaming time is also effectly money to me - as i pay for co-location on a rack server for my clans servers, so i cannot play in what i am paying out a fair amount for elsewhere,  see my situ

IDNet are aware of the frustration, Davee, and are working over the weekend to try and fix things. Unfortunately, ever since they added a new central, BT's software seems to have conspired against them, congestion one pipe and leaving the others empty.  

[Rik]

about normal now

Me too, I've been averaging 24.5ms for the past half hour.

[Philip]

Me too, I've been averaging 24.5ms for the past half hour.

we're on the right side now

[Rik]

I'm straight up the middle.

[cheekyjinx]

Hello guys,

I'm experiencing the high latency issues too, have been getting 140-220 the last week or so, although yesterday it was sub 100, I'm now back up to 190+ pinging 212.69.36.3


Apologies If I am posting out of turn or if this is an already *resolved* issue and my impatience is getting the better of me, I've only ever visited the forums here when I've been having problems with my IDnet connection (thankfully not often )- although I believe I am observing the rules here :]

[Rik]

No problems, Cheeky, welcome to the forum.

As you'll see a few posts back, IDNet have been hit today by one half of one of their centrals becoming overloaded while the other half was running light. BT's software is meant to even the connections out, but hasn't. They are working to fix it.

[Glenn]

One of the VPs on one of our Centrals has managed to attract double the normal number of login sessions. A reboot of your router should get you onto another VP whilst we try to get this sorted out, again.
Simon

[cheekyjinx]

Hi Rik,

Ah gotcha and thanks for the speedy response! You must live on here  

Thanks again,
jinx

[Rik]

My wife thinks I do.

[Mohux_Jnr]

Reboot made absolutely no difference to mine........180 before, 180 after reboot. T.B.H within an hour they creep back up anyway so constantly rebooting in order to fix a problem obviously not my end is like pee-ing into the wind.
Walking the dog, so will shut down while I am gone and hope the cyber fairies pay my connection a visit whilst it is sleeping.

[Rik]

Let IDNet know, Mo.

[DarkStar]

My pings have been behaving themselves today, mostly around 35 > 45 except for a spell between 1200 and 1220 when they were 100 > 200 ish. Don't have a ping graph to post, accidentally switched it off instead of minimizing it  
Have not had any drops or disconnections and a speed test at BBMax gave me over 2000 kbps, the first time over 2000 on my present IP Profile. So, things are looking better here, get the weekend out of the way and hopefully everyone will be back to normal

Ian

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=36ms TTL=59
Reply from 212.69.36.10: bytes=32 time=38ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms 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 = 36ms, Maximum = 39ms, Average = 37ms

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

Tracing route to idnet.net [212.69.36.10]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2   112 ms    50 ms    51 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
 3    36 ms    40 ms    37 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4    44 ms    37 ms    35 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    47 ms    47 ms    51 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 6    36 ms    36 ms    42 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Rik]

Don't have a ping graph to post, accidentally switched it off instead of minimizing it  

I do that regularly, Ian.

[cheekyjinx]

Idnet are working their magic! My latency's come back down from the 200+ area to the 30's-40's wooooooooooooooooooo  go idnet!

[Rik]

 

I'm averaging 25ms for the past hour.

[shazzy]

Reboot worked for me to.

[Rik]

It sounds like we're getting off the wrong half of the central.

[juiceuk]

This is awful! After a reboot as well.

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     *      130 ms   129 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   144 ms   162 ms   144 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   188 ms   192 ms   198 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   184 ms   188 ms   193 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   160 ms   180 ms   172 ms  www.idnet.net [212.69.36.10]

Trace complete.

Getting worse not better.

[Rik]

Let IDNet know, Juice, they can take a look at which central you are on and see if there's an obvious issue.