Web sQuad ISP - Feedback Thread #2

Looney said:
Seems like there’s a Vuma issue in my area. My internet is dead, so are a lot of other neighbours on various ISP’s.

Glenhazel

1000/500

Can you please investigate?
Click to expand...
BouncyNinja said:
Logged calls , both my directors in the same area are off ( Abbotsford area)
Click to expand...
Evening, we saw a large Vuma outage a little earlier, resolved around 16:48. Everyone back up?
 
Mzezman said:
I'm using 208.67.220.200 and quad9 for ipv4 - whats the one you hand out? I am using the default on IPV6 though
Click to expand...
OpenDNS's unicast might be a bit of an issue (I'm not sure they resolve using a locally registered IP, throwing Akamai into a bit of a spin. Try use only the two Quad9 IPs and see if that makes a difference?
 
Any routing issues to East London from JHB? Getting around 38ms WebSquad to WebSquad. Or is this just how it is? Just asking as I get around 19ms to CPT. Quite a big difference.

MTR if it means anything...


Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              10.0.0.249 -    0 |  400 |  400 |    0 |    0 |    0 |    0 |
|                         160.119.???.137 -    0 |  400 |  400 |    0 |    2 |    4 |    2 |
|                          160.119.224.95 -    0 |  400 |  400 |    2 |    2 |  149 |    2 |
|        core.pe-xe-ix01.jb1.za.ws.net.za -    0 |  400 |  400 |    2 |    3 |  149 |    3 |
|                           100.99.99.227 -    0 |  400 |  400 |   22 |   24 |  185 |   24 |
|             core.cr-01.jb1.za.ws.net.za -    0 |  400 |  400 |   21 |   23 |  185 |   24 |
|                          100.94.253.250 -    0 |  400 |  400 |   22 |   24 |  185 |   24 |
|                          160.119.???.90 -    0 |  400 |  400 |   36 |   38 |  200 |   38 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Last edited:
rvanwyk said:
Any routing issues to East London from JHB? Getting around 38ms WebSquad to WebSquad. Or is this just how it is? Just asking as I get around 19ms to CPT. Quite a big difference.

MTR if it means anything...


Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              10.0.0.249 -    0 |  400 |  400 |    0 |    0 |    0 |    0 |
|                         160.119.???.137 -    0 |  400 |  400 |    0 |    2 |    4 |    2 |
|                          160.119.224.95 -    0 |  400 |  400 |    2 |    2 |  149 |    2 |
|        core.pe-xe-ix01.jb1.za.ws.net.za -    0 |  400 |  400 |    2 |    3 |  149 |    3 |
|                           100.99.99.227 -    0 |  400 |  400 |   22 |   24 |  185 |   24 |
|             core.cr-01.jb1.za.ws.net.za -    0 |  400 |  400 |   21 |   23 |  185 |   24 |
|                          100.94.253.250 -    0 |  400 |  400 |   22 |   24 |  185 |   24 |
|                          160.119.???.90 -    0 |  400 |  400 |   36 |   38 |  200 |   38 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Click to expand...

Will take a look here and see if there's any specific reason we're seeing this latency. In general, from JHB, we should see about 26-30ms to EL (assuming the link terminates in CPT) - JHB <> CPT <> EL

rvanwyk said:
Would you store locally? Surely this would need huge storage space depending on the retention.
Click to expand...

Definitely a local solution if we build it. Will dig a little into what it takes, then we should be able to provide some better feedback
 
rvanwyk said:
Any routing issues to East London from JHB? Getting around 38ms WebSquad to WebSquad. Or is this just how it is? Just asking as I get around 19ms to CPT. Quite a big difference.

MTR if it means anything...


Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                              10.0.0.249 -    0 |  400 |  400 |    0 |    0 |    0 |    0 |
|                         160.119.???.137 -    0 |  400 |  400 |    0 |    2 |    4 |    2 |
|                          160.119.224.95 -    0 |  400 |  400 |    2 |    2 |  149 |    2 |
|        core.pe-xe-ix01.jb1.za.ws.net.za -    0 |  400 |  400 |    2 |    3 |  149 |    3 |
|                           100.99.99.227 -    0 |  400 |  400 |   22 |   24 |  185 |   24 |
|             core.cr-01.jb1.za.ws.net.za -    0 |  400 |  400 |   21 |   23 |  185 |   24 |
|                          100.94.253.250 -    0 |  400 |  400 |   22 |   24 |  185 |   24 |
|                          160.119.???.90 -    0 |  400 |  400 |   36 |   38 |  200 |   38 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Click to expand...
websquadza said:
Will take a look here and see if there's any specific reason we're seeing this latency. In general, from JHB, we should see about 26-30ms to EL (assuming the link terminates in CPT) - JHB <> CPT <> EL



