Web Squad ISP

Status
Not open for further replies.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.30.2 - 0 | 61 | 61 | 0 | 0 | 2 | 0 |
| core.cr-xe-01.jb1.za.ws.net.za - 0 | 61 | 61 | 2 | 5 | 39 | 26 |
| 160.119.224.101 - 0 | 61 | 61 | 2 | 4 | 24 | 3 |
| 160.119.224.73 - 0 | 61 | 61 | 1 | 1 | 5 | 2 |
| core.cr-xe-01.jb1.za.ws.net.za - 0 | 61 | 61 | 1 | 1 | 5 | 2 |
| core.pe-xe-ip01.jb1.za.ws.net.za - 0 | 61 | 61 | 2 | 2 | 6 | 2 |
| core.pe-xe-ip01.cp1.za.ws.net.za - 2 | 56 | 55 | 19 | 21 | 28 | 20 |
| 165-69-148-197.as37497.za.net - 13 | 41 | 36 | 20 | 21 | 27 | 25 |
| 162-68-148-197.as37497.za.net - 2 | 57 | 56 | 160 | 162 | 180 | 165 |
| 54-71-148-197.as37497.za.net - 4 | 53 | 51 | 160 | 163 | 199 | 168 |
| 37-66-148-197.as37497.za.net - 7 | 49 | 46 | 160 | 161 | 168 | 168 |
| No response from host - 100 | 12 | 0 | 0 | 0 | 0 | 0 |
| be103.gra-g2-nc5.fr.eu - 7 | 49 | 46 | 169 | 175 | 206 | 179 |
| No response from host - 100 | 12 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 12 | 0 | 0 | 0 | 0 | 0 |
| ns3068235.ip-193-70-81.eu - 7 | 49 | 46 | 168 | 173 | 188 | 171 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


is very broken tonight
13% loss, and the longer it runs, the higher it gets

Seeing this too. We’re working on this- please be patient. We’re working to bring up the JHB RR at the moment so we can troubleshoot the start of the loss in CPT. The loss does not appear in CPT based traces, and there is no loss on our NLD, so we suspect the port facing JHB on this router. It’s unlikely that 3 pieces is hardware are faulty- it’s pretty impossible. But while traffic is flowing, we can’t diagnose it without interruption. So we’re working carefully to make JHB 100%, then delve into this week’s problems once the paths are less burdened.

That said, please remember, On an MTR- your last hop is your packet loss. The intermediate hops suggest where it might start (not every router will reply to every direct ping all the time), but unless it’s 13% or more throughout the chain, that’s not your starting point.
 
Seeing this too. We’re working on this- please be patient. We’re working to bring up the JHB RR at the moment so we can troubleshoot the start of the loss in CPT. The loss does not appear in CPT based traces, and there is no loss on our NLD, so we suspect the port facing JHB on this router. It’s unlikely that 3 pieces is hardware are faulty- it’s pretty impossible. But while traffic is flowing, we can’t diagnose it without interruption. So we’re working carefully to make JHB 100%, then delve into this week’s problems once the paths are less burdened.

That said, please remember, On an MTR- your last hop is your packet loss. The intermediate hops suggest where it might start (not every router will reply to every direct ping all the time), but unless it’s 13% or more throughout the chain, that’s not your starting point.

I can feel that there is something very wrong when I can't go 10 minutes without dc'ing or flat lining.

While I understand you need info to work on, I think multiple people have now complained/given feedback.
 
I can feel that there is something very wrong when I can't go 10 minutes without dc'ing or flat lining.

While I understand you need info to work on, I think multiple people have now complained/given feedback.

We've got all the info we needed - we're currently implementing a fix, this is why we're asking for patience. We're not sitting back and hoping this goes away, rather actively rebuilding hardware and isolating the issue and ensuring our workarounds and improvements work now and into the future. Trust me, we don't want any packet loss that we can help on our network.
 
I can feel that there is something very wrong when I can't go 10 minutes without dc'ing or flat lining.

While I understand you need info to work on, I think multiple people have now complained/given feedback.
As much as I understand how frustrated you are with the issue, trust me when I say, when @websquadza says they are working on it, they are. I know the head technical guy there (also director/owner) and he is very clued up and a straight up guy.

I'm happy to be patient as I feel they are communicating to us (after hours during lockdown of all things) unlike other ISP's who promise everything and never deliver.
 
Connection dropped then came back up, pings are now 300+- to EU, but I'm assuming it's cause you're working on the issue still @websquadza ?

Nothing like after hours support to keep your clientelle happy, eh? I know the feeling all too well.
 
Whilst these types of issues are occurring the Warp+ accounts a MyBB member was handing out is working excellently
 
Connection dropped then came back up, pings are now 300+- to EU, but I'm assuming it's cause you're working on the issue still @websquadza ?

Nothing like after hours support to keep your clientelle happy, eh? I know the feeling all too well.

Yeah, it seems that some international Tier 1s accept our prefixes faster than others (and some withdraw more slowly). So traffic will bounce around until prefix lists are updated globally.
 
Last edited:
Had some jumping around but seems to have settled between 160-170ms to EU, not seeing packet loss at the moment, will keep testing.

Let me know if there is anything I can help with (testing etc).
 
Thanks for the feedback, monitoring closely. Still some tweaks to be made - will update once we're sure it's 100%.

And thank you all for your patience and continued testing and feedback here.
 
Last edited:
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X