New FTTP

[Madhatter]

Hi, I've had FTTP installed and using a Fritzbox 7530. Changed it to use modem and it's connected, the DL speeds are a 6th of what they should be. I am getting 83MB down and 57 up, package is 500 DL and 68 UL. Will it improve or is there a fault?

[Ripshod]

"file sharing may do in future."

That would likely still be possible (and gaming).

Look on the main status page on the router to see if you're getting an IPv6 address. If you are then all is not lost 🤞

[Madhatter]

Hi, at the bottom of the page where the IP4 address is, IP6 is blank.

Have to say really disappointed as getting random freezes of webpages that load OK at other times, not a load issue as currently home alone, fully expect slower performance when kids home.

The strange thing is, my download speeds fluctuates on speed test, Ookla it's 20MB to 460MB but UL is always consistent.

Ran the tests with nothing else going on so can't blame it on local network activity.

[Cynric]

@Madhatter  Was Ookla done over WiFi or Ethernet? Did you try the speed test built-in the router (assuming it's still there)?

[Madhatter]

Hi,

It was done over ethernet using a GB dongle connected via USB C to laptop and nothing else, all.orher rj45 removed and WiFi turned off.

[Cynric]

@Madhatter I don't know what a "GB dongle" is, but it sounds painful, have you been to the GP with it. Anyway, enough hilarity, only ethernet connections to the router are reliable. Also the should be a speed test in the router itself, or so I understand.

[Madhatter]

My work laptop, like most modern ones doesn't have a dedicated RJ45 port, I use a USB dongle that provided RJ45, USB, HDMI inputs.

Tried finding the speed test but didn't see it, will have a look again.

Thanks

[Cynric]

@Madhatter Thanks for the clarification, I have a USB-C to Ethernet adaptor for the same reason.

[Madhatter]

Speeds were still erratic and support said below minimum guarantee, his done a router upgrade and now IP6 showing an entry on the main page under IP6 address.

Speed is between 380 to 470, which is great but still finding the same web page within 5 to 10 minutes will not load.

Not sure what is going on.

[Madhatter]

Ran some pings and Tracert, I changed the DNS to Cloudlflare about 4 days ago as issues unresolved despite several attempts by VF and OR.

Is the issue at my end? I do have two homeplugs of different standards connected to LAN 3 and 4, 1 and 2 are hardwired with GB switches at end of both.

Thereis some packet loss and the Tracrt returns some lines with an * for the timings

C:\ping www.google.com

Pinging www.google.com [2a00:1450:4009:81f::2004] with 32 bytes of data:
Reply from 2a00:1450:4009:81f::2004: time=77ms
Reply from 2a00:1450:4009:81f::2004: time=21ms
Reply from 2a00:1450:4009:81f::2004: time=17ms
Reply from 2a00:1450:4009:81f::2004: time=32ms

Ping statistics for 2a00:1450:4009:81f::2004:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 77ms, Average = 36ms

C:\ping www.google.com

Pinging www.google.com [2a00:1450:4009:81f::2004] with 32 bytes of data:
Reply from 2a00:1450:4009:81f::2004: time=75ms
Reply from 2a00:1450:4009:81f::2004: time=32ms
Reply from 2a00:1450:4009:81f::2004: time=30ms
Request timed out.

Ping statistics for 2a00:1450:4009:81f::2004:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 75ms, Average = 45ms

C:\ping www.google.com

Pinging www.google.com [2a00:1450:4009:81f::2004] with 32 bytes of data:
Reply from 2a00:1450:4009:81f::2004: time=26ms
Reply from 2a00:1450:4009:81f::2004: time=20ms
Reply from 2a00:1450:4009:81f::2004: time=49ms
Reply from 2a00:1450:4009:81f::2004: time=73ms

Ping statistics for 2a00:1450:4009:81f::2004:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 73ms, Average = 42ms

C:\ping www.google.com

Pinging www.google.com [2a00:1450:4009:81f::2004] with 32 bytes of data:
Reply from 2a00:1450:4009:81f::2004: time=90ms
Request timed out.
Reply from 2a00:1450:4009:81f::2004: time=19ms
Reply from 2a00:1450:4009:81f::2004: time=16ms

Ping statistics for 2a00:1450:4009:81f::2004:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 90ms, Average = 41ms

C:\>ping www.google.com

Pinging www.google.com [2a00:1450:4009:81e::2004] with 32 bytes of data:
Destination host unreachable.
Reply from 2a00:1450:4009:81e::2004: time=15ms
Reply from 2a00:1450:4009:81e::2004: time=15ms
Reply from 2a00:1450:4009:81e::2004: time=17ms

Ping statistics for 2a00:1450:4009:81e::2004:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 17ms, Average = 15ms

C:\>tracert www.google.com

Tracing route to www.google.com [2a00:1450:4009:81f::2004]
over a maximum of 30 hops:

1 36 ms 24 ms 14 ms 2a0a:ef40:1049:1:170c:6eed:6ac7:bdbf
2 55 ms 74 ms 116 ms 2a0a:ef40:ffff:1a::1
3 15 ms 23 ms 25 ms 2a0a:ef40:ffff:f00::1
4 14 ms * 138 ms ae15-100-xcr1.slo.cw.net [2001:5000:1300:6::1]
5 27 ms 21 ms 33 ms ae16-xcr1.lnd.cw.net [2001:5000:0:225::1]
6 21 ms 30 ms 61 ms ae15-xcr1.lns.cw.net [2001:5000:0:1e9::2]
7 28 ms 51 ms 23 ms as15169-gw-xcr1.lns.cw.net [2001:5000:1100:7::2]
8 62 ms 48 ms 27 ms 2a00:1450:8135::1
9 49 ms 30 ms 23 ms 2001:4860:0:1::54c8
10 26 ms 17 ms 53 ms 2001:4860:0:1::54d1
11 14 ms 14 ms 14 ms lhr25s33-in-x04.1e100.net [2a00:1450:4009:81f::2004]

Trace complete.

C:\>tracert www.google.com

Tracing route to www.google.com [2a00:1450:4009:821::2004]
over a maximum of 30 hops:

1 4 ms 4 ms 5 ms 2a0a:ef40:1049:1:170c:6eed:6ac7:bdbf
2 9 ms 13 ms 9 ms 2a0a:ef40:ffff:1a::1
3 10 ms 10 ms 10 ms 2a0a:ef40:ffff:f00::1
4 11 ms 14 ms 11 ms ae15-100-xcr1.slo.cw.net [2001:5000:1300:6::1]
5 15 ms 14 ms 18 ms ae16-xcr1.lnd.cw.net [2001:5000:0:225::1]
6 14 ms 14 ms * ae15-xcr1.lns.cw.net [2001:5000:0:1e9::2]
7 15 ms 20 ms * as15169-gw-xcr1.lns.cw.net [2001:5000:1100:7::2]
8 15 ms * 15 ms 2a00:1450:80f9::1
9 15 ms 15 ms 13 ms 2001:4860:0:1::41aa
10 21 ms 21 ms 18 ms 2001:4860:0:1::7dfe
11 * 16 ms 16 ms 2001:4860::c:4002:aff7
12 34 ms 79 ms 33 ms 2001:4860::9:4001:2716
13 16 ms 16 ms * 2001:4860:0:1::7e4b
14 15 ms 15 ms 15 ms 2001:4860:0:1::5379
15 15 ms 15 ms 15 ms lhr48s28-in-x04.1e100.net [2a00:1450:4009:821::2004]

Trace complete.

C:\>tracert www.google.com

Tracing route to www.google.com [2a00:1450:4009:821::2004]
over a maximum of 30 hops:

1 4 ms 5 ms 4 ms 2a0a:ef40:1049:1:170c:6eed:6ac7:bdbf
2 13 ms 14 ms 13 ms 2a0a:ef40:ffff:1a::1
3 10 ms 10 ms 11 ms 2a0a:ef40:ffff:f00::1
4 10 ms * 11 ms ae15-100-xcr1.slo.cw.net [2001:5000:1300:6::1]
5 15 ms 16 ms 15 ms ae16-xcr1.lnd.cw.net [2001:5000:0:225::1]
6 15 ms 16 ms 14 ms ae15-xcr1.lns.cw.net [2001:5000:0:1e9::2]
7 14 ms 15 ms 14 ms as15169-gw-xcr1.lns.cw.net [2001:5000:1100:7::2]
8 20 ms * * 2a00:1450:80f9::1
9 14 ms 14 ms 14 ms 2001:4860:0:1::41aa
10 16 ms 18 ms 29 ms 2001:4860:0:1::7dfe
11 16 ms 22 ms 16 ms 2001:4860::c:4002:aff7
12 15 ms * 17 ms 2001:4860::9:4001:2716
13 16 ms 16 ms 14 ms 2001:4860:0:1::7e4b
14 16 ms 25 ms 15 ms 2001:4860:0:1::5379
15 15 ms 15 ms 15 ms lhr48s28-in-x04.1e100.net [2a00:1450:4009:821::2004]

Trace complete.

C:\>tracert www.google.com

Tracing route to www.google.com [2a00:1450:4009:81f::2004]
over a maximum of 30 hops:

1 Destination host unreachable.

Trace complete.

C:\>tracert www.google.com

Tracing route to www.google.com [2a00:1450:4009:81f::2004]
over a maximum of 30 hops:

1 4 ms 4 ms 4 ms 2a0a:ef40:1049:1:170c:6eed:6ac7:bdbf
2 10 ms 10 ms 10 ms 2a0a:ef40:ffff:1a::1
3 11 ms 10 ms 11 ms 2a0a:ef40:ffff:f00::1
4 11 ms 10 ms 11 ms ae15-100-xcr1.slo.cw.net [2001:5000:1300:6::1]
5 15 ms 14 ms 15 ms ae16-xcr1.lnd.cw.net [2001:5000:0:225::1]
6 15 ms 22 ms 16 ms ae15-xcr1.lns.cw.net [2001:5000:0:1e9::2]
7 14 ms 14 ms 15 ms as15169-gw-xcr1.lns.cw.net [2001:5000:1100:7::2]
8 15 ms 15 ms * 2a00:1450:8135::1
9 15 ms 15 ms * 2001:4860:0:1::54c8
10 14 ms 14 ms 14 ms 2001:4860:0:1::54d1
11 14 ms 14 ms 14 ms lhr25s33-in-x04.1e100.net [2a00:1450:4009:81f::2004]

Trace complete.

C:\>tracert www.google.com

Tracing route to www.google.com [2a00:1450:4009:81e::2004]
over a maximum of 30 hops:

1 4 ms 5 ms 4 ms 2a0a:ef40:1049:1:170c:6eed:6ac7:bdbf
2 10 ms 9 ms 9 ms 2a0a:ef40:ffff:1a::1
3 9 ms 10 ms 10 ms 2a0a:ef40:ffff:f00::1
4 11 ms 12 ms 11 ms ae15-100-xcr1.slo.cw.net [2001:5000:1300:6::1]
5 14 ms 15 ms 16 ms ae16-xcr1.lnd.cw.net [2001:5000:0:225::1]
6 45 ms 14 ms 15 ms ae15-xcr1.lns.cw.net [2001:5000:0:1e9::2]
7 14 ms 15 ms 14 ms as15169-gw-xcr1.lns.cw.net [2001:5000:1100:7::2]
8 18 ms 16 ms 16 ms 2a00:1450:80ff::1
9 17 ms 18 ms 16 ms 2001:4860:0:1::2fe4
10 15 ms 21 ms 16 ms 2001:4860:0:1::7dc2
11 16 ms 16 ms 16 ms 2001:4860::c:4002:aff7
12 17 ms 16 ms 16 ms 2607:f8b0:e000::a
13 15 ms 15 ms 15 ms 2001:4860:0:1::54cb
14 15 ms 15 ms 15 ms lhr25s32-in-x04.1e100.net [2a00:1450:4009:81e::2004]

Trace complete.

[Ripshod]

Disable IPv6 and run the traceroute again - you may be pleasantly surprised. While lag can cause general slowness (and I agree the pings are slow on your IPv6), generally it has no effect on your overall speed.

Let's sort out your IPv4 connection first, then look at your IPv6.