Connection very slow at peak times!

JohnH · Jun 16, 2011, 21:40:45

It might be cheaper, but it's traffic managed, so good luck.

Steve · Jun 16, 2011, 21:43:55

If your slowness is due to Exchange Congestion unless you go LLU you'll take it with you until BT upgrade the VP's at your local exchange.

Fox · Jun 16, 2011, 21:55:03

I live in a small village and normally get 6-7 meg download, much like Horizon i havent noticed an extra 1000 houses springing up in the last week.

Simon · Jun 16, 2011, 22:05:34

Quote from: HoriZon on Jun 16, 2011, 21:20:35

Emailing them my self later tonight, this is my current BT speedtest done at 9pm.

=====================================================================
Time: 9:00pm - 16th June 2011
=====================================================================
Download speedachieved during the test was - 450 Kbps
For your connection, the acceptable range of speeds is 1200-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 832 Kbps(UP-STREAM)
IP Profile for your line is - 7150 Kbps
=====================================================================

By about 11pm it will be back to normal which was this ealier today:

=====================================================================
Time: 8:30am - 16th June 2011
=====================================================================
Download speedachieved during the test was - 6443 Kbps
For your connection, the acceptable range of speeds is 1200-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 832 Kbps(UP-STREAM)
IP Profile for your line is - 7150 Kbps
=====================================================================

Clearly tonight's speed is below the BT 'acceptable range', so I would have thought IDNet could get them to do something.

Steve · Jun 16, 2011, 22:08:03

If IDNet's network was congested I think we'd see the evidence on here as poor performance gets members posting. Although you say your rural exchange has no apparent increase in population what we don't know is whether there has been an increase in broadband users and/or change in their usage which has increased traffic through the exchange.

I suggest Fox that you send that BT speedtest result to support for further investigation.

Lance · Jun 16, 2011, 22:09:57

Or BT could have changed something at or beyond the exchange. Also to note is in sone cases small exchanges link into a bigger one somewhere near by so problems could occur there.

HoriZon · Jun 19, 2011, 17:26:41

No gaming for me tonight:

ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=397ms TTL=59
Reply from 212.69.36.10: bytes=32 time=376ms TTL=59
Reply from 212.69.36.10: bytes=32 time=434ms TTL=59
Reply from 212.69.36.10: bytes=32 time=499ms 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 = 376ms, Maximum = 499ms, Average = 426ms

ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=597ms TTL=59
Reply from 212.69.36.10: bytes=32 time=535ms TTL=59
Reply from 212.69.36.10: bytes=32 time=583ms TTL=59
Reply from 212.69.36.10: bytes=32 time=609ms 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 = 535ms, Maximum = 609ms, Average = 581ms

ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=572ms TTL=59
Reply from 212.69.36.10: bytes=32 time=589ms TTL=59
Reply from 212.69.36.10: bytes=32 time=571ms TTL=59
Reply from 212.69.36.10: bytes=32 time=471ms 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 = 471ms, Maximum = 589ms, Average = 550ms

ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=418ms TTL=59
Reply from 212.69.36.10: bytes=32 time=359ms TTL=59
Reply from 212.69.36.10: bytes=32 time=394ms TTL=59
Reply from 212.69.36.10: bytes=32 time=242ms 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 = 242ms, Maximum = 418ms, Average = 353ms

---------------------------

Shall see what IDNet say when they get back to me again tomorrow hopefully.

Rik · Jun 19, 2011, 17:34:56

What's throughput like? There's some evidence of congestion here, but it's minor:

ping www.idnet.com

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

Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms 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 = 16ms, Maximum = 21ms, Average = 18ms

normally, I'd see about 15ms average. Upload and download speeds, however, are normal.

HoriZon · Jun 19, 2011, 17:51:51

Download speedachieved during the test was - 777 Kbps
For your connection, the acceptable range of speeds is 1200-7150 Kbps.
Additional Information:
Your DSL Connection Rate :8128 Kbps(DOWN-STREAM), 832 Kbps(UP-STREAM)
IP Profile for your line is - 7150 Kbps

