IDNet (ZenW) 80-20 FTTP Single Thread Speed Issues

We upgraded to 80:20 FTTP on 20th February and since then the TBB test results have been exemplary with the single thread speeds maxing out at the same level as the multithread results. However something has changed since our last good result on the 17th May (see here) and our first poor result on 25th May with the single thread speeds typically being 20Mbps lower (see here).

I have done some other comparative testing on the Ookla Speedtest single thread test and that shows similar results except when the test host is IDNet when the single thread results max out. Compare the Community Fibre result here with the IDNet result here.

Is this likely to be peering issues or something else?

Originally posted on Fibre Broadband here, but more appropriate here.

Edited by jaydub (Thu 01-Jun-23 08:54:37)

Since posting this originally, things have continued in the same vein. There is been a minor drop off in the multithread results but a significant reduction in the single thread results (now in the range 36-60 Mbps - down from >=74Mbps.

Testing on speedtest.net shows the same sort of pattern with the IDNet server returning 74Mpbps results, but other test servers showing significantly less (typically ~45Mbps).

The IDNet response is that they have not had any reports from any other users nor any notifications of any network issues with any of the network operators they peer with.

Is anybody else on FTTP seeing anything similar? I am only on a 80/20 connection, so more interested in results on relatively low speed FTTP connections.

I would appreciate anybody's thoughts on the best way forward here.

Mine appears fine:



But I don't know what backhaul provider I'm on.

In reply to a post by Andrue:

Mine appears fine:



But I don't know what backhaul provider I'm on.

Probably TTB

In reply to a post by adslmax:

In reply to a post by Andrue:

Mine appears fine:



But I don't know what backhaul provider I'm on.

Probably TTB

With IPv6? Sure?

TTB backhaul doesn't care what protocol the ISP is carrying - IPv4 or IPv6, with or without PPPoE.

The session is terminated by the ISP - IDNet in this case - and IDNet's broadband aggregation server provides routing to the customer, using IDNet's IP addresses.

Further update:

My single thread speeds have now dropped to a fairly consistent 28Mbps on a 80/20 connection (constant over the last week).

IDNet are saying that 'it is likely to be upstream from us as this is demonstrated by the single thread test to their speedtest.net server within their network which eliminates both their network and their wholesale supplier network.'

I remain surprised that they don't want to investigate further, so am planning to migrate out to see if I can do better elsewhere.

Time to move on I think. Favouring a BTw backhaul, so probably AAISP, Aquiss or possibly UNO.

I plumped for AAISP in the end.

The migration went through in the early hours of the morning and the difference between IDNet and AAISP is night and day.

Minimum ping times have dropped from 9ms to 7ms and the TBB speed test results are markedly different. Compare last nights IDNET result with this morning's AAISP result.

The only issue I have had was with my AAISP VOIP line, where I couldn't find where I had set the outgoing IP address. A quick phone call to the AAISP help desk had it sorted in very quick time.

I have always been reluctant to pay AAISP's prices, however on the first few hour's experience that is a case of more fool me! I am seriously impressed so far.

Seen this single thread issue in relation to IDNet before on FTTP. It has been knocking around for a couple of years. My understanding (I might be wrong) is that for all FTTP connections they use Zen for the backhaul exclusively and is likely related to that. Not seen any similar reports from ISPs who use BTW as a backhaul (which I believe AAISP do).

In reply to a post by bemak187:

Seen this single thread issue in relation to IDNet before on FTTP. It has been knocking around for a couple of years. My understanding (I might be wrong) is that for all FTTP connections they use Zen for the backhaul exclusively and is likely related to that. Not seen any similar reports from ISPs who use BTW as a backhaul (which I believe AAISP do).

I use IDNet FTTP with Fibreheros backhaul. Performance exemplary. I think they also use some of the other Altnets where available.

In reply to a post by jaydub:

Minimum ping times have dropped from 9ms to 7ms and the TBB speed test results are markedly different.

Um, based on your speedtest graphs, you've also changed speed - so of course they're markedly different' - you're on a faster profile and service so er, you're getting faster speeds.

Did I miss something here - obviously it's faster.

In reply to a post by therioman:

In reply to a post by jaydub:

Minimum ping times have dropped from 9ms to 7ms and the TBB speed test results are markedly different.

Um, based on your speedtest graphs, you've also changed speed - so of course they're markedly different' - you're on a faster profile and service so er, you're getting faster speeds.

Did I miss something here - obviously it's faster.

Its the difference between the multi thread and single thread tests not the headline speed that I think the OP was looking to show. For the AAISP test they are basically the same for both single and multi. On IDNet the single thread test is about half as fast as the multi.

In reply to a post by DrBob:

In reply to a post by bemak187:

Seen this single thread issue in relation to IDNet before on FTTP. It has been knocking around for a couple of years. My understanding (I might be wrong) is that for all FTTP connections they use Zen for the backhaul exclusively and is likely related to that. Not seen any similar reports from ISPs who use BTW as a backhaul (which I believe AAISP do).

I use IDNet FTTP with Fibreheros backhaul. Performance exemplary. I think they also use some of the other Altnets where available.

They were also using City Fibre at one point but I believe Zen is their go to in most cases where one of these altnets isnt an option. I should have probably said IDNet do not use BTW at all any more as far as I know. These single thread issues that come up from time to time with IDNet I have a feeling are down to the Zen backhaul.

Newbie here but been lurking years. I'm with IDNet on Zen backhaul on 80/20 FTTC. My single and my multiple thread are identical, there were issues a while ago but IDNet where aware of it, years ago there was something Zen could do, Brian at IDNet contacted a guy who posted here from Zen about the issue. I think at Zen and a fix was put in place, it did break again but its been fine been fine for over a year now for myself. I get with 7ms ping to London via Ookla to all London Servers. You could have had your backhaul changed to TTB which gets rid of that issue anyway I believe.

I had no issues on my IDNet FTTC connection (which was BTw backhaul). My issues only started when I moved to FTTP and then not immediately. Their altnet FTTP providers don't supply our area so its a choice of ZenW or ZenW.

Brin has been excellent for me in the past, both in his F2S days and in resolving single thread FTTC issues I had a few year's back, so was somwhat surprised about their 'not our issue' attitude this time.

In reply to a post by bemak187:

In reply to a post by therioman:

In reply to a post by jaydub:

Minimum ping times have dropped from 9ms to 7ms and the TBB speed test results are markedly different.

Um, based on your speedtest graphs, you've also changed speed - so of course they're markedly different' - you're on a faster profile and service so er, you're getting faster speeds.

Did I miss something here - obviously it's faster.

Its the difference between the multi thread and single thread tests not the headline speed that I think the OP was looking to show. For the AAISP test they are basically the same for both single and multi. On IDNet the single thread test is about half as fast as the multi.

Spot on. It was the single thread vs multithread differences that were my major cause of concern. I was also seeing some minor degradation in terms of the multithread speed.

In reply to a post by jaydub:

Spot on. It was the single thread vs multithread differences that were my major cause of concern. I was also seeing some minor degradation in terms of the multithread speed.

And on the basis that a picture represents a thousand words, here is the graph of my IDNet and AAISP FTTP TBB Speedtest results: FTTP Results (IDNet [ZenW] & AAISP [BTw])

As can be seen, something fundamentally changed between 17th & 25th May and IDNet were unable or unwilling to see it as their problem. Moving to AAISP resolved the issue.

Odd had similar issue, five days to go before new provider takes over. IDNet simply not interested all is fine according to them So I initiated solution.

Currently weighing up ISP options for when Cityfibre arrive at an industrial unit that I help out with the IT for as a side gig, I've now been able to rule IDNet out as a potential supplier so thanks for posting your feedback.

In reply to a post by NilSatisOptimum:

Odd had similar issue, five days to go before new provider takes over. IDNet simply not interested all is fine according to them So I initiated solution.

IDNet support in general tends to be fine however I think around this issue it comes across as they are uninterested as there is very little they can do and they know that. They seem to be all in with Zen and either don't want to or cant offer BTW as an alternative backhaul.