Web sQuad ISP - Feedback Thread #2

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]
Definitely something on this upstream link to NTT, we have escalated this. Will update as soon as this is resolved.
 
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.
Would Eastern Cape ever become it's own region and we could terminate in PE or should I lose hope and forget about that ever being a possibility? :ROFL:
 
Would Eastern Cape ever become it's own region and we could terminate in PE or should I lose hope and forget about that ever being a possibility? :ROFL:
Gqeberha (NMB) has an internet exchange, NMBINX, run by INX-ZA (JINX/CINX/DINX), operated at NTT's facility in Newton Park. So in theory, there is hope for a local routing "hub" of sorts. https://portal.inx.net.za/statistics/infrastructure/5/bits - you'll notice that there is hardly any traffic here.

Realistically though, there are more factors than just a location to peer. ISPs would need to consider the financial feasibility of operating another POP (colocation space, power costs and cross connects). In addition, there is very little content available in NMB, so pricey NLD capacity from KZN and CPT would still be necessary, in addition to IP transit.

Finally rands and cents. FNOs operate within the Eastern Cape under the premise that they deliver these services in the main "regions". I don't know of any FNOs with ENNI (External network to network) capacity in NMB. They would need to set up presence and ENNI capacity at the same facility as ISPs in NMB, at significant cost. FNOs won't set up capacity without ISPs and ISPs won't set up presence without interconnect - so we have a chicken and egg issue. ISPs also have little incentive to establish presence while FNOs bake backhaul to CPT into their costs (IE, there is no cost advantage for an ISP to set up a POP and procure backhaul capacity to Cape Town, while FNOs deliver the same service in Cape Town at the same price).
 
Gqeberha (NMB) has an internet exchange, NMBINX, run by INX-ZA (JINX/CINX/DINX), operated at NTT's facility in Newton Park. So in theory, there is hope for a local routing "hub" of sorts. https://portal.inx.net.za/statistics/infrastructure/5/bits - you'll notice that there is hardly any traffic here.

Realistically though, there are more factors than just a location to peer. ISPs would need to consider the financial feasibility of operating another POP (colocation space, power costs and cross connects). In addition, there is very little content available in NMB, so pricey NLD capacity from KZN and CPT would still be necessary, in addition to IP transit.

Finally rands and cents. FNOs operate within the Eastern Cape under the premise that they deliver these services in the main "regions". I don't know of any FNOs with ENNI (External network to network) capacity in NMB. They would need to set up presence and ENNI capacity at the same facility as ISPs in NMB, at significant cost. FNOs won't set up capacity without ISPs and ISPs won't set up presence without interconnect - so we have a chicken and egg issue. ISPs also have little incentive to establish presence while FNOs bake backhaul to CPT into their costs (IE, there is no cost advantage for an ISP to set up a POP and procure backhaul capacity to Cape Town, while FNOs deliver the same service in Cape Town at the same price).
Thank you for the explanation I appreciate it, unfortunate that it won't most likely happen, it would have reduced latency to JHB by quite a bit, but luckily it isn't by a huge amount
 
Hi all
East Rand off-line trenched. Vuma
ONT flashing green after reboot

It seems it took hour then it was back.
 
Last edited:
Hi all
East Rand off-line trenched. Vuma
ONT flashing green after reboot

It seems it took hour then it was back.

Noticed this when my home went offline , we out of the country at the moment, so it was a toss up between power or internet
 
Ia there an issue with Google services? Youtube is buffering every 10 seconds tonigh
Same on kakAfrica
Jip. Using Frogfoot through Afrihost.
Noticed this when my home went offline , we out of the country at the moment, so it was a toss up between power or internet
Morning all, seems to have been an issue on Google's side, seeing reduced traffic through our caches as well. We've logged a ticket with Google.
 
Hi @websquadza

Having trouble opening up https://herholdts.co.za/ on my PC.
With LTE router it opens fine, mobile data as well.
Specifically my websquad metrofibre fibre line gives trouble with endless loading, but never actually fully opening the website successfully. A few days ago I had another similar issue with another website. ITs becoming quite frustrating.

I did try 1.1.1.1. and 8.8.8.8 DNS with no change.


Did a pingplotter test now:
Packet loss shows after 41.175.247.151 . Whose at fault here?

Target Name: herholdts.co.za
IP: 102.214.***
Date/Time: 2025/10/26 21:40:39 - 2025/10/26 21:50:39

Hop Sent PL% Min Max Avg Host Name / [IP]
1 13 0 1,75 4,64 2,40 unifi.localdomain []
2 14 0 2,76 12,60 7,89 core.as-01.db1.za.ws.net.za [160.119.237.129]
3 14 0 3,47 18,84 9,76 100.94.254.242 [100.94.254.242]
4 14 0 4,31 11,73 8,88 160.119.237.4 [160.119.237.4]
5 14 0 4,75 12,57 8,51 core.pe-xe-ix01.db1.za.ws.net.za [160.119.232.45]
6 14 0 3,17 11,62 7,03 160.119.237.10 [160.119.237.10]
7 14 0 28,40 37,10 31,64 196-10-141-44.ixp.durban [196.10.141.44]
8 14 0 30,37 40,23 34,30 hu-0-5-0-5.lza-p4-jhb.liquidtelecom.com [5.11.12.165]
9 14 0 12,91 24,15 18,36 hu-0-6-0-3.lza-p3-jhb.liquidtelecom.net [41.175.222.182]
10 14 0 13,00 22,86 18,77 hu-0-1-0-5.lza-p4-jhb.liquidtelecom.net [41.175.242.5]
11 14 0 30,96 39,01 35,39 be-20.lza-pe2-jhb.liquidtelecom.net [41.60.135.93]
12 14 0 13,91 22,13 18,15 41.175.247.151 [41.175.247.151]
13 14 100 0 0 0 herholdts.co.za [102.214.8.46]
 
