Status
Not open for further replies.
Same here still . Just wondering how many of us need to complain about international streaming problems before you guys will admit you have an issue?
 



International looking fine here

Upload is normally hit or miss with Speedtests.

And which area are you in and which Fibre Network? Wish I was getting that on my 200mb line... anyway besides that it can be some percentage of their clients that are not affected but it seems that most are... I am on Vumatel Weltevreden Park... did iperf tests and got like 0.23% packet loss. So not sure whether that is good or bad.
 
Ran this at home over wireless, if we had any issues I would happily post it and post it on our announcements page. This is why we run Iperfs etc to narrow down and build a case for the last mile providers, we have been seeing lots of this of late. Once we have those results we can take it up with the provider, there are far more moving parts in the last mile compared to the 3rd layer provider.
 
And which area are you in and which Fibre Network? Wish I was getting that on my 200mb line... anyway besides that it can be some percentage of their clients that are not affected but it seems that most are... I am on Vumatel Weltevreden Park... did iperf tests and got like 0.23% packet loss. So not sure whether that is good or bad.
Vumatel Active Ethernet, Tamboerskloof, Cape Town.

I have barely had any issues with watching twitch so I don't think it's CISP network with international because as Paul said, everyone would be affected if it was them.

One thing to note, it also might be the server the streamer is connecting too. I find if I watch people connecting to a West coast server I see buffering but east coast is way better.
 
Ran this at home over wireless, if we had any issues I would happily post it and post it on our announcements page. This is why we run Iperfs etc to narrow down and build a case for the last mile providers, we have been seeing lots of this of late. Once we have those results we can take it up with the provider, there are far more moving parts in the last mile compared to the 3rd layer provider.

Here are my Iperf Test Results.... please let me know if this shows any packet loss issue or not.

C:\iperf>iperf3.exe -R -u -b 80M -p 17001 -c queen.cisp.co.za
Connecting to host queen.cisp.co.za, port 17001
Reverse mode, remote host queen.cisp.co.za is sending
[ 4] local 192.168.1.162 port 54072 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 9.73 MBytes 81.6 Mbits/sec 0.111 ms 20/1265 (1.6%)
iperf3: OUT OF ORDER - incoming packet = 2301 and received packet = 2314 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2302 and received packet = 2314 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2303 and received packet = 2314 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2304 and received packet = 2314 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2305 and received packet = 2314 AND SP = 4
[ 4] 1.00-2.00 sec 9.55 MBytes 80.1 Mbits/sec 0.105 ms 5/1222 (0.41%)
[ 4] 2.00-3.00 sec 9.54 MBytes 80.0 Mbits/sec 0.183 ms 0/1221 (0%)
[ 4] 3.00-4.00 sec 9.53 MBytes 80.0 Mbits/sec 0.126 ms 0/1220 (0%)
[ 4] 4.00-5.00 sec 9.54 MBytes 80.0 Mbits/sec 0.134 ms 0/1221 (0%)
[ 4] 5.00-6.00 sec 9.53 MBytes 80.0 Mbits/sec 0.110 ms 0/1220 (0%)
[ 4] 6.00-7.00 sec 9.54 MBytes 80.0 Mbits/sec 0.105 ms 0/1221 (0%)
[ 4] 7.00-8.00 sec 9.48 MBytes 79.6 Mbits/sec 0.105 ms 7/1221 (0.57%)
[ 4] 8.00-9.00 sec 9.53 MBytes 79.9 Mbits/sec 0.126 ms 1/1221 (0.082%)
[ 4] 9.00-10.00 sec 9.54 MBytes 80.0 Mbits/sec 0.114 ms 0/1221 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 97.3 MBytes 81.6 Mbits/sec 0.166 ms 34/12452 (0.27%)
[ 4] Sent 12452 datagrams
[SUM] 0.0-10.0 sec 5 datagrams received out-of-order

iperf Done.

C:\iperf>iperf3.exe -u -b 80M -p 17001 -c queen.cisp.co.za
Connecting to host queen.cisp.co.za, port 17001
[ 4] local 192.168.1.162 port 59622 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.00 sec 8.78 MBytes 73.7 Mbits/sec 1124
[ 4] 1.00-2.00 sec 9.52 MBytes 79.8 Mbits/sec 1218
[ 4] 2.00-3.00 sec 9.53 MBytes 79.9 Mbits/sec 1220
[ 4] 3.00-4.00 sec 9.50 MBytes 79.7 Mbits/sec 1216
[ 4] 4.00-5.00 sec 9.54 MBytes 80.0 Mbits/sec 1221
[ 4] 5.00-6.00 sec 9.54 MBytes 80.0 Mbits/sec 1221
[ 4] 6.00-7.00 sec 9.53 MBytes 80.0 Mbits/sec 1220
[ 4] 7.00-8.00 sec 9.56 MBytes 80.2 Mbits/sec 1224
[ 4] 8.00-9.00 sec 9.60 MBytes 80.6 Mbits/sec 1229
[ 4] 9.00-10.00 sec 9.45 MBytes 79.3 Mbits/sec 1210
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 94.6 MBytes 79.3 Mbits/sec 0.154 ms 9466/12002 (79%)
[ 4] Sent 12002 datagrams

iperf Done.

And a speed test to london:
 
Yeah I'm not willing to jump on the pitch fork bandwagon just yet. This is only the second time I've had an issue with streaming twitch in 8 months. Last time it was a bad port on a switch somewhere.

Currently:
7773218491.png

