Cool Ideas Fibre ISP - Feedback

[Saxie]

Octotel parklands, cpt. No internet at the moment. Anyone else or just me?
Ticket ID: COOL-20190323-240568

 

[ekske1]

Yup I think Octotel is a lost cause too. Looks like Artyloop was right

of course he was but I remember the mob telling him otherwise.

 

[Saxie]

Octotel parklands, cpt. No internet at the moment. Anyone else or just me?
Ticket ID: COOL-20190323-240568

Router rebooted and now its up

 

[Seeyou]

So if I'm reading this correctly, my line that was perfect, is now exhibiting packet loss too?

iperf 3.1.3
CYGWIN_NT-10.0 SCIFI 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Sat, 23 Mar 2019 06:33:36 GMT
Connecting to host trcvmh01.cisp.co.za, port 17001
Reverse mode, remote host trcvmh01.cisp.co.za is sending
Cookie: SCIFI.1553322816.325529.11c116b9098a
[ 4] local 192.168.0.101 port 55220 connected to 154.0.15.181 port 17001
Starting Test: protocol: UDP, 1 streams, 1400 byte blocks, omitting 2 seconds, 10 second test
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 2.32 MBytes 19.4 Mbits/sec 0.091 ms 127/1861 (6.8%) (omitted)
[ 4] 1.00-2.00 sec 2.39 MBytes 20.0 Mbits/sec 0.076 ms 0/1787 (0%) (omitted)
[ 4] 0.00-1.00 sec 2.22 MBytes 18.6 Mbits/sec 0.147 ms 126/1788 (7%)
[ 4] 1.00-2.00 sec 2.38 MBytes 20.0 Mbits/sec 0.059 ms 0/1784 (0%)
[ 4] 2.00-3.00 sec 2.21 MBytes 18.6 Mbits/sec 0.088 ms 127/1785 (7.1%)
[ 4] 3.00-4.00 sec 2.39 MBytes 20.0 Mbits/sec 0.029 ms 0/1788 (0%)
[ 4] 4.00-5.00 sec 2.19 MBytes 18.4 Mbits/sec 0.038 ms 145/1786 (8.1%)
[ 4] 5.00-6.00 sec 2.38 MBytes 20.0 Mbits/sec 0.079 ms 0/1783 (0%)
[ 4] 6.00-7.00 sec 2.19 MBytes 18.4 Mbits/sec 0.059 ms 144/1788 (8.1%)
[ 4] 7.00-8.00 sec 2.38 MBytes 20.0 Mbits/sec 0.058 ms 0/1785 (0%)
[ 4] 8.00-9.00 sec 2.19 MBytes 18.4 Mbits/sec 0.055 ms 145/1786 (8.1%)
[ 4] 9.00-10.00 sec 2.38 MBytes 20.0 Mbits/sec 0.067 ms 0/1783 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 23.9 MBytes 20.1 Mbits/sec 0.080 ms 687/17858 (3.8%)
[ 4] Sent 17858 datagrams
CPU Utilization: local/receiver 11.4% (5.4%u/5.9%s), remote/sender 0.0% (0.0%u/0.0%s)

 

[Seeyou]

@Seeyou Twitch is back to its usual garbage capped 300 KB/s for me. Your NNTP fixed?

*EDIT Proxy doesn't change anything either.

Nope, barely pulling half line speed at the moment. Twitch clips are worse than ever. Looks like my line's developed packet loss magically between last week and now. Given your luck getting to the bottom of it, I may as well downgrade my package and save some cash.

 

[image132]

of course he was but I remember the mob telling him otherwise.

Well he was running around attacking anyone who said anything about Octotel. Hell he opened an official complaint with ISPA against CISP for his Octotel issues. The dude was right, the way he went about it was wrong.

So if I'm reading this correctly, my line that was perfect, is now exhibiting packet loss too?

