Web sQuad ISP - Feedback Thread #2

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.

View attachment 1837219

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.
View attachment 1837216
View attachment 1837214
View attachment 1837217
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
Thanks for reaching out- we’re definitely still seeing the same on the backhaul. Our team is working to set up a call with Evotel. As I said before, the levels weren’t great, but certainly not the cause of your current issue.
 
Hi RVanWyk,

Is
Code:
ipv4-c041-jnb001-ix.1.oca.nflxvideo.net
A good host to monitor for netflix? (JHB based)
You experiencing issues with Netflix?
I’d say monitoring an OCA appliance isn’t the best idea, these tend to go down for maintenance etc.
 
You experiencing issues with Netflix?
I’d say monitoring an OCA appliance isn’t the best idea, these tend to go down for maintenance etc.
Hi, not at the moment, just trying to pick up issues pro-actively.
 
Hi, not at the moment, just trying to pick up issues pro-actively.
Ah i see.

Netflix is a little more difficult to monitor. They serve auth, api and https from AWS endpoints.

Then content is served from OCAs or their caches via peering. So content can shift around, OCAs can go offline for maintenance without affecting your access to services etc. Post the issue experienced recently where peering with Netflix was down and our prefixes leaked by an under-resourced peer, we have enabled offload to 4 separate OCAs in addition to the peering caches across 3 peering points directly and 2 indirectly. In addition, the peer that was leaking our prefixes has also been removed from any paths.

Netflix's architecture is somewhat complicated. The stuff on AWS makes services reachable, but tells you nothing about content. The content exists independently and can be served from anywhere (from Netflix directly or IXP hosted OCAS) - so choosing an endpoint can be hard
 
Last edited:
Glenhazel Vuma Aerial 1000/500

Yeah that definitely looks off - could it not be an ethernet cable issue? Those speeds are oddly close to 100Mbps negotiation speed. Mine is running at line speed - just have a bit download running at the sametime (100/100)

 
Looks like a cable issue somewhere. 93-94 Mbps means you're negotiating 100 Mbps instead of 1 Gbps. Check your cables - ONT <> Router, or router to switch (if you have one).
Okay back to normal. Not sure what happened. Unplugged all the cables and plugged them back in, reset the ONT and everything is working fine now :)
 
It seems gaming is not well currently.
Playing Diablo IV.
Latency is a big issue.
Rubber banding etc. happening.
Sound is also affected.

D4 Latency.jpg

Took a screen shot for info. should be between 180 and 200ms.

Playing to Europe.
 
It seems gaming is not well currently.
Playing Diablo IV.
Latency is a big issue.
Rubber banding etc. happening.
Sound is also affected.

View attachment 1839342

Took a screen shot for info. should be between 180 and 200ms.

Playing to Europe.
That latency is definitely looking very high. Happy to look into this for you. Do you have a server IP I can look into so we can see where this added latency is originating?
 
Ok have some info from CrypticZA help.

IP Address.jpg

Hope this will help?
 
Last edited:
It is back again. Don't know how I will obtain an IP address.

View attachment 1839571
Worse than before.

How's this looking at the moment?
Ok have some info from CrypticZA help.

View attachment 1839591

Hope this will help?
Thanks for this. Took the 3 Diablo IPs, it's pretty much a black hole once we hit Google in JHB. All 4 (battle.net) included are picked up via Google peering in JHB and Google is responsible for traffic to and from peering point to the servers. I'm seeing two servers at approx 160ms, so that's London I assume, and another 2 at about 232ms, which could be EU west or US East. Unfortunately traces don't seem to show any internal Google routing anymore.
 
How's this looking at the moment?

Thanks for this. Took the 3 Diablo IPs, it's pretty much a black hole once we hit Google in JHB. All 4 (battle.net) included are picked up via Google peering in JHB and Google is responsible for traffic to and from peering point to the servers. I'm seeing two servers at approx 160ms, so that's London I assume, and another 2 at about 232ms, which could be EU west or US East. Unfortunately traces don't seem to show any internal Google routing anymore.
Could be a local issue if the route to JHB is fluctuating would cause the full route to be elevated. If Google were dodgy I think a lot of people would be complaining considering Google servers host so much
 
Top
Sign up to the MyBroadband newsletter
X