Download speed up during 'open questions', down again when closed

[#1]

Hi mickthefitter,
Let us know when you've fitted the new block, we'll have a look at what's happening.

[#2]

Okay, thanks.

[#3]

Quote from: Anotherone

It would be helpful if Chris could just post the current WBC profile so we are sure it is what we'd expect to see.

[#4]

Sorry, missed that bit! 2 mins.

[#5]

WBC 160K - 24M Medium delay (INP 1) 6dB Downstream, UC Medium delay (INP 2) 6dB Upstream (ADSL2+)

[#6]

Thanks Chris, a great help.

[#7]

Good morning.
Yesterday (Saturday) I fitted my new surge protection block behind my stereo system and in doing so, shut down my router for about ten minutes. On re-booting it, I went straight to the BT Wholesale speed checker and got these results -
1. Best Effort Test:  -provides background information.
Download  Speed
6.59 Mbps
 
0 Mbps 7.15 Mbps
Max Achievable Speed
Download speedachieved during the test was - 6.59 Mbps
For your connection, the acceptable range of speeds is 2 Mbps-7.15 Mbps.
IP Profile for your line is - 7.75 Mbps
2. Upstream Test:  -provides background information.
Upload Speed
0.56 Mbps
 
0 Mbps 0.83 Mbps
Max Achievable Speed
Upload speed achieved during the test was - 0.56Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.83 Mbps

I've just re-run the same test (Sunday morning) and got these results -
1. Best Effort Test:  -provides background information.
Download  Speed
6.5 Mbps
 
0 Mbps 7.15 Mbps
Max Achievable Speed
Download speedachieved during the test was - 6.5 Mbps
For your connection, the acceptable range of speeds is 2 Mbps-7.15 Mbps.
IP Profile for your line is - 7.61 Mbps
2. Upstream Test:  -provides background information.
Upload Speed
0.48 Mbps
 
0 Mbps 0.83 Mbps
Max Achievable Speed
Upload speed achieved during the test was - 0.48Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.83 Mbps

This was done wirelessly, but with me standing in front of the router, just a couple of feet away, to save me putting the ethernet lead in the back of my router, which is a bit tight to the wall and held there by concealed cables!
The latest round of other stats follow -
DSL Connection
Link Information
Uptime: 0 days, 6:21:20
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 756 / 8.629
Data Transferred (Sent/Received) [MB/MB]: 36,10 / 344,91
Output Power (Up/Down) [dBm]: 12,0 / 20,5
Line Attenuation (Up/Down) [dB]: 24,2 / 45,0
SN Margin (Up/Down) [dB]: 5,6 / 6,3
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / TSTC
Loss of Framing (Local/Remote): 17 / 0
Loss of Signal (Local/Remote): 2 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 98 / 0
FEC Errors (Up/Down): 5.923 / 4.428
CRC Errors (Up/Down): 0 / 22
HEC Errors (Up/Down): 0 / 68

And here is my router log...
Recorded Events
Time Message
Info Jul 26 09:20:17 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)
Info Jul 26 09:03:26 SNTP Synchronised to server: 212.159.6.10
Error Jul 26 08:23:13 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 122.202.178.232 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 08:03:26 SNTP Synchronised again to server: 212.159.6.9
Info Jul 26 07:56:56 CONFIGURATION mbus igd sync successfull
Info Jul 26 07:56:52 CONFIGURATION mbus atomic sync successful
Error Jul 26 07:45:42 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 220.184.125.64 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 07:03:25 SNTP Synchronised to server: 212.159.6.9
Info Jul 26 06:03:25 SNTP Synchronised again to server: 212.159.6.10
Error Jul 26 05:57:42 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 191.138.108.201 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:56:38 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 69.69.152.231 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:53:04 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 120.42.81.80 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:50:45 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 179.171.169.25 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:39:42 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 125.73.180.178 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:32:27 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 222.142.97.178 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:18:58 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 60.252.253.215 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:12:20 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 69.69.155.192 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 05:03:25 SNTP Synchronised again to server: 212.159.6.10
Error Jul 26 04:59:26 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 176.97.89.30 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 04:03:25 SNTP Synchronised to server: 212.159.6.10
Error Jul 26 04:00:31 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 152.63.116.165 Dst ip: XXXXX Type: Time Exceeded Code: Time to Live exceeded in Transit
Error Jul 26 03:31:39 FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 171.8.235.243 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 03:25:30 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 213.108.208.29 Dst ip: XXXXX Type: Destination Unreachable Code: Net Unreacheable
Info Jul 26 03:03:25 SNTP Synchronised to server: 212.159.6.9
Info Jul 26 03:00:16 CONFIGURATION saved by TR69
Warning Jul 26 02:59:58 PPP link up (Internet) [XXXXX]
Info Jul 26 02:59:57 PPP CHAP Receive success (Internet)
Info Jul 26 02:59:57 PPP CHAP Receive challenge from rhost PTN-AG01 (Internet)
Info Jul 26 09:20:17 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)
Info Jul 26 09:03:26 SNTP Synchronised to server: 212.159.6.10
Error Jul 26 08:23:13 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 122.202.178.232 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 08:03:26 SNTP Synchronised again to server: 212.159.6.9
Info Jul 26 07:56:56 CONFIGURATION mbus igd sync successfull
Info Jul 26 07:56:52 CONFIGURATION mbus atomic sync successful
Error Jul 26 07:45:42 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 220.184.125.64 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 07:03:25 SNTP Synchronised to server: 212.159.6.9
Info Jul 26 06:03:25 SNTP Synchronised again to server: 212.159.6.10
Error Jul 26 05:57:42 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 191.138.108.201 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:56:38 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 69.69.152.231 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:53:04 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 120.42.81.80 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:50:45 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 179.171.169.25 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:39:42 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 125.73.180.178 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:32:27 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 222.142.97.178 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:18:58 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 60.252.253.215 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:12:20 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 69.69.155.192 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 05:03:25 SNTP Synchronised again to server: 212.159.6.10
Error Jul 26 04:59:26 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 176.97.89.30 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 04:03:25 SNTP Synchronised to server: 212.159.6.10
Error Jul 26 04:00:31 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 152.63.116.165 Dst ip: XXXXX Type: Time Exceeded Code: Time to Live exceeded in Transit
Error Jul 26 03:31:39 FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 171.8.235.243 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 03:25:30 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 213.108.208.29 Dst ip: XXXXX Type: Destination Unreachable Code: Net Unreacheable
Info Jul 26 03:03:25 SNTP Synchronised to server: 212.159.6.9
Info Jul 26 03:00:16 CONFIGURATION saved by TR69
Warning Jul 26 02:59:58 PPP link up (Internet) [XXXXX]
Info Jul 26 02:59:57 PPP CHAP Receive success (Internet)
Info Jul 26 02:59:57 PPP CHAP Receive challenge from rhost PTN-AG01 (Internet)
Info Jul 26 09:20:17 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)
Info Jul 26 09:03:26 SNTP Synchronised to server: 212.159.6.10
Error Jul 26 08:23:13 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 122.202.178.232 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 08:03:26 SNTP Synchronised again to server: 212.159.6.9
Info Jul 26 07:56:56 CONFIGURATION mbus igd sync successfull
Info Jul 26 07:56:52 CONFIGURATION mbus atomic sync successful
Error Jul 26 07:45:42 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 220.184.125.64 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 07:03:25 SNTP Synchronised to server: 212.159.6.9
Info Jul 26 06:03:25 SNTP Synchronised again to server: 212.159.6.10
Error Jul 26 05:57:42 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 191.138.108.201 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:56:38 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 69.69.152.231 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:53:04 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 120.42.81.80 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:50:45 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 179.171.169.25 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:39:42 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 125.73.180.178 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:32:27 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 222.142.97.178 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:18:58 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 60.252.253.215 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:12:20 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 69.69.155.192 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 05:03:25 SNTP Synchronised again to server: 212.159.6.10
Error Jul 26 04:59:26 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 176.97.89.30 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 04:03:25 SNTP Synchronised to server: 212.159.6.10
Error Jul 26 04:00:31 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 152.63.116.165 Dst ip: XXXXX Type: Time Exceeded Code: Time to Live exceeded in Transit
Error Jul 26 03:31:39 FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 171.8.235.243 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 03:25:30 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 213.108.208.29 Dst ip: XXXXX Type: Destination Unreachable Code: Net Unreacheable
Info Jul 26 03:03:25 SNTP Synchronised to server: 212.159.6.9
Info Jul 26 03:00:16 CONFIGURATION saved by TR69
Warning Jul 26 02:59:58 PPP link up (Internet) [XXXXX]
Info Jul 26 02:59:57 PPP CHAP Receive success (Internet)
Info Jul 26 02:59:57 PPP CHAP Receive challenge from rhost PTN-AG01 (Internet)
Info Jul 26 09:20:17 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)
Info Jul 26 09:03:26 SNTP Synchronised to server: 212.159.6.10
Error Jul 26 08:23:13 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 122.202.178.232 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Info Jul 26 08:03:26 SNTP Synchronised again to server: 212.159.6.9
Info Jul 26 07:56:56 CONFIGURATION mbus igd sync successfull
Info Jul 26 07:56:52 CONFIGURATION mbus atomic sync successful
Error Jul 26 07:45:42 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 220.184.125.64 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable

Info Jul 26 07:03:25 SNTP Synchronised to server: 212.159.6.9
Info Jul 26 06:03:25 SNTP Synchronised again to server: 212.159.6.10
Error Jul 26 05:57:42 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 191.138.108.201 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:56:38 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 69.69.152.231 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:53:04 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 120.42.81.80 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:50:45 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 179.171.169.25 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:39:42 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 125.73.180.178 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:32:27 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 222.142.97.178 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Error Jul 26 05:18:58 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 60.252.253.215 Dst ip: XXXXX Type: Destination Unreachable Code: Port Unreacheable
Boy, obliterating my Dst ip from that list took some doing...it was only on there about a zillion times. I visited the optician yesterday - I think I need to go again now. 
So, from my observations it would appear that I had another drop-out before I got out of bed this morning, although my upload speed issues seem resolved. The Ookla speed checker actually gave me 0.62Mb/s this morning, and that one is usually a bit slow on the up speed, good on the download speed. The work by Western Power contractors on the main road nearby is scheduled to be finished by tomorrow morning I think - the temporary traffic lights are still there at present, but the barriers that they had around holes in the grass verge on the entry road into my estate are now lying flat, so I think they've filled those holes in. What they've been doing and whether its had any effect on my internet experiences is open to speculation - when I peered into one of their holes, I could see some sort of grey plastic pipe, with a rectangular hatch in it. I've no idea if that is gas or electric. Do gas pipes have to be yellow?
Cheers,
Mick.

[#8]

You are correct Mick, Gas would be yellow
Well I guess we might all need to go to the optician after reading that log, I squinted several times, you obviously had fun editing it as you've manage to post the same section 3 times    don't even worry about it. The stats are probably the most important thing at this point, they look near normal and the errors are nice and low, which considering the last resync (you've had 2 - LOS) was somewhere around 0330 if post time and uptime are anything to go by, is hopefully indicative of things being OK.
The GUI log doesn't shown the xDSL down and ups because of it's limited capacity and no doubt being filled with that spurt of ICMP checks 0500-0600ish! The Telnet log would show more, but not worth the effort of looking at this point, whilst Western Power and possibly Openreach are still poking about.
Once the holes are filled in and the work has ceased, watching what happens over the next couple of days will be the key. Speed tests as you know can vary, it's stats consistency we hope to see. If you can post some more stats later, and perhaps some tomorrow morning and evening, that may give a feel for how it's going. If you have any more sync loss, then the log could useful as well.

[#9]

I see what you mean about the event log being repetitive. I honestly didn't notice, I just copied and pasted. There was a heck of a lot of entries in the log this morning. I guess it is possible that my right-clicking of the mouse somehow duplicated what I was copying - I've known my laptop to spontaneously duplicate JPEG images when I've been trying to move them - so maybe that is what happened, but there were masses of errors recorded in the log so I thought that is all I was copying. Never mind.
Here are a few Sunday night stats then - BT Wholesale.
1. Best Effort Test:  -provides background information.
Download  Speed
6.57 Mbps

0 Mbps 7.15 Mbps
Max Achievable Speed
Download speedachieved during the test was - 6.57 Mbps
For your connection, the acceptable range of speeds is 2 Mbps-7.15 Mbps.
IP Profile for your line is - 7.61 Mbps
2. Upstream Test:  -provides background information.
Upload Speed
0.46 Mbps

0 Mbps 0.83 Mbps
Max Achievable Speed

DSL stats -
Link Information
Uptime: 0 days, 16:58:29
DSL Type: ITU-T G.992.5
Bandwidth (Up/Down) [kbps/kbps]: 756 / 8.629
Data Transferred (Sent/Received) [MB/MB]: 75,05 / 744,27
Output Power (Up/Down) [dBm]: 12,0 / 20,5
Line Attenuation (Up/Down) [dB]: 24,2 / 45,0
SN Margin (Up/Down) [dB]: 5,8 / 6,3
System Vendor ID (Local/Remote): TMMB / ----
Chipset Vendor ID (Local/Remote): BDCM / TSTC
Loss of Framing (Local/Remote): 17 / 0
Loss of Signal (Local/Remote): 2 / 0
Loss of Power (Local/Remote): 0 / 0
Loss of Link (Remote): -
Error Seconds (Local/Remote): 119 / 0
FEC Errors (Up/Down): 16.914 / 11.268
CRC Errors (Up/Down): 0 / 50
HEC Errors (Up/Down): 0 / 190
I'm getting lazy again. The speed test was done upstairs wirelessly from the router downstairs - for a Sunday night, when I anticipate a lot of traffic, on a wireless connection, I think that 0.46Mbps upload speed is quite acceptable. A couple of days ago it wasn't achieving 0.3Mbps. 

[#10]

If that poor upload speed persists, maybe you could do a check on an Ethernet connection some time. Why not leave an Ethernet cable plugged into the Modem/Router so you don't have to fiddle with moving it and/or any concealed cables. Just leave it and the other end tucked somewhere handy for when you might want it.
At least the rest looks good, the errors especially good, and you've had no more sync drops since last night.

[#11]

Yeah okay - Ethernet cable down the back of the book case might work! 

[#12]

Greetings. It has been a while before I could get back to this both because of a succession of early starts with work, meaning my only online time would be when it was night time, and because the men digging up the main road went on for about a week longer than scheduled, hence the disruption to whatever they were doing with electricity went on for longer than anticipated. In fact they have replaced the traffic lights controlling a pedestrian crossing - with identical ones, from what I can see! They aren't even the new LED type. When passing, I think maybe the pedestrian push-button box may be new....anyway, its the traffic lights they were messing with.
So, I did the following tonight in this order - ran a couple of speed tests wirelessly (Ookla and Uswitch) and got good download speeds, poor upload speeds
                                                                              logged into the Gateway, looked at the event log (nothing of interest)
                                                                              took some DSL stats
                                                                              disconnected the broadband connection from within the Gateway, waited three minutes, and reconnected
                                                                              ran the Ookla and Uswitch tests as before, no improvement
                                                                              put my ethernet lead between the PC and router, did a BT speed test, copied the result.
                                                                              came on the forum.
I did the disconnection around 7pm, this being a Sunday, so the day is wearing on, but there is plenty of daylight left, whatever influence that has on results.
So here are the copied stats. Remember, the connection time (9 days) was before I did the disconnection at 7pm.
DSL Connection 
Link Information
   

Uptime: 9 days, 6:32:56

DSL Type: ITU-T G.992.5

Bandwidth (Up/Down) [kbps/kbps]: 396 / 8.520

Data Transferred (Sent/Received) [MB/GB]: 304,92 / 3,40

Output Power (Up/Down) [dBm]: 12,2 / 20,5

Line Attenuation (Up/Down) [dB]: 24,2 / 45,0

SN Margin (Up/Down) [dB]: 15,7 / 6,3

System Vendor ID (Local/Remote): TMMB / ----

Chipset Vendor ID (Local/Remote): BDCM / TSTC

Loss of Framing (Local/Remote): 43 / 0

Loss of Signal (Local/Remote): 5 / 0

Loss of Power (Local/Remote): 0 / 0

Loss of Link (Remote): -

Error Seconds (Local/Remote): 1.158 / 94

FEC Errors (Up/Down): 6.202 / 512.333

CRC Errors (Up/Down): 6 / 1.294

HEC Errors (Up/Down): 8 / 14.014


1. Best Effort Test:  -provides background information.
Download  Speed
6.2 Mbps
 
0 Mbps 7.15 Mbps
Max Achievable Speed
Download speedachieved during the test was - 6.2 Mbps
For your connection, the acceptable range of speeds is 2 Mbps-7.15 Mbps.
IP Profile for your line is - 7.52 Mbps
2. Upstream Test:  -provides background information.
Upload Speed
0.26 Mbps
 
0 Mbps 0.83 Mbps
Max Achievable Speed
Upload speed achieved during the test was - 0.26Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.83 Mbps

All in all, I'd say my upload speed is pants, if I may be permitted to use that expression. 
Mick

[#13]

Quote from: mickthefitter

I did the disconnection around 7pm, this being a Sunday, so the day is wearing on, but there is plenty of daylight left, whatever influence that has on results.

Hi Mick,
It is not so much the daylight which is the influence, rather continental AM radio interference travels further after dark and it is that which gives rise to degradation of xDSL operation.
Looks like your US needs to be uncapped.
Kevin

[#14]

Yeah, I know. It was uncapped once before. If its capped again, I don't understand why, since I don't mess with the router by turning it on and off like I once did. And if I needed to, I now know to disconnect it from within the Gateway first.

[#15]

The upstream isn't capped - it is definitely borked, however...

Quote

Upstream Rate IP profile on your line is - 0.83 Mbps