|
|
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.
|
|
|
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.
|
|
|
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.
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|