iperf 3.1.3
CYGWIN_NT-10.0 SCIFI 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Sat, 23 Mar 2019 06:33:36 GMT
Connecting to host trcvmh01.cisp.co.za, port 17001
Reverse mode, remote host trcvmh01.cisp.co.za is sending
Cookie: SCIFI.1553322816.325529.11c116b9098a
[ 4] local 192.168.0.101 port 55220 connected to 154.0.15.181 port 17001
Starting Test: protocol: UDP, 1 streams, 1400 byte blocks, omitting 2 seconds, 10 second test
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 2.32 MBytes 19.4 Mbits/sec 0.091 ms 127/1861 (6.8%) (omitted)
[ 4] 1.00-2.00 sec 2.39 MBytes 20.0 Mbits/sec 0.076 ms 0/1787 (0%) (omitted)
[ 4] 0.00-1.00 sec 2.22 MBytes 18.6 Mbits/sec 0.147 ms 126/1788 (7%)
[ 4] 1.00-2.00 sec 2.38 MBytes 20.0 Mbits/sec 0.059 ms 0/1784 (0%)
[ 4] 2.00-3.00 sec 2.21 MBytes 18.6 Mbits/sec 0.088 ms 127/1785 (7.1%)
[ 4] 3.00-4.00 sec 2.39 MBytes 20.0 Mbits/sec 0.029 ms 0/1788 (0%)
[ 4] 4.00-5.00 sec 2.19 MBytes 18.4 Mbits/sec 0.038 ms 145/1786 (8.1%)
[ 4] 5.00-6.00 sec 2.38 MBytes 20.0 Mbits/sec 0.079 ms 0/1783 (0%)
[ 4] 6.00-7.00 sec 2.19 MBytes 18.4 Mbits/sec 0.059 ms 144/1788 (8.1%)
[ 4] 7.00-8.00 sec 2.38 MBytes 20.0 Mbits/sec 0.058 ms 0/1785 (0%)
[ 4] 8.00-9.00 sec 2.19 MBytes 18.4 Mbits/sec 0.055 ms 145/1786 (8.1%)
[ 4] 9.00-10.00 sec 2.38 MBytes 20.0 Mbits/sec 0.067 ms 0/1783 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 23.9 MBytes 20.1 Mbits/sec 0.080 ms 687/17858 (3.8%)
[ 4] Sent 17858 datagrams
CPU Utilization: local/receiver 11.4% (5.4%u/5.9%s), remote/sender 0.0% (0.0%u/0.0%s)

I find it interesting that your line is exhibiting the EXACT same type of "burst" packet loss mine is. Every second result is major packet loss. I don't know whats going on man but the proxy did nothing for me last night and I'm slowly losing my the small amount of faith I had in Octotel.

 

[Seeyou]

I find it interesting that your line is exhibiting the EXACT same type of "burst" packet loss mine is. Every second result is major packet loss. I don't know whats going on man but the proxy did nothing for me last night and I'm slowly losing my the small amount of faith I had in Octotel.

yep, I'm seeing it in my gaming now too. Tiny bursts of packet loss which either cause a small pause or a tiny rubber band effect. I've sent a ticket to CISP, but having followed your adventure from the start, I'm not expecting much.

 

[PBCool]

We had a meeting with the executives at Octotel during this week they have advised they are busy with a core network upgrade, this was the first we have heard of it even after all our complaining. That being said they are commited to resolution and their customers, so we should have some constructive feedback in the next week or two.

 

[jannier]

@PBCool

Vuma Trenched Brackenfell Cape Town 200/200

Is this loss on International and JHB OK?

CPT