Definitely a local solution if we build it. Will dig a little into what it takes, then we should be able to provide some better feedback
Click to expand...
I've checked on the EL link. It seems we're seeing about 14ms on the L2 path between East London and Cape Town, which is a little higher than the usual. I suspect this service may be on the EL <> Bloem <> CPT path rather than direct path, however this is an FNO related matter. If there's an issue on the path, let us know and we'll escalate this for you.
 
websquadza said:
I've checked on the EL link. It seems we're seeing about 14ms on the L2 path between East London and Cape Town, which is a little higher than the usual. I suspect this service may be on the EL <> Bloem <> CPT path rather than direct path, however this is an FNO related matter. If there's an issue on the path, let us know and we'll escalate this for you.
Click to expand...
So to get to EL from JHB, you have to go via CPT?
 
Hi there. I've send a message also my ticket ref is #895216
 
Last edited:
@websquadza hello wake up a bit please are you looking into my ticket? did you see myresponse. looks like websquad support is a bit lackluster lately.
 
Any known issues in Jhb with Vumatel?
Been expiercing very erratic connections with work servers located in the UK.

Been trying to download Pingplotter on my Mac, and it keeps timing out.
Speed tests seems fine

Finally got it downloaded:


Code: 
Target Name: www.summit-group.com
         IP: 109.109.135.207
  Date/Time: 2025/10/01 1:02:27 PM - 2025/10/01 1:12:27 PM

Hop  Sent  PL%     Min     Max     Avg  Host Name / [IP]
  1    53    0    2,26    6,05    2,86  192.168.68.1 [192.168.68.1]
  2    53    0    4,15   12,68    5,13  core.bng-xe-02.jb1.za.wecom.net.za [160.119.230.1]
  3    53    0    4,16   10,94    5,11  160.119.224.92 [160.119.224.92]
  4    52    0    4,42    8,89    5,08  core.pe-xe-ix01.jb1.za.ws.net.za [160.119.224.17]
  5    52    0    4,25   22,50    5,54  160.119.224.54 [160.119.224.54]
  6    52    0   23,49   27,45   24,35  160.119.224.81 [160.119.224.81]
  7    52    0   24,14   31,26   25,65  63-222-113-24.static.as3491.net [63.222.113.24]
  8    51   53  202,90  226,07  205,47  bundle-ether43.br03.frf05.as3491.net [63.218.230.66]
  9    52    0  202,97  226,24  207,11  63-218-231-14.static.as3491.net [63.218.231.14]
 10    52    4  202,76  226,85  204,06  ae-3.r26.frnkge13.de.bb.gin.ntt.net [129.250.4.174]
 11    52    8  202,49  203,74  203,07  ae-4.r23.londen12.uk.bb.gin.ntt.net [129.250.3.12]
 12    52    4  202,35  220,76  203,69  ae-9.r22.londen12.uk.bb.gin.ntt.net [129.250.3.249]
 13    52    0  208,32  220,27  209,84  ae-24.a01.mancen01.uk.bb.gin.ntt.net [129.250.4.190]
 14    52    0  207,99  234,25  210,61  ae-5.a00.mancen01.uk.bb.gin.ntt.net [129.250.4.101]
 15    52    2  200,65  279,54  206,76  83.217.238.110 [83.217.238.110]
 16    52    6  214,22  364,46  242,60  185.149.110.250 [185.149.110.250]
 17    52    4  200,50  234,57  203,20  6d6d883b.reverse.layershift.co.uk [109.109.136.59]
 18    52    4  200,91  206,53  202,80  www.summit-group.com [109.109.135.207]

It's averaging out to 70% on the 8th hop now
 
Last edited:
rvanwyk said:
So to get to EL from JHB, you have to go via CPT?
Click to expand...
MakoPC said:
It's unfortunately the same for PE, everything goes via CPT, no matter the FNO
Click to expand...
Unfortunately the Eastern Cape is generally recognised as South, so terminating in CPT. This is Legacy from when Telkom recognised 3 regions; Eastern as KZN, then Northern as everything in Limpopo, North West, Gauteng, Free State, Mpumalanga, and Southern as Western, Eastern and Northern Cape. Networks have largely retained these "regions" and with the growth of independent operators, quite often relying on Openserve's infrastructure to get back to a local Teraco. Some operators, eg. Frogfoot, implement EVPN in their core, which means they should be able to dynamically "route" L2 services - but this is not implemented by any as yet, and most with NNI in JHB for an out of region service like Eastern Cape, will dogleg via CPT.
 
