Slow speeds -- anyone else having problems?

[LinLin]

My speeds are incredibly slow today. Supposed to be 8 Mbps and a dslzoneUK test just came in at 357 Kbps. Wow.

Anybody else having problems with speed?

LinLin

And another test from Speedtest.net gives this result --

[Rik]

Hi LinLin - see Tim's announcement, one central failed last night, you need to re-boot your router.

[LinLin]

Thanks, Rik.
Where do I find Tim's announcement, and how do I re-boot my router? Sorry, I'm a bit of a techno-dinosaur.

LL

[Glenn]

The announcement is here http://www.idnetters.co.uk/forums/index.php?topic=15153.0

To reboot the router, power it off then back on again.

[LinLin]

Ah, that's better.
Thank you!

[Rik]

If only every problem was that easy to solve.

[Fox]

If only every problem was that easy to solve.

If only it was Rick, I have been having problems with ping/download speeds for weeks now (looking at the forums it seems to be quite widespread). I have rebooted several times but it only seems to be a temporary solution.

Ping to idnet 185ms ==> reboot ==> ping goes back down to "normal" levels ==> wait for 15 to 20 mins, ping goes back up

I normally get a good 7 meg d/l but when my ping increases my d/l goes to less than 1 meg (currently 0.77Mbs with a ping to 195ms to a manchester server...I live oop north). I joined IDNet as they advertise themselves as a gamers ISP, currently I would struggle to play pong. Reading the many threads on idnetters regarding this problem it seems as if IDNet has simply run out of capacity. I know they deny this but having run VisualRoute many times over a period of a week the problem seems to be with IDNets servers and not BT

Currently telehouse-gw2-lo2.idnet.net is showing an average reponse time of 162.1ms, and redbus-gw2-go-1-331.idnet.net is an average of 167 ms with a worst time of 241ms (these are all steps my packets take on the way to www.idnet.com)

As I am sure you would agree this is a totally unacceptable service from IDNet. I cannot play on my favourite game servers as I keep getting kicked for high ping. I think I will give them until the end of the month to offer a solution other than rebooting my router every 30 mins, failing that I (and I am sure many others) will simply find an ISP who can provide the service they promise. I am getting totally pissed of with this and IDNets lack of action to solve it. Sorry for the harsh language but my money is too hard earned to waste.

[Rik]

You don't appear to have re-booted from July 7, until now. Has this re-boot cured your problems?

[Fox]

its is slightly better (ping to idnet is now 101ms and telehouse-gw2-lo2.idnet.net is the problem)

[Rik]

How long was the router powered down?

[Baz]

is the re boot only needed if you have slow speeds Rik. If you dont re boot will it right itself.Just checked my router log and had a drop last night

stats look ok  

ADSL Link     Downstream     Upstream
Connection Speed    8128 kbps    448 kbps
Line Attenuation    36.0 db    18.0 db
Noise Margin    7.9 db    23.0 db


but my uptime has dropped but not LAN both were same times before the drop. is that right  

                Up Time
WAN    17:29:34
LAN        268:06:42
WLAN    116:41:09

[Fox]

30 seconds or so, I didn't bother to time it. My average ping currently to idnet after the reboot is 82ms with a max of 208ms.

[Rik]

See your PMs. You are on the unpopulated central right now.

[Fox]

Got the message rick ..... this is from VisualRoute

"This trace was started on 14-Jul-2009 17:40:05. The host 'www.idnet.com' has been found, and is reachable in 8 hops. The TTL value of packets received from it is 59. In general this route offers a good throughput, with hops responding on average within 137ms. However, hop 4 in network 'IDNET core network address allocation' is noticeably slower than others"

Hop 4 is telehouse-gw3-g0-400.idnet.net (212.69.63.243) average RTT 71.5ms max 233ms

[Rik]

From here:

tracert www.idnet.com

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

  1     1 ms    <1 ms     1 ms  home [192.168.1.254]
  2    26 ms    27 ms    25 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    26 ms    25 ms    25 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    25 ms    25 ms    25 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    25 ms    25 ms    27 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    25 ms    25 ms    26 ms  www.idnet.net [212.69.36.10]

Trace complete.

There doesn't appear to be an inherent problem. 

[Baz]

re boot has made it better for me



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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    46 ms    45 ms    66 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    46 ms    46 ms    45 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243

  4    46 ms    47 ms    46 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    46 ms    46 ms    48 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    45 ms    46 ms    46 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Rik]

You'll have been moved to the uncongested central, Baz, IDNet are stopping new logins on the congested pipe until the network is re-balanced.

[Baz]

will we stop on the uncongested one or get shifted back when its fixed.

[Rik]

You'll stay there until you re-boot after balancing has been completed, at which time the normal 'round robin' approach will be used.

[Fox]

Sorry for the big size but you need to be able to read the info. You can clearly see the poor response time from part of IDNets core network.

[Rik]

The point I'm making, though, is I'm not seeing it here - so the question is, what's causing it for you?

[Fox]

I dont know, I would guess that you are taking a different route through IDNets "plumbing".

[Rik]

It's identical, I think. Try re-booting to safe mode with network support and then run an extended ping, ie ping www.idnet.net -n 100. Your endpoint response is 39ms or so, which is reasonable, the servers give low priority to pings so will produce odd spikes when you run the kind of program you are doing.

[Gary]

The point I'm making, though, is I'm not seeing it here - so the question is, what's causing it for you?

Could it be you are on wbc Rik?

[Rik]

It wouldn't affect things at this point, Gary - plus I also checked on my Max connection.