C:\iperf>iperf3.exe --verbose --port 17001 -c trcvmh01.cisp.co.za --bandwidth 180M -l 1400 --omit 2 -R -u
iperf 3.1.3
CYGWIN_NT-10.0 JANNIE-PC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Sat, 23 Mar 2019 08:36:17 GMT
Connecting to host trcvmh01.cisp.co.za, port 17001
Reverse mode, remote host trcvmh01.cisp.co.za is sending
Cookie: JANNIE-PC.1553330177.942601.458947b0
[ 4] local 192.168.88.253 port 64916 connected to 154.0.15.181 port 17001
Starting Test: protocol: UDP, 1 streams, 1400 byte blocks, omitting 2 seconds, 10 second test
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 21.6 MBytes 182 Mbits/sec 0.025 ms 481/16696 (2.9%) (omitted)
[ 4] 1.00-2.00 sec 21.5 MBytes 180 Mbits/sec 0.019 ms 0/16075 (0%) (omitted)
[ 4] 0.00-1.00 sec 21.5 MBytes 180 Mbits/sec 0.038 ms 0/16074 (0%)
[ 4] 1.00-2.00 sec 21.5 MBytes 180 Mbits/sec 0.022 ms 0/16072 (0%)
[ 4] 2.00-3.00 sec 21.5 MBytes 180 Mbits/sec 0.041 ms 0/16070 (0%)
[ 4] 3.00-4.00 sec 21.5 MBytes 180 Mbits/sec 0.023 ms 0/16071 (0%)
[ 4] 4.00-5.00 sec 21.5 MBytes 180 Mbits/sec 0.025 ms 0/16072 (0%)
[ 4] 5.00-6.00 sec 21.5 MBytes 180 Mbits/sec 0.024 ms 0/16076 (0%)
[ 4] 6.00-7.00 sec 21.5 MBytes 180 Mbits/sec 0.016 ms 0/16067 (0%)
[ 4] 7.00-8.00 sec 21.5 MBytes 180 Mbits/sec 0.025 ms 0/16070 (0%)
[ 4] 8.00-9.00 sec 21.5 MBytes 180 Mbits/sec 0.021 ms 0/16079 (0%)
[ 4] 9.00-10.00 sec 21.4 MBytes 180 Mbits/sec 0.017 ms 0/16064 (0%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 215 MBytes 181 Mbits/sec 0.019 ms 0/160748 (0%)
[ 4] Sent 160748 datagrams
CPU Utilization: local/receiver 1.4% (0.3%u/1.2%s), remote/sender 2.2% (0.2%u/2.0%s)

iperf Done.

London

C:\iperf>iperf3.exe -R -u -b 180M -p 17001 -c iperf.cisp.co.za
Connecting to host iperf.cisp.co.za, port 17001
Reverse mode, remote host iperf.cisp.co.za is sending
[ 4] local 192.168.88.253 port 62339 connected to 172.104.157.197 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 21.7 MBytes 182 Mbits/sec 0.192 ms 79/2852 (2.8%)
[ 4] 1.00-2.00 sec 21.0 MBytes 176 Mbits/sec 0.172 ms 58/2746 (2.1%)
[ 4] 2.00-3.00 sec 21.5 MBytes 180 Mbits/sec 0.210 ms 1/2748 (0.036%)
iperf3: OUT OF ORDER - incoming packet = 8524 and received packet = 8536 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8525 and received packet = 8536 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8526 and received packet = 8537 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8527 and received packet = 8537 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8528 and received packet = 8537 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8529 and received packet = 8537 AND SP = 4
[ 4] 3.00-4.00 sec 20.8 MBytes 174 Mbits/sec 0.164 ms 93/2747 (3.4%)
iperf3: OUT OF ORDER - incoming packet = 13210 and received packet = 13218 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 13211 and received packet = 13218 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 13212 and received packet = 13218 AND SP = 4
[ 4] 4.00-5.00 sec 21.4 MBytes 179 Mbits/sec 0.269 ms 11/2743 (0.4%)
[ 4] 5.00-6.00 sec 20.8 MBytes 174 Mbits/sec 0.344 ms 89/2747 (3.2%)
[ 4] 6.00-7.00 sec 21.5 MBytes 180 Mbits/sec 0.184 ms 1/2747 (0.036%)
[ 4] 7.00-8.00 sec 21.0 MBytes 176 Mbits/sec 0.223 ms 62/2749 (2.3%)
[ 4] 8.00-9.00 sec 21.5 MBytes 180 Mbits/sec 0.211 ms 0/2746 (0%)
[ 4] 9.00-10.00 sec 21.0 MBytes 176 Mbits/sec 0.139 ms 56/2747 (2%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 219 MBytes 183 Mbits/sec 0.158 ms 450/27996 (1.6%)
[ 4] Sent 27996 datagrams
[SUM] 0.0-10.0 sec 9 datagrams received out-of-order

iperf Done.

C:\iperf>iperf3.exe -R -u -b 180M -p 17001 -c iperf.cisp.co.za
Connecting to host iperf.cisp.co.za, port 17001
Reverse mode, remote host iperf.cisp.co.za is sending
[ 4] local 192.168.88.253 port 61179 connected to 172.104.157.197 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 18.0 MBytes 151 Mbits/sec 0.225 ms 553/2856 (19%)
[ 4] 1.00-2.00 sec 21.4 MBytes 180 Mbits/sec 0.283 ms 3/2745 (0.11%)
[ 4] 2.00-3.00 sec 17.8 MBytes 149 Mbits/sec 0.177 ms 469/2748 (17%)
iperf3: OUT OF ORDER - incoming packet = 8797 and received packet = 8817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8798 and received packet = 8817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8799 and received packet = 8817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8800 and received packet = 8817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8801 and received packet = 8817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8802 and received packet = 8817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8803 and received packet = 8817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8804 and received packet = 8817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8805 and received packet = 8817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8806 and received packet = 8817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8807 and received packet = 8817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8808 and received packet = 8817 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 8809 and received packet = 8817 AND SP = 4
[ 4] 3.00-4.00 sec 21.4 MBytes 180 Mbits/sec 0.261 ms 13/2745 (0.47%)
[ 4] 4.00-5.00 sec 17.8 MBytes 149 Mbits/sec 0.170 ms 471/2747 (17%)
[ 4] 5.00-6.00 sec 21.5 MBytes 180 Mbits/sec 0.247 ms 0/2746 (0%)
[ 4] 6.00-7.00 sec 17.8 MBytes 149 Mbits/sec 0.216 ms 470/2748 (17%)
[ 4] 7.00-8.00 sec 21.5 MBytes 180 Mbits/sec 0.299 ms 0/2746 (0%)
iperf3: OUT OF ORDER - incoming packet = 23404 and received packet = 23413 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 23405 and received packet = 23413 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 23406 and received packet = 23413 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 23407 and received packet = 23413 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 23408 and received packet = 23413 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 23409 and received packet = 23413 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 23410 and received packet = 23413 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 23411 and received packet = 23413 AND SP = 4
iperf3: OUT OF ORDER - incoming packet = 23412 and received packet = 23413 AND SP = 4
[ 4] 8.00-9.00 sec 17.8 MBytes 149 Mbits/sec 0.203 ms 479/2746 (17%)
[ 4] 9.00-10.00 sec 21.5 MBytes 180 Mbits/sec 0.158 ms 2/2748 (0.073%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 219 MBytes 183 Mbits/sec 0.198 ms 2460/27992 (8.8%)
[ 4] Sent 27992 datagrams
[SUM] 0.0-10.0 sec 22 datagrams received out-of-order

iperf Done.


JHB

C:\iperf>iperf3.exe -R -u -b 180M -p 17001 -c lnms.cisp.co.za
Connecting to host lnms.cisp.co.za, port 17001
Reverse mode, remote host lnms.cisp.co.za is sending
[ 4] local 192.168.88.253 port 65041 connected to 154.0.1.254 port 17001
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-1.00 sec 21.6 MBytes 181 Mbits/sec 0.095 ms 86/2853 (3%)
[ 4] 1.00-2.00 sec 21.3 MBytes 179 Mbits/sec 0.101 ms 17/2747 (0.62%)
[ 4] 2.00-3.00 sec 21.4 MBytes 180 Mbits/sec 0.156 ms 6/2746 (0.22%)
[ 4] 3.00-4.00 sec 21.3 MBytes 179 Mbits/sec 0.099 ms 20/2747 (0.73%)
[ 4] 4.00-5.00 sec 21.3 MBytes 179 Mbits/sec 0.115 ms 13/2745 (0.47%)
[ 4] 5.00-6.00 sec 21.0 MBytes 176 Mbits/sec 0.101 ms 61/2747 (2.2%)
[ 4] 6.00-7.00 sec 21.1 MBytes 177 Mbits/sec 0.197 ms 48/2748 (1.7%)
[ 4] 7.00-8.00 sec 21.2 MBytes 178 Mbits/sec 0.104 ms 31/2745 (1.1%)
[ 4] 8.00-9.00 sec 21.2 MBytes 178 Mbits/sec 0.114 ms 38/2746 (1.4%)
[ 4] 9.00-10.00 sec 21.2 MBytes 178 Mbits/sec 0.277 ms 34/2746 (1.2%)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 216 MBytes 181 Mbits/sec 0.111 ms 354/27626 (1.3%)
[ 4] Sent 27626 datagrams

iperf Done.

 

[image132]

We had a meeting with the executives at Octotel during this week they have advised they are busy with a core network upgrade, this was the first we have heard of it even after all our complaining. That being said they are commited to resolution and their customers, so we should have some constructive feedback in the next week or two.

Thank you for the update.

Please tell me you brought up their poor communication skills. I mean why did it take a meeting between you and Octotel for them to let people know they're doing core upgrades? Why couldn't they just inform ISP's and their clients that they're doing it?

 

[PBCool]

Thank you for the update.

Please tell me you brought up their poor communication skills. I mean why did it take a meeting between you and Octotel for them to let people know they're doing core upgrades? Why couldn't they just inform ISP's and their clients that they're doing it?

That point was very much the highlight of the discussion.

 

[alwaysthankful]

@PBCool

Thank you for your effort. I really hope they are telling the truth and it is not just another "we hope this will go away" story. International is now pretty much useless, day and night. Before it was only in peak hours. Restarting the router does not help. Doing the tests on other computers, laptops, tablets, cellphones all give identical results, over wifi and lan.

@PBCool

Another matter, do Netflix and Youtube pay ISP's to prioritize their traffic? Some friends of mine told me that is whats happening in the US.

 

[PBCool]

@PBCool

Thank you for your effort. I really hope they are telling the truth and it is not just another "we hope this will go away" story. International is now pretty much useless, day and night. Before it was only in peak hours. Restarting the router does not help. Doing the tests on other computers, laptops, tablets, cellphones all give identical results, over wifi and lan.

@PBCool

Another matter, do Netflix and Youtube pay ISP's to prioritize their traffic? Some friends of mine told me that is whats happening in the US.

No they don't but if you are a large enough ISP they will place caching appliances on your network for better performance of their services.

 

[alwaysthankful]

@PBCool
"No they don't but if you are a large enough ISP they will place caching appliances on your network for better performance of their services"

Oh ok, but it is true in the US. Netflix did sign an agreement with Comcast, and other ISPS'.

 

[MDE]

We had a meeting with the executives at Octotel during this week they have advised they are busy with a core network upgrade, this was the first we have heard of it even after all our complaining. That being said they are commited to resolution and their customers, so we should have some constructive feedback in the next week or two.

@PBcool

Thanks for the update. Did they give you a time frame on how far they are and when they going to be completed? Have they started? What should customers lookout for? Are there new features similar to the Vumatel shopping portal?

 

[image132]

@PBcool

Thanks for the update. Did they give you a time frame on how far they are and when they going to be completed? Have they started? What should customers lookout for? Are there new features similar to the Vumatel shopping portal?

Wow wow wow, hold your horses their partner. Lets not do complicated things.

They need to fix their network first and if possible eliminate the packet loss. For now lets just focus on that. I've been sitting with this rubbish for 6 months now.

Side note, hope your kid is doing better.

 

[MDE]

Wow wow wow, hold your horses their partner. Lets not do complicated things.

They need to fix their network first and if possible eliminate the packet loss. For now lets just focus on that. I've been sitting with this rubbish for 6 months now.

Side note, hope your kid is doing better.

Lol completely agree ATM sitting with 5% loss but weirdly I'm able to stream fine. :/ I'm a technical person so any new features and mods are exciting...if it happens

 

[ArtyLoop]

We had a meeting with the executives at Octotel during this week they have advised they are busy with a core network upgrade, this was the first we have heard of it even after all our complaining. That being said they are commited to resolution and their customers, so we should have some constructive feedback in the next week or two.

ANY DAY NOW (TM)

 

[stefan9]

So when is my ticket getting resolved...

#COOL-20180711-122832

Last I heard I was getting some box to track, not happened. Issue still unresolved. Ticket now been open for 8 months.

This simply not on and no I don't care whether its Frogfoot's fault or not. Get it resolved...

 

[SeaSickMama]

@TheRoDent

Any reason for this


Tracert to PUBG Server from JHB

Then

Same server but from Cape Town ?

Obviously we both Cool Ideas