Web sQuad ISP - Feedback Thread #2

websquadza said:
Thank you, you too!

Octotel typically are available to assist, however on a day like today with skeleton staff it can be slower - and we only have email correspondence with them today. I can see your order has been submitted to Octotel. I'll ask our team to follow up and provide any feedback received.
Click to expand...
Thank you so much.

I have LTE backup, so not a huge deal if I have to wait.
 
r00igev@@r said:
Anyone that is doing serious gaming should use OpenWRT because it will make a difference to their experience as it has the latest Linux kernel with excellent queue management.

What Cudy router are you using? I'd like to give it a go on that as well.
Click to expand...
I hadn't thought of the newer queue management; but yes this will be a significant improvement. Been playing around with the AX3000 model, it has a beefy(er) ARM CPU and a decent (ish) amount of RAM, just low on flash, so we're testing a few things on this box with OpenWRT.
 
Last edited:
r00igev@@r said:
Anyone that is doing serious gaming should use OpenWRT because it will make a difference to their experience as it has the latest Linux kernel with excellent queue management.

What Cudy router are you using? I'd like to give it a go on that as well.
Click to expand...

I have an unused Edge Router X lying around, perhaps I should give this a try.
 
I have been having timeout trouble with a number of servers overseas for the last few days. Here is an MTR:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 182 | 182 | 0 | 0 | 0 | 0 |
| 160.119.238.2 - 2 | 174 | 172 | 2 | 3 | 15 | 4 |
| 100.94.253.249 - 1 | 178 | 177 | 2 | 4 | 44 | 3 |
| core.cr-01.cp1.za.ws.net.za - 1 | 178 | 177 | 2 | 4 | 42 | 4 |
| core.pe-xe-ip01.cp1.za.ws.net.za - 2 | 174 | 172 | 2 | 4 | 42 | 2 |
| 197.159.53.216 - 2 | 170 | 167 | 3 | 6 | 44 | 4 |
|core.100g-0-8-1-wc-ro-ter-scp-2.za.africainx.net - 1 | 178 | 177 | 3 | 5 | 43 | 4 |
| 105.22.72.213 - 2 | 174 | 172 | 2 | 5 | 40 | 5 |
| ce-0-0-4.cr-01-cpt.za.seacomnet.com - 35 | 78 | 51 | 143 | 145 | 156 | 146 |
| ce-0-0-13.cr-01-mrs.fr.seacomnet.com - 2 | 170 | 167 | 136 | 139 | 148 | 137 |
| ae-1.pp-01-mrs.fr.seacomnet.com - 2 | 174 | 172 | 136 | 138 | 192 | 138 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Issue starts at 12th hop. FNO is Openserve. Any advice?


Edit, here is a tracert which is a bit more readable:

Tracing route to [172.67.173.3]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 2 ms 5 ms 5 ms 160.119.238.2
3 5 ms 5 ms 2 ms 100.94.253.249
4 6 ms 4 ms 2 ms core.cr-01.cp1.za.ws.net.za [160.119.233.189]
5 6 ms 5 ms 5 ms core.pe-xe-ip01.cp1.za.ws.net.za [160.119.232.19]
6 5 ms 4 ms 4 ms 197.159.53.216
7 8 ms 21 ms 21 ms core.100g-0-8-1-wc-ro-ter-scp-2.za.africainx.net [41.84.12.44]
8 3 ms 5 ms 7 ms 105.22.72.213
9 146 ms 145 ms * ce-0-0-4.cr-02-cpt.za.seacomnet.com [105.16.30.2]
10 137 ms 139 ms 141 ms ce-0-0-13.cr-02-mrs.fr.seacomnet.com [105.25.160.166]
11 154 ms 137 ms 137 ms ae-1.pp-01-mrs.fr.seacomnet.com [105.16.33.8]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
 
