Post Office ADSL Max problems

Hi
5 weeks ago I moved house and had a new line put in with the Post Office (and post office bb). My previous house was on the other side of town, but connected to the same exchange and ISP and I had no problems at all.

Since having this new line put in most of the time my speed will not exceed 0.6mpbs (according to the BT speedchecker) unless its between 4am-8am when it can see anything up to 2.5mb. I am synced at 8mb consitantly.

About 3 weeks ago I contacted PO and they sent a BT engineer out who said that there was nothing wrong with the line and that it was congestion with the ISP.

Now, I have done the BT speedchecker many times and often the speed is so low (400k) that it askes me to do a 3rd test and change my router login to the bt startupdomain one.

These tests also come back very slow.

It was my understanding that if these were slow to then the problem was with BTopenreach and the exchange rather than my ISP?

PO are sending another openreach engineer tomorrow - I'm expecting the same results as the first one.

Can anyone offer any advice as to what I should do?

Thanks

What happens when you tracert www.speedtester.bt.com

The Post Office service is a white label BT Wholesale affair so should stay in their network.
We presume the IP profile is set to 7150, i.e. what you would expect?

Congestion somewhere is the most likely issue. The same ISP can have multiple routes leaving an exchange (or virtual paths in Wholesale talk)

I don't have a solution but out of interest, what 'IP Profile' does the BT speed checker report you're on?

What does the BT speed tester say your IP profile is?

Is your computer connected wired or wirelessly to the router?

Hi
Same problem no matter wired or wireless. My IP profile was 7150k, but my ISP decided to turn interleaving on so my sync dropped to 8096k and my IP profile lowered to 7000k. I would have assumed that as the speed tester reported low speed when using the startup domain this would point finger at openreach/exchange issue?

This is the speedtest tracerout using my isp login details in my router:

Tracing route to www.speedtester.bt.com [217.32.105.42]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 60 ms 61 ms 60 ms 217.47.203.58
3 58 ms 60 ms 61 ms 217.47.203.161
4 56 ms 56 ms 53 ms 213.123.106.6
5 54 ms 52 ms 57 ms 213.123.106.50
6 60 ms 54 ms 55 ms core2-pos5-3.birmingham.ukcore.bt.net [195.99.12
0.77]
7 61 ms 67 ms 67 ms core2-pos0-1-4-0.ilford.ukcore.bt.net [62.6.204.
14]
8 63 ms 68 ms 67 ms core2-pos9-0.stalbans.ukcore.bt.net [194.74.16.2
22]
9 65 ms 61 ms 64 ms vhsaccess2-gig1-0.stalbans.fixed.bt.net [217.32.
169.148]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Interestingly when the speed is bad it always seems to be constant at 0.6mbps


Here is a snapshot of my speedtest results - the bt speedtester results are pretty much the same as these

Date Time Up Down
21st February 2010 15:53:46 356 Kbps 638 Kbps
21st February 2010 13:54:45 242 Kbps 1613 Kbps
20th February 2010 14:06:34 256 Kbps 2003 Kbps
20th February 2010 14:02:38 239 Kbps 2475 Kbps
20th February 2010 14:01:39 250 Kbps 2050 Kbps
20th February 2010 14:01:06 232 Kbps 2117 Kbps
18th February 2010 18:38:00 228 Kbps 750 Kbps
17th February 2010 21:27:34 231 Kbps 665 Kbps
17th February 2010 21:25:00 364 Kbps 542 Kbps
17th February 2010 10:40:36 257 Kbps 1874 Kbps
17th February 2010 09:34:34 249 Kbps 1472 Kbps
17th February 2010 09:17:22 235 Kbps 1421 Kbps
17th February 2010 09:03:37 239 Kbps 1717 Kbps
17th February 2010 08:54:44 251 Kbps 1494 Kbps
17th February 2010 08:49:28 232 Kbps 1294 Kbps
17th February 2010 08:48:35 257 Kbps 1584 Kbps
17th February 2010 08:21:58 249 Kbps 2947 Kbps
17th February 2010 01:38:50 244 Kbps 894 Kbps
17th February 2010 01:37:11 369 Kbps 610 Kbps
16th February 2010 21:32:34 228 Kbps 504 Kbps
16th February 2010 20:24:00 228 Kbps 415 Kbps
16th February 2010 20:05:12 226 Kbps 484 Kbps
16th February 2010 20:04:36 228 Kbps 485 Kbps
16th February 2010 19:39:17 363 Kbps 382 Kbps
16th February 2010 17:51:41 230 Kbps 639 Kbps
16th February 2010 17:42:42 226 Kbps 609 Kbps
16th February 2010 17:41:53 232 Kbps 1560 Kbps
16th February 2010 00:34:49 340 Kbps 684 Kbps
15th February 2010 19:24:10 228 Kbps 466 Kbps
15th February 2010 17:18:58 240 Kbps 874 Kbps
15th February 2010 13:12:26 240 Kbps 818 Kbps
15th February 2010 01:06:30 229 Kbps 649 Kbps
15th February 2010 01:05:49 228 Kbps 647 Kbps
15th February 2010 01:04:26 226 Kbps 562 Kbps
9th February 2010 02:44:12 253 Kbps 1450 Kbps

