cancel
Showing results for 
Search instead for 
Did you mean: 
Distinguished Sage
267 Views
Message 21 of 58

Re: Slow peak speeds :(

a trace route showing as things are now and when the problem appears would be of help
0 Ratings
pmk24
Contributor
258 Views
Message 22 of 58

Re: Slow peak speeds :(

ok 2x tracerts when the internet speed is ok

 

C:\Users\pmk>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.244.69] over a maximum of 30 hops:

1     11 ms     1 ms     2 ms  BThomehub.home [192.168.1.254]  

2     7 ms     7 ms     6 ms  172.16.13.131  

3     *        6 ms     6 ms  217.41.217.110  

4    20 ms     7 ms   121 ms  217.41.217.109  

5     8 ms     8 ms     8 ms  212.140.235.130  

6     8 ms     8 ms     9 ms  217.41.169.33  

7     8 ms     8 ms     8 ms  217.41.169.107  

8     8 ms     7 ms     7 ms  109.159.251.83  

9    18 ms    16 ms    22 ms  core2-te0-13-0-2.ilford.ukcore.bt.net [109.159.2 51.11]  

10    14 ms    13 ms    14 ms  peer2-xe2-1-0.telehouse.ukcore.bt.net [109.159.2 54.142]  

11    14 ms    14 ms    14 ms  194.74.65.42  

12     *        *        *     Request timed out.  

13     *        *        *     Request timed out.

14    18 ms    16 ms    18 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]  

15    14 ms    17 ms    15 ms  132.185.255.149  

16    15 ms    14 ms    14 ms  bbc-vip114.telhc.bbc.co.uk [212.58.244.69]

Trace complete.

 

C:\Users\pmk>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.244.69] over a maximum of 30 hops:

1     2 ms     2 ms     2 ms  BThomehub.home [192.168.1.254]  

2     7 ms     6 ms     6 ms  172.16.13.131  

3     7 ms     7 ms     6 ms  217.41.217.110  

4     6 ms     26 ms     76 ms  217.41.217.109  

5     8 ms     8 ms     8 ms  212.140.235.130  

6     8 ms     8 ms     8 ms  217.41.169.33  

7     8 ms     8 ms     8 ms  217.41.169.107  

8    10 ms     8 ms     7 ms  109.159.251.75  

9    20 ms    23 ms    15 ms  core2-te0-13-0-2.ilford.ukcore.bt.net [109.159.2 51.11]  

10    13 ms    14 ms    16 ms  peer1-xe3-2-0.telehouse.ukcore.bt.net [109.159.2 54.221]  

11    14 ms    14 ms    15 ms  194.74.65.42  

12     *        *        *     Request timed out.  

13     *        *        *     Request timed out.  

14    15 ms    18 ms    28 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]  

15    16 ms    18 ms    14 ms  132.185.255.149  

16    14 ms    15 ms    14 ms  bbc-vip114.telhc.bbc.co.uk [212.58.244.69]

Trace complete.

0 Ratings
pmk24
Contributor
250 Views
Message 23 of 58