TwinDucT said:
Any known issues in Jhb with Vumatel?
Been expiercing very erratic connections with work servers located in the UK.

Been trying to download Pingplotter on my Mac, and it keeps timing out.
Speed tests seems fine

Finally got it downloaded:


Code: 
Target Name: www.summit-group.com
         IP: 109.109.135.207
  Date/Time: 2025/10/01 1:02:27 PM - 2025/10/01 1:12:27 PM

Hop  Sent  PL%     Min     Max     Avg  Host Name / [IP]
  1    53    0    2,26    6,05    2,86  192.168.68.1 [192.168.68.1]
  2    53    0    4,15   12,68    5,13  core.bng-xe-02.jb1.za.wecom.net.za [160.119.230.1]
  3    53    0    4,16   10,94    5,11  160.119.224.92 [160.119.224.92]
  4    52    0    4,42    8,89    5,08  core.pe-xe-ix01.jb1.za.ws.net.za [160.119.224.17]
  5    52    0    4,25   22,50    5,54  160.119.224.54 [160.119.224.54]
  6    52    0   23,49   27,45   24,35  160.119.224.81 [160.119.224.81]
  7    52    0   24,14   31,26   25,65  63-222-113-24.static.as3491.net [63.222.113.24]
  8    51   53  202,90  226,07  205,47  bundle-ether43.br03.frf05.as3491.net [63.218.230.66]
  9    52    0  202,97  226,24  207,11  63-218-231-14.static.as3491.net [63.218.231.14]
 10    52    4  202,76  226,85  204,06  ae-3.r26.frnkge13.de.bb.gin.ntt.net [129.250.4.174]
 11    52    8  202,49  203,74  203,07  ae-4.r23.londen12.uk.bb.gin.ntt.net [129.250.3.12]
 12    52    4  202,35  220,76  203,69  ae-9.r22.londen12.uk.bb.gin.ntt.net [129.250.3.249]
 13    52    0  208,32  220,27  209,84  ae-24.a01.mancen01.uk.bb.gin.ntt.net [129.250.4.190]
 14    52    0  207,99  234,25  210,61  ae-5.a00.mancen01.uk.bb.gin.ntt.net [129.250.4.101]
 15    52    2  200,65  279,54  206,76  83.217.238.110 [83.217.238.110]
 16    52    6  214,22  364,46  242,60  185.149.110.250 [185.149.110.250]
 17    52    4  200,50  234,57  203,20  6d6d883b.reverse.layershift.co.uk [109.109.136.59]
 18    52    4  200,91  206,53  202,80  www.summit-group.com [109.109.135.207]

It's averaging out to 70% on the 8th hop now
Click to expand...

Thanks for the pingplotter here. Looks like about 4% (remember look at the last hop first), but and clear on hop 9, which means we're reaching the EU lossless. That 8th hop looks more like ICMP rate limiting.

Overall path from CPT to France looks a little on the high side (+-180ms), we're logging a ticket for that.

However, the handover to NTT seems to be an issue. Any other IPs you're struggling with, want to see if there's a pattern there.
 
websquadza said:
Thanks for the pingplotter here. Looks like about 4% (remember look at the last hop first), but and clear on hop 9, which means we're reaching the EU lossless. That 8th hop looks more like ICMP rate limiting.

Overall path from CPT to France looks a little on the high side (+-180ms), we're logging a ticket for that.

However, the handover to NTT seems to be an issue. Any other IPs you're struggling with, want to see if there's a pattern there.
Click to expand...

Thanks for the tip, I always look at the first one, clearly I don't quite understand this hah.
This is a plot to the ping plotter site, which was slowing down/ timing out the download

Code: 
Target Name: www.pingplotter.com
         IP: 216.92.151.75
  Date/Time: 2025/10/01 1:29:51 PM - 2025/10/01 1:39:51 PM

