Speed issues

Started by David, Jul 08, 2009, 11:25:48

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Rik

I wish I could answer that, Steve.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

David

Well I dont know if Im relieved its sticking to form or not



But it is

502.34 Kbps ( 0.5 Mbps )
Speed Up    378.48 Kbps ( 0.4 Mbps )
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

Steve

David. Can you post your adsl router connection stats sorry I don't know which router your using at present.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

David

    6592 kbs         448 kbs
Max Rate:       6660 kbs       980 kbs
Current Connection:
   Current Noise Margin:       6.0 dB       22.0 dB
   Current Attenuation:       43.3 dB       23.5 dB
   Current Output Power:       19.5 dBm       12.1 dBm

This what you want Steve?

2 wire router Steve
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

Steve

They look fine. What does Home > Broadband Link > Details show under the protocol heading I am  assuming your v5 firmware.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Wooloff

Can someone post the email address for support please.

The one address I can find on the site is contactus@idnet.com, is that the correct address?

bobleslie

=Bob=.
Sky/Easylink LLU. Thankfully! ;-)

wecpcs

Quote from: zappaDPJ on Jul 08, 2009, 17:59:16
I'm would be very interested to hear from anyone who has reverting back to ADSL Max what latency (ping) you are getting to idnet.com.

Monitoring the forums it appears that those of you that have switched back are all experiencing low throughput and high latency, is this still the case?

Well I have not moved as it is not available for the foreseeable future, but I am getting much lower throughput also, about 2-4Mb when it is usually 5-6.5Mb and the latency has increased from around 40 to over 160 during the evenings on a quiet uncongested exchange. It has been like this now for several weeks, even before the tennis and is continuing.

System Up Time 00:37:35
Port    Status    TxPkts    RxPkts    Collisions    Tx B/s    Rx B/s    Up Time
WAN    PPPoA    16387    27441    0    1502    21673    00:27:14
LAN    10M/100M    30052    26421    0    16640    2552    00:37:27
WLAN    11M/54M    0    0    0    0    0    00:37:18

ADSL Link    Downstream    Upstream
Connection Speed    8128 kbps    448 kbps
Line Attenuation    27.0 db    12.5 db
Noise Margin    9.8 db    24.0 db

This was my lowest recorded on Idnet 05/07/09: 



This is one from today around 5pm on 08/07/09: 



This is one from today around 7pm on 08/07/09: 


We have been experiencing a couple of power cuts locally every other day for about a week, lasting only a minute or so. We have even seen their helicopter flying overhead trying to find the fault and very early on the Saturday morning (around 4am) we had a longer one lasting over an hour, but it seems to be all OK now. But how do you explain this log I recorded for that Saturday. (the date is incorrect due to the previous power cut).

There appears to be router reboot approximately every hour lasting about 20 hours and it was not due to power loss. Maybe it was exchange related on the ADSL line.

