At one level all customers really want to know is what's the problem and when are you going to fix it.
Congestion can be managed fairly , back to the original post FTTC has been rolled out and presumably take up is stretching the backhaul networks. So it come sto fair management , 3Mbs is nothing to 30Mbs but is ;ife and death to someone at the 3Mbs
The way it has degenerated ove rthe past week, makes me think it could be a fault related issue ( in my world troubleshooting a router in a large netwrk that has gone rogue , randomising routing tables is a bear and gives you some whacky problems)
Downbelow 1Mbs ....
In order to get some help you need to post the btspeedtester results I asked for before
fibre available at your exchange will not affect your adsl connection as different systems so that is not the cause of your problem
Hi @andy_p and thanks for posting.
If the engineer visit doesn't resolve this for you drop me over an email with your details and I'll look into it for you. You'll get the contact the moderators link in my profile.
when is engineer visited supposed to happen
this is a copper adsl problem nothing to do with fibre connections
the mods will get back to you in about 3/5 days due to queue and they will find out if congection at your exchange
You were requested to post BT speedtester results both peak and off peak to show your problem.
Thought I'd post an ongoing update, that may help others understand call handling / fault reporting as seen from the customer stand point.
The level 2 Openreach engineer went back to basics and satisfied himself it wasn't anything to do with the connection, and ruled out REIN as cause to the throughput drop offs (no line dropouts remember). He also spent time looking into the problem with Bt Wholesale, going beyond his direct demarcation remite I would argue.
The then current feedback was the exchange was not suffering a hot VP, and that VLAN with my circuit looked fine.
It was then left he would refer back to BT (Retail I guess) for further handling.
Previously I has always received a call back from BT asking about the fault, though this time the fault status was changed to Customer accepted fix ... not true, but I assume there are only so many ways that Openreach can close the fault, and that fault closure didn't raise a call back with BT level 1 call handling.
Prior to knowing this I kicked off an email to the Mods as invited earlier in this thread for an update ( no reply yet , but can I assume the Mods also interact with BT Level 2 at the call centre?)
Contacted BT via chat explaining the issue, which was quickly escalted to their level 2 for a call back.
That conversation has happened, and while we're no closer to a resolution currently, they were keen to have period of monitoring as 'network' issues had effected the exchange earlier.
They left it that I would contact the level 2 team directly if matters haven't improved.
OK it's taking a while, but at this point I feel that BT is involved in my on going issue.
It's also been good to get my MRTG server up and running again, so it can monitor the router's key metrics over extended terms. I can say that a Raspberry Pi makes a great little MRTG server if anyone wanted to go down that route.
Thanks for taking my calls on this and for the update this morning.
Hopefully the change with the suppliers will resolve, as agreed I will call on Saturday.