@PBCool Its been getting better slowly. Twitch is also working fine now too. What's the process for iperf testing? What server do I tell it to connect to, do I just use what macedon did above?
 
Twitch has been pretty good for me lately, ran multitwitch streams at 1080p 60fps no buffering whatsoever.
I'm on Octotel 100/100.
Speedtest now:
7773354736.png
 
100/100 Vumatel trenched, Northern suburbs CPT. Don't think I've ever seen speeds this high to the UK before, will test again during peak hours and see..


7774044427.png
 
Here are my Iperf Test Results.... please let me know if this shows any packet loss issue or not.

C:\iperf>iperf3.exe -R -u -b 80M -p 17001 -c queen.cisp.co.za
Connecting to host queen.cisp.co.za, port 17001
Reverse mode, remote host queen.cisp.co.za is sending
[ 4] local 192.168.1.162 port 54072 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 9.73 MBytes 81.6 Mbits/sec 0.111 ms 20/1265 (1.6%)
iperf3: OUT OF ORDER - incoming packet = 2301 and received packet = 2314 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2302 and received packet = 2314 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2303 and received packet = 2314 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2304 and received packet = 2314 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 2305 and received packet = 2314 AND SP = 4
[ 4] 1.00-2.00 sec 9.55 MBytes 80.1 Mbits/sec 0.105 ms 5/1222 (0.41%)
[ 4] 2.00-3.00 sec 9.54 MBytes 80.0 Mbits/sec 0.183 ms 0/1221 (0%)
[ 4] 3.00-4.00 sec 9.53 MBytes 80.0 Mbits/sec 0.126 ms 0/1220 (0%)
[ 4] 4.00-5.00 sec 9.54 MBytes 80.0 Mbits/sec 0.134 ms 0/1221 (0%)
[ 4] 5.00-6.00 sec 9.53 MBytes 80.0 Mbits/sec 0.110 ms 0/1220 (0%)
[ 4] 6.00-7.00 sec 9.54 MBytes 80.0 Mbits/sec 0.105 ms 0/1221 (0%)
[ 4] 7.00-8.00 sec 9.48 MBytes 79.6 Mbits/sec 0.105 ms 7/1221 (0.57%)
[ 4] 8.00-9.00 sec 9.53 MBytes 79.9 Mbits/sec 0.126 ms 1/1221 (0.082%)
[ 4] 9.00-10.00 sec 9.54 MBytes 80.0 Mbits/sec 0.114 ms 0/1221 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 97.3 MBytes 81.6 Mbits/sec 0.166 ms 34/12452 (0.27%)
[ 4] Sent 12452 datagrams
[SUM] 0.0-10.0 sec 5 datagrams received out-of-order

iperf Done.

C:\iperf>iperf3.exe -u -b 80M -p 17001 -c queen.cisp.co.za
Connecting to host queen.cisp.co.za, port 17001
[ 4] local 192.168.1.162 port 59622 connected to 62.233.65.195 port 17001
[ ID] Interval Transfer Bandwidth Total Datagrams
[ 4] 0.00-1.00 sec 8.78 MBytes 73.7 Mbits/sec 1124
[ 4] 1.00-2.00 sec 9.52 MBytes 79.8 Mbits/sec 1218
[ 4] 2.00-3.00 sec 9.53 MBytes 79.9 Mbits/sec 1220
[ 4] 3.00-4.00 sec 9.50 MBytes 79.7 Mbits/sec 1216
[ 4] 4.00-5.00 sec 9.54 MBytes 80.0 Mbits/sec 1221
[ 4] 5.00-6.00 sec 9.54 MBytes 80.0 Mbits/sec 1221
[ 4] 6.00-7.00 sec 9.53 MBytes 80.0 Mbits/sec 1220
[ 4] 7.00-8.00 sec 9.56 MBytes 80.2 Mbits/sec 1224
[ 4] 8.00-9.00 sec 9.60 MBytes 80.6 Mbits/sec 1229
[ 4] 9.00-10.00 sec 9.45 MBytes 79.3 Mbits/sec 1210
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 94.6 MBytes 79.3 Mbits/sec 0.154 ms 9466/12002 (79%)
[ 4] Sent 12002 datagrams

iperf Done.

And a speed test to london:

Please mail me these and use 160M if you have a 200Mbps line. Try do one not at peak times for comparison that we can motivate.
 
Hi @PBCool ,

Our fibre service has been down for almost 5 days now. There has been no feedback on a resolution/ETA of a resolution. Please can you have a look - COOL-20181031-167206

Thanks
 
Hi PBCool

Have you had a chance to look into the RD issues, especially during peak time?
 
Hi PBCool

Have you had a chance to look into the RD issues, especially during peak time?
I did some basic get tests last night and the RD servers performed poorly compared to the other file hosts at peak time. Initial indicators are either they are congested at those times and local traffic wins the demand vs higher latency traffic. This would also explain why multithread works and single doesn't. But am still doing some more tests from other networks etc.
 
I did some basic get tests last night and the RD servers performed poorly compared to the other file hosts at peak time. Initial indicators are either they are congested at those times and local traffic wins the demand vs higher latency traffic. This would also explain why multithread works and single doesn't. But am still doing some more tests from other networks etc.


Is there a possible reason why rain Lte with higher latency and speeds averaging 15mbs streams better than a 200/200 Fibre line if it’s the RD servers?
 
Is there a possible reason why rain Lte with higher latency and speeds averaging 15mbs streams better than a 200/200 Fibre line if it’s the RD servers?
Well this is why I am doing some tests from other networks, it's possible the LTE provider is using application acceleration for instance.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X