Last edited:
IdlePhaedrus said:
I have been having timeout trouble with a number of servers overseas for the last few days. Here is an MTR:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 182 | 182 | 0 | 0 | 0 | 0 |
| 160.119.238.2 - 2 | 174 | 172 | 2 | 3 | 15 | 4 |
| 100.94.253.249 - 1 | 178 | 177 | 2 | 4 | 44 | 3 |
| core.cr-01.cp1.za.ws.net.za - 1 | 178 | 177 | 2 | 4 | 42 | 4 |
| core.pe-xe-ip01.cp1.za.ws.net.za - 2 | 174 | 172 | 2 | 4 | 42 | 2 |
| 197.159.53.216 - 2 | 170 | 167 | 3 | 6 | 44 | 4 |
|core.100g-0-8-1-wc-ro-ter-scp-2.za.africainx.net - 1 | 178 | 177 | 3 | 5 | 43 | 4 |
| 105.22.72.213 - 2 | 174 | 172 | 2 | 5 | 40 | 5 |
| ce-0-0-4.cr-01-cpt.za.seacomnet.com - 35 | 78 | 51 | 143 | 145 | 156 | 146 |
| ce-0-0-13.cr-01-mrs.fr.seacomnet.com - 2 | 170 | 167 | 136 | 139 | 148 | 137 |
| ae-1.pp-01-mrs.fr.seacomnet.com - 2 | 174 | 172 | 136 | 138 | 192 | 138 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Issue starts at 12th hop. FNO is Openserve. Any advice?


Edit, here is a tracert which is a bit more readable:

Tracing route to [172.67.173.3]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 2 ms 5 ms 5 ms 160.119.238.2
3 5 ms 5 ms 2 ms 100.94.253.249
4 6 ms 4 ms 2 ms core.cr-01.cp1.za.ws.net.za [160.119.233.189]
5 6 ms 5 ms 5 ms core.pe-xe-ip01.cp1.za.ws.net.za [160.119.232.19]
6 5 ms 4 ms 4 ms 197.159.53.216
7 8 ms 21 ms 21 ms core.100g-0-8-1-wc-ro-ter-scp-2.za.africainx.net [41.84.12.44]
8 3 ms 5 ms 7 ms 105.22.72.213
9 146 ms 145 ms * ce-0-0-4.cr-02-cpt.za.seacomnet.com [105.16.30.2]
10 137 ms 139 ms 141 ms ce-0-0-13.cr-02-mrs.fr.seacomnet.com [105.25.160.166]
11 154 ms 137 ms 137 ms ae-1.pp-01-mrs.fr.seacomnet.com [105.16.33.8]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Click to expand...
It looks like a Seacom problem.

1704185828619.png
 
A Trace Route that worked and one that didn't a few minutes apart. Mostly they don't. Not getting the same issue on my Telkom SIM, so assuming it isn't a problem with Openserve's routing.

C:\Users\Administrator>tracert hyprland.org

Tracing route to hyprland.org [172.67.176.121]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 4 ms 5 ms 5 ms 160.119.238.2
3 5 ms 5 ms 9 ms 100.94.253.249
4 47 ms 5 ms 4 ms core.cr-01.cp1.za.ws.net.za [160.119.233.189]
5 5 ms 5 ms 5 ms core.pe-xe-ip01.cp1.za.ws.net.za [160.119.232.19]
6 5 ms 3 ms 10 ms 197.159.53.216
7 4 ms 5 ms 6 ms core.100g-0-8-1-wc-ro-ter-scp-2.za.africainx.net [41.84.12.44]
8 5 ms 5 ms 5 ms 105.22.72.213
9 137 ms * * ce-0-2-4.cr-02-cpt.za.seacomnet.com [105.16.31.2]
10 137 ms 139 ms 138 ms ce-0-0-13.cr-02-mrs.fr.seacomnet.com [105.25.160.166]
11 147 ms 146 ms 145 ms ae-0.pp-01-mrs.fr.seacomnet.com [105.16.32.8]
12 173 ms 174 ms 182 ms cloudflare.mrs.franceix.net [37.49.232.29]
13 173 ms 179 ms 184 ms 162.158.20.242
14 171 ms 170 ms 172 ms 172.67.176.121

Trace complete.

C:\Users\Administrator>tracert hyprland.org

Tracing route to hyprland.org [172.67.176.121]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 4 ms 3 ms 2 ms 160.119.238.2
3 4 ms 3 ms 2 ms 100.94.253.249
4 4 ms 5 ms 3 ms core.cr-01.cp1.za.ws.net.za [160.119.233.189]
5 4 ms 5 ms 5 ms core.pe-xe-ip01.cp1.za.ws.net.za [160.119.232.19]
6 4 ms 4 ms 5 ms 197.159.53.216
7 6 ms 5 ms 4 ms core.100g-0-8-1-wc-ro-ter-scp-2.za.africainx.net [41.84.12.44]
8 5 ms 5 ms 5 ms 105.22.72.213
9 * * 138 ms ce-0-2-4.cr-02-cpt.za.seacomnet.com [105.16.31.2]
10 138 ms 139 ms 138 ms ce-0-0-13.cr-02-mrs.fr.seacomnet.com [105.25.160.166]
11 145 ms 145 ms 145 ms ae-0.pp-01-mrs.fr.seacomnet.com [105.16.32.8]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Click to expand...
 