Hop  Sent  PL%     Min     Max     Avg  Host Name / [IP]
  1    82    0    2,05   11,60    2,93  192.168.68.1 [192.168.68.1]
  2    82    0    4,11   12,15    5,18  core.bng-xe-02.jb1.za.wecom.net.za [160.119.230.1]
  3    82    0    4,14   16,93    5,13  160.119.224.92 [160.119.224.92]
  4    82    0    4,21    9,29    5,11  core.pe-xe-ix01.jb1.za.ws.net.za [160.119.224.17]
  5    82    0    3,89   13,40    5,25  160.119.224.54 [160.119.224.54]
  6    82    0    4,67   10,09    5,89  te0-2-0-7.ccr51.jnb01.atlas.cogentco.com [206.249.0.8]
  7    81    0  168,62  218,46  170,82  be8440.ccr31.par04.atlas.cogentco.com [154.54.172.166]
  8    81    0  169,15  174,46  170,28  be3183.ccr41.par01.atlas.cogentco.com [154.54.38.65]
  9    81    0  175,44  180,82  176,89  port-channel8670.ccr91.lhr01.atlas.cogentco.com [154.54.75.42]
 10    81    0  176,86  184,92  177,83  be2640.agr21.lhr01.atlas.cogentco.com [154.54.73.241]
 11    81    6  176,55  191,51  178,59  gi0-0-1-10.nr12.b020862-1.lhr01.atlas.cogentco.com [149.6.8.193]
 12    81    4  243,53  252,15  245,41  e25.er100a-ewr1-bb.teraswitch.com [64.130.60.66]
 13    81    6  243,76  250,33  245,47  po1.er100b-ewr1-bb.teraswitch.com [64.130.60.23]
 14    81    6  243,30  248,35  245,31  po3.er100b-ewr2-bb.teraswitch.com [64.130.60.33]
 15    81    7  243,95  247,45  245,44  po1.er100a-ewr2-bb.teraswitch.com [64.130.60.50]
 16    79   47  251,84  292,55  256,63  204.16.241.170 [204.16.241.170]
 17    81    7  251,31  258,53  253,02  cr1.pit1.teraswitch.com [204.16.241.181]
 18    81    5  250,36  257,87  253,06  100.90.63.35 [100.90.63.35]
 19    81    5  250,84  259,43  252,77  100.90.63.9 [100.90.63.9]
 20    81    5  251,36  265,93  253,05  172.16.38.10 [172.16.38.10]
 21    81    2  251,21  262,90  253,36  www.pingplotter.com [216.92.151.75]

Gonna try and find another layershift ip, as that was the initial indicator for me

Found another site on the same server:


Code: 
Target Name: www.2heads.com
         IP: 109.109.134.45
  Date/Time: 2025/10/01 1:52:50 PM - 2025/10/01 2:02:50 PM

Hop  Sent  PL%     Min     Max     Avg  Host Name / [IP]
  1   239    0    1,98   20,19    3,08  192.168.68.1 [192.168.68.1]
  2   239    0    4,00   20,96    5,13  core.bng-xe-02.jb1.za.wecom.net.za [160.119.230.1]
  3   239    0    3,69   20,41    5,15  160.119.224.92 [160.119.224.92]
  4   239    0    4,11   21,48    5,12  core.pe-xe-ix01.jb1.za.ws.net.za [160.119.224.17]
  5   239    0    4,21   19,98    5,23  160.119.224.54 [160.119.224.54]
  6   239    0   23,15   33,67   24,54  160.119.224.81 [160.119.224.81]
  7   239    0   24,41   39,40   25,68  63-222-113-24.static.as3491.net [63.222.113.24]
  8   239   59  202,71  216,43  204,29  bundle-ether43.br03.frf05.as3491.net [63.218.230.66]
  9   239    0  202,54  238,34  205,88  63-218-231-14.static.as3491.net [63.218.231.14]
 10   239    1  202,48  343,85  204,43  ae-3.r26.frnkge13.de.bb.gin.ntt.net [129.250.4.174]
 11   239    3  202,13  240,26  203,61  ae-4.r23.londen12.uk.bb.gin.ntt.net [129.250.3.12]
 12   239    3  201,87  235,86  203,59  ae-9.r22.londen12.uk.bb.gin.ntt.net [129.250.3.249]
 13   239    0  207,78  227,86  209,57  ae-24.a01.mancen01.uk.bb.gin.ntt.net [129.250.4.190]
 14   239    0  207,58  247,36  210,21  ae-5.a00.mancen01.uk.bb.gin.ntt.net [129.250.4.101]
 15   239   14  200,38  294,84  213,95  83.217.238.110 [83.217.238.110]
 16   239   15  207,56  418,24  249,78  185.149.110.250 [185.149.110.250]
 17   239   14  200,44  248,20  211,77  6d6d881b.reverse.layershift.co.uk [109.109.136.27]
 18   239   14  200,47  300,38  203,91  www.2heads.com [109.109.134.45]
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X