New full fibre connection - bizarrely specific fault.

[#1]

My full fibre 500 was installed yesterday. All seems to be working fine apart from one detail.

Ive been using speedtest.net (ookla) to measure speed both before and after the upgrade.


Since the upgrade it has been taking 20 to 30 seconds "finding optimal server". This wasn't happening the day before.

It happens with multiple devices (Phone and laptop) with multible browsers (safari and brave), and only with my fibre connection (if I use my phones internet - either with my phone - or by using my phone's hotspot with my laptop - it doesn't happen.)


Any ideas what the reason could be?

[#2]

Clutching at potential straws...

Do you have (did you have) a static IP address?

Having / not having a static IP address changes how you are connected to the internet.  A static IP address belongs to the account, not the connection, but there have been fringe cases of a static IP address being lost on switching services or indeed moving home.

I am on a static IP address with FTTC and there is no noticeable delay in connecting to Ookla speed test service.

IF

• you have a static IP address
• and
• it was 'lost' on switching to FTTP
• and
• service location / connection establishment over the low-touch network is for some reason slower

THEN

• this could be a reason for your reported experience
• you need to ask Plusnet support to reinstate for static IP address

If you DO NOT have a static IP address, the explanation lays elsewhere!

[#3]

Thanks - I do have a static IP - and it has carried over to the new connection, so presumably that is not the issue.

Either way I wouldn't expect a network speed issue to cause up to 30s delay to find a test server, compared to "instant" on a weak phone connection.

It is baffling because I can't find any sluggishness anywhere else at all.

[#4]

I think it may be speedtest.net.

I've been on full fibre for a while - Speedtest.net used to find a server fairly quickly, but now shows the delay you describe. 

[#5]

---

@tonycollinet wrote:

Thanks - I do have a static IP - and it has carried over to the new connection, so presumably that is not the issue.

Either way I wouldn't expect a network speed issue to cause up to 30s delay to find a test server, compared to "instant" on a weak phone connection.

---

I am on FTTP with a static IP address and speedtest.net does take some while finding an "Optimal server" -
University of Oxford, IT Services.

I usually use fast.com

[#6]

Now there’s funny thing !

I have had this behaviour with speedtest.net for a while, not sure how long as I don’t speed all that often. Being FTTP (900) it either works or it doesn’t.

I have a static IP in the range 80.226.x.x. I had assumed it was a problem with speedtest since other speed test sites work fine.

In my case, using Chrome, it consistently takes 42 seconds to find the ‘optimal server’. It’s exactly the same on Firefox and Chrome.

Not a real concern as I’ve not noticed a problem otherwise, interesting though !

[#7]

I have a static IP, stopped using speedtest via a browser or app in favour of the cli version, available for all sensible operating systems.

https://www.speedtest.net/apps/cli the test result can still be shared using a browser link.

https://www.speedtest.net/result/c/e29a789c-7120-4b57-b150-93d2fca2cda3 

[#8]

Which would be valid - if it didn't work perfectly when (as sated : 😜)  I switch to my phone hotspot.


It was also working fine 2 days ago on VDSL.

[#9]

@tonycollinet 

A suggestion: do you have geolocation turned on on your phone?

Doesn't speedtest.net ask for "location"? If it doesn't know your reported location, perhaps it takes longer 'thinking' to find the best host for the test.

[#10]

Wouldn't this be the same between phone and plus-net connections?

[#11]

@tonycollinet 

Depends. Does your PC have geolocation? Do you tell speedtest.net your location?

Perhaps, with a private landline, even on FTTC, it is easier to automatically establish location than on the very different FTTP? 

[#12]

@bobpullen 

Any wisdom to illuminate the anecdotal evidence that speed test is taking a good while to find a server when on FTTP, but not when on FTTC / SoGEA / Mobile please?

To those on FTTP who have responded affirming the experience, are you all of static IP addresses?  If yes that might point to a FTTP + High Touch network consideration.

[#13]

@ Townman  As per my post No 6. It consistently takes 42 seconds to find the optimal server in Chrome, Firefox and Edge.

Curiously on my Android mobile with the sim removed, so definitely on WiFi not mobile data, Speedtest.net finds the server in a couple seconds!

FTTP 900 with a static IP in the  80.229.x.x range.

[#14]

@Townman 

To those on FTTP who have responded affirming the experience, are you all of static IP addresses?  If yes that might point to a FTTP + High Touch network consideration.

I've just tried ( I'm on the same 80.229... subnet as @Batfrog ) and server selection is more or less instant. AFAIK I havent set any server and looking at the settings for speedtest it confirms that ( server 'None' )

[#15]

@Townman @MisterW 

I see no visible delay when using chrome or edge, using the cli speedtest I see

On a raspberry pi
Speedtest by Ookla
[error] Error: [0] Timeout occurred in connect.
Server: Zzoomm Plc - Slough (id: 57318)
ISP: Plusnet

On Windows 11
Speedtest by Ookla
[error] Error: [0] Unknown error
Server: Vodafone UK - Bracknell (id: 23389)
ISP: Plusnet

In both the speedtest completes with my usual results