Re: Slow peak speeds :(

now this is when my net is fine, but looking at the tracert hop4 seems to spike somtimes, so i did 2x pings to it

 

C:\Users\pmk>ping 217.41.217.109 -t

Pinging 217.41.217.109 with 32 bytes of data:

Reply from 217.41.217.109: bytes=32 time=10ms TTL=252

Reply from 217.41.217.109: bytes=32 time=10ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=135ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=8ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Ping statistics for 217.41.217.109:     Packets: Sent = 37, Received = 37, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 6ms, Maximum = 135ms, Average = 9ms

Control-C ^C

 

C:\Users\pmk>ping 217.41.217.109 -t

Pinging 217.41.217.109 with 32 bytes of data:

Reply from 217.41.217.109: bytes=32 time=10ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=8ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=92ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=8ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=11ms TTL=252

Reply from 217.41.217.109: bytes=32 time=116ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=23ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=29ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

 

Ping statistics for 217.41.217.109:     Packets: Sent = 57, Received = 57, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:     Minimum = 6ms, Maximum = 116ms, Average = 10ms

Control-C ^C

C:\Users\pmk>

0 Ratings
Distinguished Sage
248 Views
Message 24 of 58

Re: Slow peak speeds :(

ok thanks please try the same when the connection slows down
0 Ratings
pmk24
Contributor
239 Views
Message 25 of 58

Re: Slow peak speeds :(

C:\Users\pmk>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.244.69] over a maximum of 30 hops:

  1     2 ms     2 ms     3 ms  BThomehub.home [192.168.1.254]  

2     6 ms     6 ms     7 ms  172.16.13.131  

3     6 ms     6 ms     6 ms  217.41.217.110  

4     7 ms     6 ms     7 ms  217.41.217.109  

5     8 ms     8 ms     8 ms  212.140.235.130  

6     7 ms     7 ms     8 ms  217.41.169.33  

7     9 ms     9 ms     8 ms  217.41.169.107  

8    10 ms     8 ms     8 ms  109.159.251.83  

9   368 ms   287 ms   167 ms  core2-te0-13-0-2.ilford.ukcore.bt.net [109.159.2 51.11]  

10   265 ms   273 ms   275 ms  peer1-xe3-2-0.telehouse.ukcore.bt.net [109.159.2 54.221]  

11   231 ms   143 ms   155 ms  194.74.65.42  

12     *        *        *     Request timed out.  

13     *        *        *     Request timed out.  

14    18 ms    19 ms    18 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]  

15    18 ms    17 ms    15 ms  132.185.255.149  

16    14 ms    13 ms    14 ms  bbc-vip114.telhc.bbc.co.uk [212.58.244.69]

Trace complete.

 

C:\Users\pmk>ping 217.41.217.109 -t

Pinging 217.41.217.109 with 32 bytes of data:

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=8ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=121ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Request timed out.

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=11ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=7ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=102ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Reply from 217.41.217.109: bytes=32 time=6ms TTL=252

Ping statistics for 217.41.217.109:     Packets: Sent = 46, Received = 45, Lost = 1 (2% loss), Approximate round trip times in milli-seconds:     Minimum = 6ms, Maximum = 121ms, Average = 10ms

Control-C ^C

C:\Users\pmk>

 

newbt.png

newbt2.png

and as by magic 5 minutes later its back at

 

Just to make things clear, I am the only thing connected to the home hub, nothing is downloading or causing traffic on my PC or it would be reported via netlimiter

liimiter.png

All i want is a good and stable connection so I am able to use the internet

 

Regards

Paul

0 Ratings
Distinguished Sage
233 Views
Message 26 of 58

Re: Slow peak speeds :(

it does look like some peak time network congestion but as your speeds are currently in spec there is little that can be done
0 Ratings
pmk24
Contributor
226 Views
Message 27 of 58

Re: Slow peak speeds :(

so in peak hours (basicly the time I am at home) I am unable to use my internet connection and this is ok?

 

I honestly am really puzzled how BT expect anyone to be happy with this level of service of connection, I understand that this is a community forum but even if the BTW page said my connection is 2mb or 20mb all the time it still does not help resolve that when i use the internet the connection is terrible and not function correctly.

0 Ratings
Distinguished Sage
223 Views
Message 28 of 58

Re: Slow peak speeds :(

there is nothing BT retail your provider can do as the network is provided by BT Wholesale to the majority of ISPs and unless speed drop below their minimum fault level which in your case is 4mb they will not act on it
0 Ratings
pmk24
Contributor
218 Views
Message 29 of 58

Re: Slow peak speeds :(

John,

I think either I have not explained my issue correctly or you think I am complaining about this magic number that is displayed on a webpage that does not help my issue at all.

At peak hours, I am unable to use the internet for anything other then browsing and email. It does not matter that I connect to the internet at a value and as by magic if this value is green then my connection must be fine .... It isn't fine.

I am seeking help or advice in getting a service that I pay for to an acceptable level. If I was sold with the knowledge that I would get in reality a very weak line I would not be complaining as much, however something is wrong somewhere and it needs to be fixed.
0 Ratings
Distinguished Sage
Distinguished Sage
216 Views
Message 30 of 58

Re: Slow peak speeds :(

your problem certainly looks like exchnage congestion at peak time just as thought earlier but from your btspeedtester results your download speed is always above the acceptable limit/threshold shown and from previous experience wholesale do not normally help in these cases.

 

john46 and I are not saying we agree with that just that is the way wholesale have been in similar situations to yours in the past



If you like a post, or want to say thanks for a helpful answer, please click on the Ratings 'Thumbs up' on left hand side.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.
0 Ratings