^^^ lol

Its only doing this when its busy, thing is a few weeks ago it was fine its the last week or so.

Cant game, cant watch iPlayer stuff and really cant use the net when i want to which is like everyone on a night!

Maybe i should quit working and use the net in the day its fine then.

Right now its like been on IDSN again but a little worse.

Lona · Jun 19, 2011, 18:21:10

I have to agree not knowing anything about pings etc. Connections at weekends is poor. I live with it and put it down to BT.

All isps suffer the same problem. End of story.

HoriZon · Jun 19, 2011, 18:23:46

Quote from: Lona on Jun 19, 2011, 18:21:10
I have to agree not knowing anything about pings etc. Connections at weekends is poor. I live with it and put it down to BT.

All isps suffer the same problem. End of story.

Shouldn't be this slow and even so its not just the weekend for me this is every night.

Rik · Jun 19, 2011, 18:24:05

Quote from: HoriZon on Jun 19, 2011, 17:51:51
Download speedachieved during the test was - 777 Kbps
For your connection, the acceptable range of speeds is 1200-7150 Kbps.

That test will help IDNet, send it on to them.

Rik · Jun 19, 2011, 18:24:28

Quote from: HoriZon on Jun 19, 2011, 18:23:46
Shouldn't be this slow and even so its not just the weekend for me this is every night.

Usually that points to exchange congestion.

HoriZon · Jun 19, 2011, 18:26:03

Quote from: Rik on Jun 19, 2011, 18:24:05
That test will help IDNet, send it on to them.

Have done with about another 5 from Thursday night last week, still waiting on an answer.

Quote from: Rik on Jun 19, 2011, 18:24:28
Usually that points to exchange congestion.

Yeah i understand all that but its getting worse and it was fine i used to game, stream vidoes at anytime with no issues till about a week or so ago.

Rik · Jun 19, 2011, 18:26:56

You won't get one till tomorrow.

HoriZon · Jun 19, 2011, 18:29:15

Quote from: Rik on Jun 19, 2011, 18:26:56
You won't get one till tomorrow.

Wasn't expecting one today

Rik · Jun 19, 2011, 18:31:26

HoriZon · Jun 19, 2011, 18:33:28

One thing i do know, is our new neighbours have broadband the last ones didnt would this effect me? as we are on the same poll ?

Using it at the same time etc, but then again wouldnt that effect it all the time not just on a night?

Simon · Jun 19, 2011, 18:35:59

Are they having the same problems as you?

Rik · Jun 19, 2011, 18:37:25

Potentially it might increase cross-talk and, therefore, the error count, but that would be it - unless they're on the same VP as you and downloading 24/7. It might be worth asking them if they've noticed any speed problems, and, if they will, get their d/s sync speed, attenuation and noise margin to compare with yours. One other possibility is that any wireless connections could be affected by their router.

HoriZon · Jun 19, 2011, 18:38:54

Quote from: Simon on Jun 19, 2011, 18:35:59
Are they having the same problems as you?

Dont know them well enough to ask and dont really see them.

As for Wireless im getting this wired as well.

Rik · Jun 19, 2011, 18:39:36

Another bright idea bites the dust.

HoriZon · Jun 19, 2011, 18:43:08

It has to be congestion at the exchange, thing is can IDNet do anything about that? a BT fix could be ages if ever.

Either that or i get a night job

Rik · Jun 19, 2011, 18:45:57

IDNet moan to BT, BT acknowledge and schedule an upgrade (this may have already happened), the upgrade can take from a few days to a few weeks.

HoriZon · Jun 19, 2011, 18:48:18

Quote from: Rik on Jun 19, 2011, 18:45:57
IDNet moan to BT, BT acknowledge and schedule an upgrade (this may have already happened), the upgrade can take from a few days to a few weeks.

Lets hope so and BT are on there way to fix it this week at least if that gets done and i still have issue, then i go kill the neighbour's!