Sorted, was a Unifi firmware bug

Hi @websquadza

Having trouble opening up https://herholdts.co.za/ on my PC.
With LTE router it opens fine, mobile data as well.
Specifically my websquad metrofibre fibre line gives trouble with endless loading, but never actually fully opening the website successfully. A few days ago I had another similar issue with another website. ITs becoming quite frustrating.

I did try 1.1.1.1. and 8.8.8.8 DNS with no change.


Did a pingplotter test now:
Packet loss shows after 41.175.247.151 . Whose at fault here?

Target Name: herholdts.co.za
IP: 102.214.***
Date/Time: 2025/10/26 21:40:39 - 2025/10/26 21:50:39

Hop Sent PL% Min Max Avg Host Name / [IP]
1 13 0 1,75 4,64 2,40 unifi.localdomain []
2 14 0 2,76 12,60 7,89 core.as-01.db1.za.ws.net.za [160.119.237.129]
3 14 0 3,47 18,84 9,76 100.94.254.242 [100.94.254.242]
4 14 0 4,31 11,73 8,88 160.119.237.4 [160.119.237.4]
5 14 0 4,75 12,57 8,51 core.pe-xe-ix01.db1.za.ws.net.za [160.119.232.45]
6 14 0 3,17 11,62 7,03 160.119.237.10 [160.119.237.10]
7 14 0 28,40 37,10 31,64 196-10-141-44.ixp.durban [196.10.141.44]
8 14 0 30,37 40,23 34,30 hu-0-5-0-5.lza-p4-jhb.liquidtelecom.com [5.11.12.165]
9 14 0 12,91 24,15 18,36 hu-0-6-0-3.lza-p3-jhb.liquidtelecom.net [41.175.222.182]
10 14 0 13,00 22,86 18,77 hu-0-1-0-5.lza-p4-jhb.liquidtelecom.net [41.175.242.5]
11 14 0 30,96 39,01 35,39 be-20.lza-pe2-jhb.liquidtelecom.net [41.60.135.93]
12 14 0 13,91 22,13 18,15 41.175.247.151 [41.175.247.151]
13 14 100 0 0 0 herholdts.co.za [102.214.8.46]
 
Hi @websquadza

Having trouble opening up https://herholdts.co.za/ on my PC.
With LTE router it opens fine, mobile data as well.
Specifically my websquad metrofibre fibre line gives trouble with endless loading, but never actually fully opening the website successfully. A few days ago I had another similar issue with another website. ITs becoming quite frustrating.

I did try 1.1.1.1. and 8.8.8.8 DNS with no change.


Did a pingplotter test now:
Packet loss shows after 41.175.247.151 . Whose at fault here?

Target Name: herholdts.co.za
IP: 102.214.***
Date/Time: 2025/10/26 21:40:39 - 2025/10/26 21:50:39

Hop Sent PL% Min Max Avg Host Name / [IP]
1 13 0 1,75 4,64 2,40 unifi.localdomain []
2 14 0 2,76 12,60 7,89 core.as-01.db1.za.ws.net.za [160.119.237.129]
3 14 0 3,47 18,84 9,76 100.94.254.242 [100.94.254.242]
4 14 0 4,31 11,73 8,88 160.119.237.4 [160.119.237.4]
5 14 0 4,75 12,57 8,51 core.pe-xe-ix01.db1.za.ws.net.za [160.119.232.45]
6 14 0 3,17 11,62 7,03 160.119.237.10 [160.119.237.10]
7 14 0 28,40 37,10 31,64 196-10-141-44.ixp.durban [196.10.141.44]
8 14 0 30,37 40,23 34,30 hu-0-5-0-5.lza-p4-jhb.liquidtelecom.com [5.11.12.165]
9 14 0 12,91 24,15 18,36 hu-0-6-0-3.lza-p3-jhb.liquidtelecom.net [41.175.222.182]
10 14 0 13,00 22,86 18,77 hu-0-1-0-5.lza-p4-jhb.liquidtelecom.net [41.175.242.5]
11 14 0 30,96 39,01 35,39 be-20.lza-pe2-jhb.liquidtelecom.net [41.60.135.93]
12 14 0 13,91 22,13 18,15 41.175.247.151 [41.175.247.151]
13 14 100 0 0 0 herholdts.co.za [102.214.8.46]
Sorted, was a Unifi firmware bug

Thanks for your feedback here. Unifi has a weird MSS calculation quirk. If you see this again, navigate to your WAN interface settings (Devices > USG >WAN) and set the MSS manually. If you're on PPPOE, try 1432 and 1420 to see which works best.
 
Top
Sign up to the MyBroadband newsletter
X