Have opened a ticket #800067. The Websquad portal also appears to be timing out on ticket submission etc. but that ticket appears to have gone through.

Definitely something problematic up.
 
IdlePhaedrus said:
Have opened a ticket #800067. The Websquad portal also appears to be timing out on ticket submission etc. but that ticket appears to have gone through.

Definitely something problematic up.
Click to expand...
Eish. It's my first day with Web Squad, so support will probably ask me to test a bunch of things if I log this.

Lots of sites just don't work, except now-and-then for a minute or two.

Examples:
wiki.hyprland.org
cricfree.live
torrentio.strem.fun (Stremio add-on)
 
ctriaan said:
Eish. It's my first day with Web Squad, so support will probably ask me to test a bunch of things if I log this.

Lots of sites just don't work, except now-and-then for a minute or two.

Examples:
wiki.hyprland.org
cricfree.live
torrentio.strem.fun (Stremio add-on)
Click to expand...

I have been with WS for a number of years and in general have found their service exemplary. Now that the issue is raised, and appears to affecting their own portal I am hoping it is fixed quite smartly.
 
IdlePhaedrus said:
I have been with WS for a number of years and in general have found their service exemplary. Now that the issue is raised, and appears to affecting their own portal I am hoping it is fixed quite smartly.
Click to expand...
ctriaan said:
Eish. It's my first day with Web Squad, so support will probably ask me to test a bunch of things if I log this.

Lots of sites just don't work, except now-and-then for a minute or two.

Examples:
wiki.hyprland.org
cricfree.live
torrentio.strem.fun (Stremio add-on)
Click to expand...
Apologies for my late response on these posts, just quoting the last two.

There definitely is an issue with some prefixes (specifically cloudflare prefixes) which are not being announced locally, and instead in Marseilles. These prefixes would usually be announced locally, which is a bit odd. It seems there may be a congestion issue upstream affecting traffic from Cloudflare in Marseilles. We have reached out to Cloudflare and Seacom NOCs.

With regards to our portal, we are aware of an unrelated issue (you won't see the timeouts). We are working on this currently.
 
websquadza said:
Apologies for my late response on these posts, just quoting the last two.

There definitely is an issue with some prefixes (specifically cloudflare prefixes) which are not being announced locally, and instead in Marseilles. These prefixes would usually be announced locally, which is a bit odd. It seems there may be a congestion issue upstream affecting traffic from Cloudflare in Marseilles. We have reached out to Cloudflare and Seacom NOCs.

With regards to our portal, we are aware of an unrelated issue (you won't see the timeouts). We are working on this currently.
Click to expand...
Thanks, I also logged Ticket #773484 with Chanelle (hope I spelt correctly) and attached some traceroutes now.
 
websquadza said:
Apologies for my late response on these posts, just quoting the last two.

There definitely is an issue with some prefixes (specifically cloudflare prefixes) which are not being announced locally, and instead in Marseilles. These prefixes would usually be announced locally, which is a bit odd. It seems there may be a congestion issue upstream affecting traffic from Cloudflare in Marseilles. We have reached out to Cloudflare and Seacom NOCs.

With regards to our portal, we are aware of an unrelated issue (you won't see the timeouts). We are working on this currently.
Click to expand...
The twelfth hop does appear to be the interface between Seacom and Cloudflare in France. Good luck.
 
websquadza said:
With regards to our portal, we are aware of an unrelated issue (you won't see the timeouts). We are working on this currently.
Click to expand...
Wanted to pay my bills and saw clientzone and www down :laugh:
 
@websquadza, could you please explain what someone in your sales team meant when she asked if she should set up IPV6 for me? I said "no" because I didn't think I needed it.

I know what IPV6 is, and noticed that my OpenWRT router automatically created a virtual DHCPv6 client "attached to" my PPPOE interface.

What I wanted to know was if she meant she would change it from PPPOE to only DHVPv6 or a static address or am I overthinking this?

Also, is it free or is it an add-on like a static IP?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X