New full fibre connection - bizarrely specific fault.

[#1]

Is IPv6 a factor here ?

I'll have a look with Wireshark later to see exactly what happens...

[#2]

OK. Lacking any other explanation to date, I'm still backing Location, Location, Location.

speedtest.net asks for your location, presumably to find the nearest server. If it can get your location from your device automatically, or otherwise, it quickly selects the optimum server for the test and goes ahead. But what if it can't get your device location?

I suggest it 'pings' your device from a geographical selection of its test hosts and the one with the lowest response time wins and is selected to carry out the test. All this must take time before the test can start.

I know that PN Hub 2 does not respond to the ping command, however there must be some operating response packets from your device that the hosts can use.

(I too wondered about IPv6 but don't have any relevant knowledge to go on)

[#3]

I suggest it 'pings' your device from a geographical selection of its test hosts and the one with the lowest response time wins and is selected to carry out the test. All this must take time before the test can start

I believe it works the other way round, it pings its known servers and selects the one with fastest reply i.e lowest latency.

[#4]

For windows and ubuntu mate I have used https://ipv6.speedtest.net/ for IPv6 speedtest, see also librespeed-cli --ipv4 or --ipv6 option. Clearly you need to be on the IPv6 trial for this link to work.

If you create a speedtest account in "Settings" you can select your preferred server host and location.

Speedtest must do a geolocation check as for me speedtest closest server moves around England.

I can be near to Sheffield, Manchester, Nottingham and others. Today I am in near Oxford, I live in a Portsmouth (PO20) postcode.

[#5]

Didn't think of it before, tried on my phone...

1. Network data OFF, strictly WiFi via Hub 2. Geolocation OFF: Speedtest: "Allow location access?"
"<Speedtest site> wants to know your location". Deny

Speedtest: My Usual IP; University of Oxford, IT services; Speed ~150Mbps

But Speedtest takes ages finding server.

2. Network data ON (4G), WiFi OFF. Geolocation OFF.

Speedtest: O2 IP; Structured Communications, London; Speed <9Mbps ping 59mS!

Speedtest quick to find server

3. Network data ON (4G), WiFi OFF. Geolocation ON (it's guessing!).

Speedtest: O2 IP; Lightning Fibre Ltd (ironic?); Speed <5Mbps ping 60mS

Speedtest quick to find server.

[#6]

@Dan_the_Van 

Speedtest must do a geolocation check as for me speedtest closest server moves around England.

Well Wireshark showed no evidence of any pings to establish the nearest server so that sounds likely.

My server doesnt seem to move , its always the 20i Nottingham (I'm in Derbyshire) . Running the IPv6 test selected Sheffield.

The normal (speedtest.net) test does seem to use both IPv6 and IPv4  

[#7]

---

@pvmb wrote:

Didn't think of it before, tried on my phone...

1. Network data OFF, strictly WiFi via Hub 2. Geolocation OFF: Speedtest: "Allow location access?"
"<Speedtest site> wants to know your location". Deny

Speedtest: My Usual IP; University of Oxford, IT services; Speed ~150Mbps

But Speedtest takes ages finding server.

2. Network data ON (4G), WiFi OFF. Geolocation OFF.

Speedtest: O2 IP; Structured Communications, London; Speed <9Mbps ping 59mS!

Speedtest quick to find server

3. Network data ON (4G), WiFi OFF. Geolocation ON (it's guessing!).

Speedtest: O2 IP; Lightning Fibre Ltd (ironic?); Speed <5Mbps ping 60mS

Speedtest quick to find server.

---

Similarly - if it were location definition problems - this would be the same whether I was connecting my laptop via fibre, or via my phone’s hotspot. In both cases, Safari denies Speedtest  access to location data.

But connecting via the phone hotspot, and the server is located instantly.

I've also tried allowing Speedtest to access location information - verified location is working in Google Maps, and it still takes 20 or 30 seconds to find the server when connected vie fibre, AND I have tried both wired only and wireless only connections to the router. (to mimic wireless hotspot on phone and eliminate that variable.)

I don't believe lack of access to location is causing the problem.


PS - my fixed IP also starts 80.229.

[#8]

Another question for those of you who are not experiencing a "find server" delay.


Are you using the Hub 2?

[#9]

Are you using the Hub 2?

No. I'm using a TPlink ER605 running OpenWrt

[#10]

Are you using the Hub 2?

TP-Link AX53 with manufacturers firmware.

If windows have you tried the Ookla app downloadable from the Microsoft Store?

Have you made any changes to your Hub 2?

Other than the speedtest.net server selection delay is your connection working as expected?

What if you use https://interprefy.speedtestcustom.com/ 

I'm PlusNet 80.229.24n.nn

[#11]

---

@Dan_the_Van wrote:

Are you using the Hub 2?

TP-Link AX53 with manufacturers firmware.

If windows have you tried the Ookla app downloadable from the Microsoft Store?

Have you made any changes to your Hub 2?

Other than the speedtest.net server selection delay is your connection working as expected?

What if you use https://interprefy.speedtestcustom.com/ 

I'm PlusNet 80.229.24n.nn

---

Not windows - mac.

Only changes to hub to has been to open a port (5000-5001) to my server, and set up. custom passwords and wifi ssid/password. That's about it. 

Other than speedtest.net havin't noticed anyting else working incorrectly.

Speedtest custom has the same delay.


I currently have 3x TP link Deco M9 running as access point - I'll try the main one as router when I get some time to set it up.

[#12]

OK - Has someone flicked a switch?

I'm now getting a server in less than 2 seconds from page load.