Also, not sure if this help but somthing doesnt look right here:

C:\Users\huw>ping -t jolt.co.uk

Pinging jolt.co.uk [84.234.17.86] with 32 bytes of data:
Reply from 84.234.17.86: bytes=32 time=65ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=57ms TTL=118
Reply from 84.234.17.86: bytes=32 time=510ms TTL=118
Reply from 84.234.17.86: bytes=32 time=146ms TTL=118
Reply from 84.234.17.86: bytes=32 time=74ms TTL=118
Reply from 84.234.17.86: bytes=32 time=53ms TTL=118
Reply from 84.234.17.86: bytes=32 time=116ms TTL=118
Reply from 84.234.17.86: bytes=32 time=345ms TTL=118
Reply from 84.234.17.86: bytes=32 time=72ms TTL=118
Reply from 84.234.17.86: bytes=32 time=60ms TTL=118
Reply from 84.234.17.86: bytes=32 time=62ms TTL=118
Reply from 84.234.17.86: bytes=32 time=60ms TTL=118
Reply from 84.234.17.86: bytes=32 time=56ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=62ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=57ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=54ms TTL=118
Reply from 84.234.17.86: bytes=32 time=83ms TTL=118
Reply from 84.234.17.86: bytes=32 time=141ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=115ms TTL=118
Reply from 84.234.17.86: bytes=32 time=61ms TTL=118
Reply from 84.234.17.86: bytes=32 time=68ms TTL=118
Reply from 84.234.17.86: bytes=32 time=67ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=60ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=62ms TTL=118
Reply from 84.234.17.86: bytes=32 time=61ms TTL=118
Reply from 84.234.17.86: bytes=32 time=56ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=57ms TTL=118
Reply from 84.234.17.86: bytes=32 time=67ms TTL=118
Reply from 84.234.17.86: bytes=32 time=69ms TTL=118
Reply from 84.234.17.86: bytes=32 time=66ms TTL=118
Reply from 84.234.17.86: bytes=32 time=63ms TTL=118
Reply from 84.234.17.86: bytes=32 time=66ms TTL=118
Reply from 84.234.17.86: bytes=32 time=61ms TTL=118
Reply from 84.234.17.86: bytes=32 time=62ms TTL=118
Reply from 84.234.17.86: bytes=32 time=276ms TTL=118
Reply from 84.234.17.86: bytes=32 time=61ms TTL=118
Reply from 84.234.17.86: bytes=32 time=64ms TTL=118
Reply from 84.234.17.86: bytes=32 time=64ms TTL=118
Reply from 84.234.17.86: bytes=32 time=61ms TTL=118
Reply from 84.234.17.86: bytes=32 time=59ms TTL=118
Reply from 84.234.17.86: bytes=32 time=67ms TTL=118
Reply from 84.234.17.86: bytes=32 time=60ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=62ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=64ms TTL=118
Reply from 84.234.17.86: bytes=32 time=57ms TTL=118
Reply from 84.234.17.86: bytes=32 time=62ms TTL=118
Reply from 84.234.17.86: bytes=32 time=57ms TTL=118
Reply from 84.234.17.86: bytes=32 time=58ms TTL=118
Reply from 84.234.17.86: bytes=32 time=61ms TTL=118

Ping statistics for 84.234.17.86:
Packets: Sent = 61, Received = 61, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:

Edited by deleted (Sun 21-Feb-10 21:26:50)

In reply to a post by huwwatkins:

I would have assumed that as the speed tester reported low speed when using the startup domain this would point finger at openreach/exchange issue?

Yes, sounds like a capacity issue at the exchange. startup_domain won't go via your ISPs allocated capacity, so that can be ruled out.

Matt

In reply to a post by uno:

In reply to a post by huwwatkins:

I would have assumed that as the speed tester reported low speed when using the startup domain this would point finger at openreach/exchange issue?

Yes, sounds like a capacity issue at the exchange. startup_domain won't go via your ISPs allocated capacity, so that can be ruled out.

Matt

So this is an issue for the bt openreach engineer to sort out then?

Should not normally even go that far. Issues such as the one you are seeing are often identified and fixed within BT Wholesale.

Matt

Which exchange is it?

In reply to a post by RobertoS:

Which exchange is it?

Aberystwyth (WNAE)

I specifically asked if the exchange was congested. He said it used to be but wasn't anymore.