Sat, 2000-01-01 00:00:39 - Initialize LCP.
Sat, 2000-01-01 00:00:39 - LCP is allowed to come up.
Sat, 2000-01-01 00:00:51 - CHAP authentication failed
Sat, 2000-01-01 00:00:51 - LCP down.
Sat, 2000-01-01 00:01:38 - Initialize LCP.
Sat, 2000-01-01 00:01:38 - LCP is allowed to come up.
Sat, 2000-01-01 00:01:49 - CHAP authentication failed
Sat, 2000-01-01 00:01:49 - LCP down.
Sat, 2000-01-01 00:02:38 - Initialize LCP.
Sat, 2000-01-01 00:02:38 - LCP is allowed to come up.
Sat, 2000-01-01 00:02:48 - CHAP authentication failed
Sat, 2000-01-01 00:02:48 - LCP down.
Sat, 2000-01-01 00:03:38 - Initialize LCP.
Sat, 2000-01-01 00:03:38 - LCP is allowed to come up.
Sat, 2000-01-01 00:03:50 - CHAP authentication failed
Sat, 2000-01-01 00:03:50 - LCP down.
Sat, 2000-01-01 00:04:38 - Initialize LCP.
Sat, 2000-01-01 00:04:39 - LCP is allowed to come up.
Sat, 2000-01-01 00:04:47 - CHAP authentication failed
Sat, 2000-01-01 00:04:47 - LCP down.
Sat, 2000-01-01 00:05:39 - Initialize LCP.
Sat, 2000-01-01 00:05:39 - LCP is allowed to come up.
Sat, 2000-01-01 00:05:49 - CHAP authentication failed
Sat, 2000-01-01 00:05:49 - LCP down.
Sat, 2000-01-01 00:06:39 - Initialize LCP.
Sat, 2000-01-01 00:06:39 - LCP is allowed to come up.
Sat, 2000-01-01 00:06:51 - CHAP authentication failed
Sat, 2000-01-01 00:06:51 - LCP down.
Sat, 2000-01-01 00:07:39 - Initialize LCP.
Sat, 2000-01-01 00:07:39 - LCP is allowed to come up.
Sat, 2000-01-01 00:07:49 - CHAP authentication failed
Sat, 2000-01-01 00:07:49 - LCP down.
Sat, 2000-01-01 00:08:39 - Initialize LCP.
Sat, 2000-01-01 00:08:39 - LCP is allowed to come up.
Sat, 2000-01-01 00:08:48 - CHAP authentication failed
Sat, 2000-01-01 00:08:48 - LCP down.
Sat, 2000-01-01 00:09:39 - Initialize LCP.
Sat, 2000-01-01 00:09:39 - LCP is allowed to come up.
Sat, 2000-01-01 00:09:50 - CHAP authentication failed
Sat, 2000-01-01 00:09:50 - LCP down.
Fri, 1999-12-31 24:59:59 - Router start up
Sat, 2000-01-01 00:10:39 - Initialize LCP.
Sat, 2000-01-01 00:10:39 - LCP is allowed to come up.
Sat, 2000-01-01 00:10:50 - CHAP authentication failed
Sat, 2000-01-01 00:10:51 - LCP down.
Sat, 2000-01-01 00:11:39 - Initialize LCP.
Sat, 2000-01-01 00:11:39 - LCP is allowed to come up.
Sat, 2000-01-01 00:11:51 - CHAP authentication failed
Sat, 2000-01-01 00:11:51 - LCP down.
Sat, 2000-01-01 00:12:40 - Initialize LCP.
Sat, 2000-01-01 00:12:40 - LCP is allowed to come up.
Sat, 2000-01-01 00:12:49 - CHAP authentication failed
Sat, 2000-01-01 00:12:49 - LCP down.
Sat, 2000-01-01 00:13:40 - Initialize LCP.
Sat, 2000-01-01 00:13:40 - LCP is allowed to come up.
Sat, 2000-01-01 00:14:01 - CHAP authentication failed
Sat, 2000-01-01 00:14:01 - LCP down.
Sat, 2000-01-01 00:14:40 - Initialize LCP.
Sat, 2000-01-01 00:14:40 - LCP is allowed to come up.
Sat, 2000-01-01 00:14:49 - CHAP authentication failed
Sat, 2000-01-01 00:14:49 - LCP down.
Sat, 2000-01-01 00:15:40 - Initialize LCP.
Sat, 2000-01-01 00:15:40 - LCP is allowed to come up.
Sat, 2000-01-01 00:15:49 - CHAP authentication failed
Sat, 2000-01-01 00:15:49 - LCP down.
Sat, 2000-01-01 00:16:40 - Initialize LCP.
Sat, 2000-01-01 00:16:40 - LCP is allowed to come up.
Sat, 2000-01-01 00:16:51 - CHAP authentication failed
Sat, 2000-01-01 00:16:51 - LCP down.
Sat, 2000-01-01 00:17:40 - Initialize LCP.
Sat, 2000-01-01 00:17:40 - LCP is allowed to come up.
Sat, 2000-01-01 00:17:50 - CHAP authentication failed
Sat, 2000-01-01 00:17:50 - LCP down.
Sat, 2000-01-01 00:18:40 - Initialize LCP.
Sat, 2000-01-01 00:18:40 - LCP is allowed to come up.
Sat, 2000-01-01 00:18:48 - CHAP authentication success
Sat, 2000-01-01 00:18:51 - Send out NTP request to time-g.netgear.com
Sat, 2000-01-01 00:20:13 - Send out NTP request to time-h.netgear.com
Sun, 2009-07-05 05:37:06 - Receive NTP Reply from time-h.netgear.com

