Hi,

Just to confirm, we have investigated, and not found any issue with dsl6.th-lon.

I see that you've raised a support ticket, so your issues will be investigated by our support team.

Regards,

Jon

Hi,

I'd suggest anyone with speed issues raises a ticket with our support teams. Any issues which look to be related to our core/access networks will be escalated to us to investigate, and resolve where necessary.

Some issues will require work from our Tech Support teams, potentially with the help of our suppliers.

I'm just trying to make sure that effort is being focussed in the right areas, as a lot of the reports on this thread appear to be general speed issues, and separate to the single-thread issue.

Hope this clears things up.

Jon

I've been getting similar issues on dsl6.th-lon, but I don't think its related directly to the gateway itself.

I've found that by dropping PPP and re-establishing it, while I always end up on dsl6.th-lon, I don't always seem to go via the same route to get there. Doing so has seen me go from poor speed to normal speed, bad latency to good latency, etc.

I also notice that while I always end up on dsl6.th-lon, other gateways (I've seen dsl4, dsl5 before) are mentioned within the debug output of the PPP daemon on my router as it's establishing a connection, but I always end up on dsl6 in the end.

I've not opened a ticket on this yet as my cabinet got killed by a car crash a couple of weeks ago and its not fully settled yet after they fitted the new cab, and I didn't want to muddy the waters adding potential issues related to that to the mix.

If it helps in any way though, exchange is Bewdley (WMBEW) PCP 3.

Jongreen84 tell me when its going to be fixed. Its months now. Do you have any more info to share, surely team must know now what to problem is.

Fully understand your frustration with this, apologies for the delay.

We're still working with our supplier on the issue of slow single-thread downloads, and have requested an update today. We've been testing with a staff line, and our supplier has found a number of issues that could be the root-cause of this, but we'd still like to confirm.

In reply to a post by aparat:

Jongreen84 tell me when its going to be fixed. Its months now. Do you have any more info to share, surely team must know now what to problem is.

It'd be nice to get some more information other than "we're working on it" repeated ad infinitum. I know there may be commercial and other concerns, but there's surely some wiggle room.


As I said, I used to work in a support role at a major vendor and if I did the same thing with our customers they'd quickly get angry. I suspect Zen is a customer of that vendor (everyone is), and I doubt Zen's network engineers would be happy with "we're working on it, hold tight" for months if they had an open support case with us...

Edited by deleted (Mon 21-Mar-16 13:37:40)

Five days ago I got an update from the ISP on the single thread issue: "The physical issue however appears to lie on BT Openreach equipment. Now we are liaising with them to try and resolve this issue but it has not been easy to identify the root cause." What is odd is that no other ISP appears to have single-thread issues, at least not that I can find in the thinkbroadband forum.

According to an earlier post on this topic, Zen has just two engineers working on this problem. Surely, selling internet connectivity is the core part of the ISP's business and should warrant more urgent and extensive action than this.

I suspect the problem will be solved in the next financial year when equipment can be upgraded or more connectivity purchased from Zen's suppliers.

plusnet have/had them on BT wholesale, they ended up deciding to bypass the shared BTw MISL's and are rolling out a new network.

In reply to a post by Chrysalis:

plusnet have/had them on BT wholesale, they ended up deciding to bypass the shared BTw MISL's and are rolling out a new network.

It's been mentioned that people who are on Zen's unbundled network are also seeing the same thing, so if it's a fault in Openreach, it must be within the NGA kit?

Single thread seems to be working really good tonight:

http://www.thinkbroadband.com/speedtest/results.html...