Hey
@websquadza ,
Please can you chat to your team about the internet quality in our estate (perhaps check the calls logged), we are getting random disconnections and packetloss frequently (during working hours, teams meetings etc), we have logged numerous calls and even though I largely gave up on the issue, this is my last resort before seeking a new ISP. last night at 9:35 till 10:00pm was another bad one
Tickets logged in the past:
#865568
#859964
#262078
I am giving up because I have supplied all the MTR results etc etc, and no resolution in sight yet.
Last night example:
View attachment 1822478
Hi There
Thanks for your patience and continued support, and for reaching out and bringing this to my attention.
Could you please add one more IP to your monitoring, the gateway IP you're seeing on your PPPOE (you can pick this up on your router), as this will help us see if your connection is routable your home and our network handover. While I see your PPPOE is staying up, I'd like to see if traffic is flowing. PPPOE is usually quite sensitive, so if L2 is down, PPPOE drops, but I want to see if there isn't something causing issues with the actual flow of PPPOE packets. We have noted that an NLD flapped last night, however this would not have affected you.
Looking at your tickets below, there have been varied issues and I see you've had some headaches here. But we're certainly keen to investigate these, and ensure that these are resolved permanently.
I have checked on these tickets, and I see the following.
#865568 - This one was us. We experienced a fault on our BNG which you connect to, a memory exhaustion error, and routes didn't clear out of the routing table quickly enough (or at all). We have made adjustments to our devices to ensure this behaviour is prevented in future.
#859964 - FNO (Comtel Connect) upgraded a device at their POP without any prior notification, affecting all the services linked to POP. Unfortunately this was done during production traffic, which was not ideal. I note you mentioned on the ticket that this only affected Web sQuad off this POP. This is odd, as the FNO confirmed all services were affected, and the RFO was shared with you.
#262078 - Part of a larger issue that stemmed from a faulty configuration issue. Web sQuad had a legacy VLAN at the POP, and new VLAN configs introduced during 2024 by the FNO. While you were on the newer VLAN, 3 clients connecting to this POP were on the legacy VLAN and the FNO had bridged both VLANs towards us as a single service. The OLTs at the POP saw these duplicate MACs as potential loops and would randomly drop traffic it incorrectly thought was broadcast. This issue could only affect Web sQuad due to the VLANs being Web sQuad specific and caused major headaches for our clients and us while we worked with the FNO to resolve the issue. Unfortunately as per our RFO to you, we don't get to see what the FNOs do on their end and this particular one caused a lot of distress.
We're not an ISP to point fingers, and will always acknowledge if a fault lies with us, and hound our FNOs if the issue is on their side, until issues are resolved.
I'm also asking the team to review all your tickets and correlate them to any other network incidents we may have experienced.
Please PM me any other issues you may have and I'll be happy to investigate further.