Sorry for the long post

Colin

David

Just posting here for support to view tomorrow.  

Test1 comprises of Best Effort Test:  -provides background information.
   Your DSL connection rate: 6592 kbps(DOWN-STREAM),  448 kbps(UP-STREAM)
   IP profile for your line is - 5000 kbps
   Actual IP throughput achieved during the test was - 428 kbps
test carried out 22.22
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

rireed3

Just because I didn't see it mentioned, have a look at this report that plusnet tracks:

exchange capacity status

It doesn't mean a lot, just that if 'red' the exchange has yet to implement required spare Virtual Path capacity.  Many associate the 'red' with 'likely exchange congestion', but I find my experience of the difference between red and green statuses unreliable.

Richard

David

Test1 comprises of Best Effort Test:  -provides background information.
    Your DSL connection rate: 6592 kbps(DOWN-STREAM),  448 kbps(UP-STREAM)
    IP profile for your line is - 5000 kbps
    Actual IP throughput achieved during the test was - 3369 kbps

Posted here for James to monitor throught the day
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

Rik

Getting better, David...
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

David

Its hard to say as the first test near enough every morning for the past few weeks or more have been the same and from say midday or whatever it usually deterioarates ,so too early at the moment Rik
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

Rik

That sounds like exchange congestion, David.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

David

Yes its very odd it only started when I changed over.James mentioned "rebalancing" what ever this is but hopefully it will get resolved once and for all !
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

Rik

Re-balancing would be at IDNet's end. If it's the exchange, they'd need to try and get you moved to a different VP.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

David

I'm confident that a solution will be found its just one of those things at least there is a pattern which may at least help identify the source of it.I thought congestion but as sometimes it is gone 23.00 I would have thought that it would have been the reverse at this time .I don't know though.
Support are doing their best and with luck I can get on with something else other than get fixated about my speeds .It cannot be easy I would have thought to pinpoint this type of issue but I'm sure they will .
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

Rik

They will, David, it just takes a while.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

David

#43
 :fingers

9/07/09 11:41:05
Speed Down    1237.53 Kbps ( 1.2 Mbps )
Speed Up    376.79 Kbps ( 0.4 Mbps
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

David

09/07/09 13:52:44
Speed Down    800.67 Kbps ( 0.8 Mbps )
Speed Up    376.55 Kbps ( 0.4 Mbps )
Port    8095
Server    speedtest1.thinkbroadband.com
IP Address    212.69.45.185
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

Rik

It does look like either exchange congestion or a balancing issue. :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

David

Yes slowing by the hour  :(
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

David

Test1 comprises of Best Effort Test:  -provides background information.
    Your DSL connection rate: 6592 kbps(DOWN-STREAM),  448 kbps(UP-STREAM)
    IP profile for your line is - 5000 kbps
    Actual IP throughput achieved during the test was - 894 kbps

If you wish to discuss these results please contact your ISP.


Last one until this evening hope there is enough here to indicate what the problem is
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

Wooloff

This is what I got back from my email regarding my poor speeds,

Occasionally one of our connections into BT can attract more traffic
than the others and become congested. We have enough aggregated to
bandwidth to cope with normal loads and are constantly trying to keep
the traffic level balanced between our BT pipes. A simple router reboot
can force a reconnection to a different pipe.

I've done the resetting the router thing plenty of time and yes the speeds are slightly better for a short time but it soon reverts back again.

Where should I go from here guys?

Rik

Back to support and tell them it isn't resolving the problem for you except for a short while.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.