Web sQuad ISP - Feedback Thread #2

Yeah everything feels sluggish. Apple Music very slow. And trying to reach my servers in JHB (from JHB) on Seacom is routing through the Netherlands.
What DNS are you using out of interest?

Thanks for letting me know about Seacom- this is a separate issue due to Seacom’s pathetic peering policy- will ask the team to make some changes to get return path traffic on the right path.

How’s your Netflix looking- that issue is isolated and specific.
 
What DNS are you using out of interest?

Thanks for letting me know about Seacom- this is a separate issue due to Seacom’s pathetic peering policy- will ask the team to make some changes to get return path traffic on the right path.

How’s your Netflix looking- that issue is isolated and specific.

Changed yesterday to DNS you supplied to test as the Netflix issue has been there for a few days. Normally use 1.1.1.1.

Seems everything is back to normal for me.

Agreed, hate Seacom as much as you. But, it used to hop over in Cape Town, now going through NL and UK. Separate issue, but was fine yesterday afaik.
 
Changed yesterday to DNS you supplied to test as the Netflix issue has been there for a few days. Normally use 1.1.1.1.

Seems everything is back to normal for me.

Agreed, hate Seacom as much as you. But, it used to hop over in Cape Town, now going through NL and UK. Separate issue, but was fine yesterday afaik.
On a sidenote, we’re finding Quad1 tend to sometimes unicast out of Non South African IPs, resulting in weirdness with Akamai. Quad9 have this polished and always originate from a South African Unicast.
 
On a sidenote, we’re finding Quad1 tend to sometimes unicast out of Non South African IPs, resulting in weirdness with Akamai. Quad9 have this polished and always originate from a South African Unicast.
Thanks. Saw I'm getting issued 9.9.9.9, 149.112.112.112 and 1.1.1.1. Will leave it at that.
 
Just an FYI on the Seacom side.


Host Loss% Snt Last Avg Best Wrst StDev


1. 192.168.8.1 0.0% 20 0.5 0.6 0.4 0.7 0.1
2. core.bng-xe-02.jb1.za.wecom.net.za 0.0% 19 2.4 2.6 2.3 3.5 0.3
3. 160.119.224.92 0.0% 19 2.6 2.6 2.4 3.4 0.2
4. core.pe-xe-ix01.jb1.za.ws.net.za 0.0% 19 2.5 2.8 2.5 4.2 0.5
5. 160.119.224.54 0.0% 19 3.8 3.5 2.8 4.5 0.4
6. te0-2-0-7.ccr51.jnb01.atlas.cogentco.com 0.0% 19 167.0 167.3 167.0 170.5 0.8
7. be4429.ccr41.lon13.atlas.cogentco.com 0.0% 19 182.4 165.7 163.8 182.4 4.2
8. be12194.ccr41.ams03.atlas.cogentco.com 0.0% 19 169.1 169.0 168.7 169.4 0.2
9. be2020.rcr21.b021535-1.ams03.atlas.cogentco.com 0.0% 19 170.5 170.7 170.4 171.5 0.3
10. 149.29.1.218 0.0% 19 168.6 168.7 168.3 169.2 0.2
11. ae-4.er-01-ams.nl.seacomnet.com 0.0% 19 184.4 184.4 184.0 186.8 0.6
12. ce-0-0-11.cr-02-lhr.uk.seacomnet.com 0.0% 19 188.3 190.0 187.4 218.8 7.1
13. ce-0-1-7.cr-02-cpt.za.seacomnet.com 0.0% 19 187.1 188.1 187.1 189.5 0.8
14. (waiting for reply)
 
We've isolated the issue to a specific peer this morning. Please can you check again.

Please note that we're still waiting on Netflix to assist from their end with the sessions that are down and provide more feedback, their response has been useless, so we are working with limited information, thanks for your patience here.
just got home, tested, and it is sorted (:

Thank you again for the awesome service!
 
So last night i was not dreaming Netflix was bad, switched over to YouTube and watched a movie.
 
So last night i was not dreaming Netflix was bad, switched over to YouTube and watched a movie.
Netflix issue has been resolved. What area and FNO are you on?

Just a quick question IPv6 have we switched yet?
I'm still on IPv4.
We run dual stack on all PPPoE networks. You can enable if you're on a PPPoE. Unfortunately Vumatel are still dragging their feet on implementing v6 on their trenched network.
 
Just an FYI on the Seacom side.


Host Loss% Snt Last Avg Best Wrst StDev


1. 192.168.8.1 0.0% 20 0.5 0.6 0.4 0.7 0.1
2. core.bng-xe-02.jb1.za.wecom.net.za 0.0% 19 2.4 2.6 2.3 3.5 0.3
3. 160.119.224.92 0.0% 19 2.6 2.6 2.4 3.4 0.2
4. core.pe-xe-ix01.jb1.za.ws.net.za 0.0% 19 2.5 2.8 2.5 4.2 0.5
5. 160.119.224.54 0.0% 19 3.8 3.5 2.8 4.5 0.4
6. te0-2-0-7.ccr51.jnb01.atlas.cogentco.com 0.0% 19 167.0 167.3 167.0 170.5 0.8
7. be4429.ccr41.lon13.atlas.cogentco.com 0.0% 19 182.4 165.7 163.8 182.4 4.2
8. be12194.ccr41.ams03.atlas.cogentco.com 0.0% 19 169.1 169.0 168.7 169.4 0.2
9. be2020.rcr21.b021535-1.ams03.atlas.cogentco.com 0.0% 19 170.5 170.7 170.4 171.5 0.3
10. 149.29.1.218 0.0% 19 168.6 168.7 168.3 169.2 0.2
11. ae-4.er-01-ams.nl.seacomnet.com 0.0% 19 184.4 184.4 184.0 186.8 0.6
12. ce-0-0-11.cr-02-lhr.uk.seacomnet.com 0.0% 19 188.3 190.0 187.4 218.8 7.1
13. ce-0-1-7.cr-02-cpt.za.seacomnet.com 0.0% 19 187.1 188.1 187.1 189.5 0.8
14. (waiting for reply)
Evening, let me know how this is looking?
 
Please can you assist with my affiliation program. I have asked soooo many times that they sort it out.

Cape Town still not added since April
East London went live 2 July

Also waiting on feasibility for a JHB site (Link Africa) since 2 July.
 
Please can you assist with my affiliation program. I have asked soooo many times that they sort it out.

Cape Town still not added since April
East London went live 2 July

Also waiting on feasibility for a JHB site (Link Africa) since 2 July.
Evening, will get this sorted for you, our team has had some challenges with the affiliate module requiring some manual intervention. I'll chat to the accounts team tomorrow, thanks for your patience here.

I'll also chat to your SDM and confirm what the hold up is with LA.
 
i've been getting some disconnection but it only last a minute or 2. Pretoria, Openserve. Can you please have a look at this.
 
Thanks for the update, I've asked the team to escalate this urgently.
just back and forths, tests and tests ubt with no end/resolution in sight for this heavily degraded internet experience that starts around 7pm.
even when a meeting is "scheduled", people don't pitch up.

Screenshot 2025-07-27 185854.png

today i got woken up by a call from an evotel tech wanting to come "fix" my problem. they came, re-spliced outside then swapped my ont as well but my issues in the evening still persist (slow international, buffering on yt and a blurry mess on GeForce NOW), and my light levels just stay fluctuating.
Screenshot 2025-07-27 190513.png
Screenshot 2025-07-27 185043.png
Screenshot 2025-07-27 191333.png
Code:
iperf3 -R -u -b 10M -O2 -t 30 -c 169.150.238.161
Connecting to host 169.150.238.161, port 5201
Reverse mode, remote host 169.150.238.161 is sending
[  5] local 10.0.0.20 port 64093 connected to 169.150.238.161 port 5201
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-1.00   sec  1.23 MBytes  10.3 Mbits/sec  2.568 ms  16/912 (1.8%)  (omitted)
[  5]   1.00-2.00   sec  1.15 MBytes  9.68 Mbits/sec  5.059 ms  25/864 (2.9%)  (omitted)
[  5]   0.00-1.01   sec  1.16 MBytes  9.63 Mbits/sec  4.218 ms  36/883 (4.1%)
[  5]   1.01-2.00   sec  1.14 MBytes  9.67 Mbits/sec  4.884 ms  29/861 (3.4%)
[  5]   2.00-3.01   sec  1.14 MBytes  9.52 Mbits/sec  6.552 ms  41/872 (4.7%)
[  5]   3.01-4.01   sec  1.17 MBytes  9.75 Mbits/sec  4.578 ms  20/869 (2.3%)
[  5]   4.01-5.00   sec  1.15 MBytes  9.72 Mbits/sec  3.829 ms  25/862 (2.9%)
[  5]   5.00-6.00   sec  1.16 MBytes  9.79 Mbits/sec  5.102 ms  18/866 (2.1%)
[  5]   6.00-7.01   sec  1.18 MBytes  9.85 Mbits/sec  4.028 ms  12/870 (1.4%)
[  5]   7.01-8.01   sec  1.17 MBytes  9.76 Mbits/sec  4.514 ms  21/874 (2.4%)
[  5]   8.01-9.00   sec  1.15 MBytes  9.72 Mbits/sec  3.965 ms  25/859 (2.9%)
[  5]   9.00-10.01  sec  1.16 MBytes  9.71 Mbits/sec  3.663 ms  27/873 (3.1%)
[  5]  10.01-11.01  sec  1.16 MBytes  9.72 Mbits/sec  5.966 ms  23/871 (2.6%)
[  5]  11.01-12.01  sec  1.15 MBytes  9.63 Mbits/sec  5.026 ms  32/869 (3.7%)
[  5]  12.01-13.01  sec  1.16 MBytes  9.73 Mbits/sec  5.708 ms  24/867 (2.8%)
[  5]  13.01-14.01  sec  1.16 MBytes  9.73 Mbits/sec  4.765 ms  23/869 (2.6%)
[  5]  14.01-15.01  sec  1.17 MBytes  9.80 Mbits/sec  3.460 ms  19/871 (2.2%)
[  5]  15.01-16.00  sec  1.15 MBytes  9.80 Mbits/sec  3.053 ms  17/857 (2%)
[  5]  16.00-17.00  sec  1.16 MBytes  9.69 Mbits/sec  4.879 ms  26/870 (3%)
[  5]  17.00-18.01  sec  1.17 MBytes  9.75 Mbits/sec  2.616 ms  23/876 (2.6%)
[  5]  18.01-19.01  sec  1.15 MBytes  9.61 Mbits/sec  4.730 ms  32/868 (3.7%)
[  5]  19.01-20.00  sec  1.13 MBytes  9.60 Mbits/sec  3.528 ms  36/858 (4.2%)
[  5]  20.00-21.00  sec  1.14 MBytes  9.57 Mbits/sec  4.855 ms  37/870 (4.3%)
[  5]  21.00-22.01  sec  1.16 MBytes  9.69 Mbits/sec  5.162 ms  24/869 (2.8%)
[  5]  22.01-23.01  sec  1.15 MBytes  9.62 Mbits/sec  4.609 ms  36/876 (4.1%)
[  5]  23.01-24.01  sec  1.15 MBytes  9.67 Mbits/sec  4.698 ms  30/869 (3.5%)
[  5]  24.01-25.01  sec  1.15 MBytes  9.64 Mbits/sec  6.612 ms  29/866 (3.3%)
[  5]  25.01-26.01  sec  1.14 MBytes  9.51 Mbits/sec  5.517 ms  42/869 (4.8%)
[  5]  26.01-27.01  sec  1.14 MBytes  9.57 Mbits/sec  4.830 ms  39/869 (4.5%)
[  5]  27.01-28.00  sec  1.14 MBytes  9.69 Mbits/sec  2.048 ms  26/858 (3%)
[  5]  28.00-29.01  sec  1.15 MBytes  9.64 Mbits/sec  5.189 ms  30/870 (3.4%)
[  5]  29.01-30.00  sec  1.16 MBytes  9.72 Mbits/sec  5.830 ms  24/867 (2.8%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-30.06  sec  35.8 MBytes  10.0 Mbits/sec  0.000 ms  0/0 (0%)  sender
[SUM]  0.0-30.1 sec  12050 datagrams received out-of-order
[  5]   0.00-30.00  sec  34.6 MBytes  9.68 Mbits/sec  5.830 ms  826/26048 (3.2%)  receiver

I even said to the tech that these "abnormal" light levels have been here since my fibre got installed (just like i told support for the 2nd/3rd time).
So how would this be the cause of the issue if my internet was literally perfect for 6 months with those abnormal light levels?

I'm not really at my wits end but my family is and I can't even give them an answer to a "why is the internet doing this?" question
 

Attachments

  • Screenshot 2025-07-27 185854.png
    Screenshot 2025-07-27 185854.png
    91.1 KB · Views: 18
seeing big packet loss (or icmp throttling) from hop 5


Host Loss% Snt Last Avg Best Wrst StDev


1. 192.168.8.1 0.0% 22 0.6 0.6 0.4 0.8 0.1
2. core.bng-xe-02.jb1.za.wecom.net.za 0.0% 22 2.3 3.4 2.3 14.1 2.4
3. 160.119.224.92 0.0% 22 2.6 2.7 1.9 3.0 0.2
4. core.pe-xe-ix01.jb1.za.ws.net.za 0.0% 22 2.6 2.7 2.2 3.2 0.2
5. 196-60-10-2.ixp.joburg 57.1% 22 3.4 3.5 3.3 3.8 0.2
196-60-10-1.ixp.joburg
6. netflix.ixp.joburg 63.6% 22 3.8 3.6 3.4 3.9 0.2
196.4.6.17
7. netflix.ixp.joburg 61.9% 21 4.1 3.6 3.0 4.1 0.4
ipv4-c041-jnb001-ix.1.oca.nflxvideo.net
8. ipv4-c041-jnb001-ix.1.oca.nflxvideo.net 69.2% 14 4.8 4.3 3.5 4.8 0.6
Hi RVanWyk,

Is
Code:
ipv4-c041-jnb001-ix.1.oca.nflxvideo.net
A good host to monitor for netflix? (JHB based)
 
Top
Sign up to the MyBroadband newsletter
X