Cool Ideas Fibre ISP - Feedback

Status
Not open for further replies.
jamot said:
Hi guys,

Is there anyway I can get CoolIdeas and Vumatel to move quicker on my Fibre setup/installation?

I've been waiting for close to a month now for these guys to setup my fibre line and all i've been getting is excuses. So frustrating!
Click to expand...
No, just hurry up and wait.
 
My Vuma line too 3 days from ordering to active. Was super surprised by the turn around especially after getting the run around for 6 weeks with TT Connect.
 
No idea what octotel did this weekend but my line in kenilworth is somehow decent again
100/25 account

2019-03-04 12_28_42-Window.png
 
Hype said:
My Vuma line too 3 days from ordering to active. Was super surprised by the turn around especially after getting the run around for 6 weeks with TT Connect.
Click to expand...
I ordered my line at 4:30PM on a friday, they installed saterday morning at 9AM :) beat that
 
I posted this in the RocketNet thread but this one is more active.

Does anyone know exactly what Octotel is referring to by "node maintenance" - I sure hope it means they're fixing things.

Octotel engineers will be performing node maintenance in the following areas: in a day
Octotel engineers will be performing node maintenance in the following areas:
Sea Point Strand Cape Gate Rondebosch Blouberg Green Point Vredehoek/ City Bowl East CBD
Please see dates and timelines below:
Sea Point: 5 March 2019 Time: 4am - 5am
Strand: 7 March 2019 Time: 4am - 5am
Cape Gate: 7 March 2019 Time: 4am - 5am
Rondebosch: 12 March 2019 Time: 4am - 5am
Blouberg: 14 March 2019 Time: 4am - 5am
Green Point: 19 March 2019 Time: 4am - 5am
Vredehoek: 19 March 2019 Time: 4am - 5am
East CBD: 19 March 2019 Time: 4am - 5am
During this time, subscribers may experience packet loss and high latency.
Octotel engineers will be onsite during this maintenance to ensure that downtime is kept to an absolute minimum
For more information on this maintenance, please contact support on 087 470 0800 or email [email protected]
Kind Regards
Octotel Noc
Octotel: Open Access Fibre Networks
Click to expand...
 
DrJohnZoidberg said:
I posted this in the RocketNet thread but this one is more active.

Does anyone know exactly what Octotel is referring to by "node maintenance" - I sure hope it means they're fixing things.
Click to expand...
When Frogfoot did maintenance in my area, my single threaded speeds went from 5Mbps to line speeds. Here's hoping Octotel does the same for you guys!
 
No mention of Kenilworth. Does the Rondebosch node service surrounding areas too or are we still screwed?
 
Slow connection to SAIX/Ububtu mirror.... on top of the problems you have to Hurricane Electric tunnel server which you seem to ignore, you also have issues with traffic to SAIX, the MTR above suggests traffic bounces CPT-JNB-CPT-Europe-CPT, most likely on the return route

Code: 
$ httping ubuntu.saix.net
PING ubuntu.saix.net:80 (/):
connected to 196.43.2.109:80 (242 bytes), seq=0 time=333.69 ms
connected to 196.43.2.109:80 (242 bytes), seq=1 time=330.15 ms
connected to 196.43.2.109:80 (242 bytes), seq=2 time=330.08 ms
connected to 196.43.2.109:80 (242 bytes), seq=3 time=330.15 ms
connected to 196.43.2.109:80 (242 bytes), seq=4 time=330.11 ms
connected to 196.43.2.109:80 (242 bytes), seq=5 time=330.39 ms
connected to 196.43.2.109:80 (242 bytes), seq=6 time=330.11 ms
connected to 196.43.2.109:80 (242 bytes), seq=7 time=330.13 ms
connected to 196.43.2.109:80 (242 bytes), seq=8 time=330.15 ms
connected to 196.43.2.109:80 (242 bytes), seq=9 time=350.17 ms
connected to 196.43.2.109:80 (242 bytes), seq=10 time=330.36 ms
connected to 196.43.2.109:80 (242 bytes), seq=11 time=330.25 ms
Got signal 2
--- http://ubuntu.saix.net/ ping statistics ---
12 connects, 12 ok, 0.00% failed, time 15799ms
round-trip min/avg/max = 330.1/332.1/350.2 ms


Code: 
 Host                                                              Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 155.93.234.1                                                    0.0%   157    5.9   7.1   1.9  47.0   6.5
 2. 155.93.240.25                                                   0.0%   157    7.4   4.6   0.5  71.4   9.2
 3. 154.0.4.161                                                     0.0%   157    0.8   1.4   0.6  18.7   2.3
 4. wc-grwf-ars1-vl1701.enetworks.net                               0.0%   157    1.7   1.3   0.8  18.0   1.6
 5. wc-grwf-cr2-gi0-0-2-3202.enetworks.net                          0.0%   157    1.4   1.3   0.6  17.0   2.0
 6. wc-trce-cr2-gi0-0-4-3209.enetworks.net                          0.0%   157    1.1   1.9   1.0  20.8   2.5
 7. wc-trce-br1-gi0-2-3205.enetworks.net                            0.0%   157    1.6   2.8   1.1 162.2  12.9
 8. 196.34.14.193                                                   0.0%   157   17.9  19.8  17.6  78.8   6.2
 9. 168.209.6.130                                                   0.0%   157   17.8  20.3  17.8  53.9   6.0
10. 196-10-140-228.ixp.capetown                                     0.0%   157   18.6  20.7  18.4  89.9   8.5
11. rrba-ip-hsll-1-gig-7-0-0.telkom-ipnet.co.za                     0.0%   157  176.6 181.2 176.3 404.6  19.3
12. rrba-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za                 0.0%   156  185.3 181.7 176.4 231.0   7.6
13. rrba-ip-dlr-11-3a.saix.net                                      0.0%   156  179.9 184.6 179.2 225.5   9.5
 
ipv6_warrior said:
Slow connection to SAIX/Ububtu mirror.... on top of the problems you have to Hurricane Electric tunnel server which you seem to ignore, you also have issues with traffic to SAIX, the MTR above suggests traffic bounces CPT-JNB-CPT-Europe-CPT, most likely on the return route

Code: 
$ httping ubuntu.saix.net
PING ubuntu.saix.net:80 (/):
connected to 196.43.2.109:80 (242 bytes), seq=0 time=333.69 ms
connected to 196.43.2.109:80 (242 bytes), seq=1 time=330.15 ms
connected to 196.43.2.109:80 (242 bytes), seq=2 time=330.08 ms
connected to 196.43.2.109:80 (242 bytes), seq=3 time=330.15 ms
connected to 196.43.2.109:80 (242 bytes), seq=4 time=330.11 ms
connected to 196.43.2.109:80 (242 bytes), seq=5 time=330.39 ms
connected to 196.43.2.109:80 (242 bytes), seq=6 time=330.11 ms
connected to 196.43.2.109:80 (242 bytes), seq=7 time=330.13 ms
connected to 196.43.2.109:80 (242 bytes), seq=8 time=330.15 ms
connected to 196.43.2.109:80 (242 bytes), seq=9 time=350.17 ms
connected to 196.43.2.109:80 (242 bytes), seq=10 time=330.36 ms
connected to 196.43.2.109:80 (242 bytes), seq=11 time=330.25 ms
Got signal 2
--- http://ubuntu.saix.net/ ping statistics ---
12 connects, 12 ok, 0.00% failed, time 15799ms
round-trip min/avg/max = 330.1/332.1/350.2 ms


Code: 
 Host Loss% Snt Last Avg Best Wrst StDev
1. 155.93.234.1 0.0% 157 5.9 7.1 1.9 47.0 6.5
2. 155.93.240.25 0.0% 157 7.4 4.6 0.5 71.4 9.2
3. 154.0.4.161 0.0% 157 0.8 1.4 0.6 18.7 2.3
4. wc-grwf-ars1-vl1701.enetworks.net 0.0% 157 1.7 1.3 0.8 18.0 1.6
5. wc-grwf-cr2-gi0-0-2-3202.enetworks.net 0.0% 157 1.4 1.3 0.6 17.0 2.0
6. wc-trce-cr2-gi0-0-4-3209.enetworks.net 0.0% 157 1.1 1.9 1.0 20.8 2.5
7. wc-trce-br1-gi0-2-3205.enetworks.net 0.0% 157 1.6 2.8 1.1 162.2 12.9
8. 196.34.14.193 0.0% 157 17.9 19.8 17.6 78.8 6.2
9. 168.209.6.130 0.0% 157 17.8 20.3 17.8 53.9 6.0
10. 196-10-140-228.ixp.capetown 0.0% 157 18.6 20.7 18.4 89.9 8.5
11. rrba-ip-hsll-1-gig-7-0-0.telkom-ipnet.co.za 0.0% 157 176.6 181.2 176.3 404.6 19.3
12. rrba-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za 0.0% 156 185.3 181.7 176.4 231.0 7.6
13. rrba-ip-dlr-11-3a.saix.net 0.0% 156 179.9 184.6 179.2 225.5 9.5
Click to expand...
I'll have a look at the SAIX side for you, the enetworks portion is falling away soon.
 
DrJohnZoidberg said:
I posted this in the RocketNet thread but this one is more active.

Does anyone know exactly what Octotel is referring to by "node maintenance" - I sure hope it means they're fixing things.
Click to expand...
Not sure, we get told the same thing. We have asked for feedback on a couple occasions and are still awaiting a response.
 
The 10/2 thing on the Vumatel portal should be sorted and we are awaiting Vumatel with regards to the 1Gbps service.
 
This is getting ridiculous, what am I supposed to do with this line speed...





C:\Users\main>C:\Users\main\Desktop\iperf-3.1.3-win64\iperf3.exe iperf3 --verbose --port 17001 -c queen.cisp.co.za --bandwidth 18M -l 1400 --omit 2 -R -u
iperf 3.1.3
CYGWIN_NT-10.0 EDWARD-PC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Mon, 04 Mar 2019 17:31:36 GMT
Connecting to host queen.cisp.co.za, port 17001
Reverse mode, remote host queen.cisp.co.za is sending
Cookie: EDWARD-PC.1551720695.739760.4e9fb6ba
[ 4] local 192.168.0.104 port 57478 connected to 62.233.65.195 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.12 MBytes 17.8 Mbits/sec 0.555 ms 82/1670 (4.9%) (omitted)
[ 4] 1.00-2.00 sec 2.04 MBytes 17.1 Mbits/sec 0.449 ms 79/1606 (4.9%) (omitted)
[ 4] 0.00-1.00 sec 1.98 MBytes 16.6 Mbits/sec 0.456 ms 130/1610 (8.1%)
[ 4] 1.00-2.00 sec 2.02 MBytes 16.9 Mbits/sec 0.458 ms 91/1604 (5.7%)
[ 4] 2.00-3.00 sec 1.99 MBytes 16.7 Mbits/sec 0.553 ms 120/1611 (7.4%)
[ 4] 3.00-4.00 sec 2.04 MBytes 17.1 Mbits/sec 0.523 ms 87/1613 (5.4%)
[ 4] 4.00-5.00 sec 1.93 MBytes 16.2 Mbits/sec 0.381 ms 153/1599 (9.6%)
[ 4] 5.00-6.00 sec 1.93 MBytes 16.2 Mbits/sec 0.557 ms 160/1607 (10%)
[ 4] 6.00-7.00 sec 2.03 MBytes 17.1 Mbits/sec 0.451 ms 84/1608 (5.2%)
[ 4] 7.00-8.00 sec 2.00 MBytes 16.8 Mbits/sec 0.457 ms 107/1607 (6.7%)
[ 4] 8.00-9.00 sec 2.03 MBytes 17.0 Mbits/sec 0.398 ms 86/1607 (5.4%)
[ 4] 9.00-10.00 sec 2.01 MBytes 16.8 Mbits/sec 0.518 ms 102/1605 (6.4%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 22.0 MBytes 18.4 Mbits/sec 0.556 ms 1128/16390 (6.9%)
[ 4] Sent 16390 datagrams
CPU Utilization: local/receiver 4.6% (1.5%u/3.2%s), remote/sender 3.2% (0.5%u/2.7%s)

iperf Done.
 
TranQ said:
This is getting ridiculous, what am I supposed to do with this line speed...





C:\Users\main>C:\Users\main\Desktop\iperf-3.1.3-win64\iperf3.exe iperf3 --verbose --port 17001 -c queen.cisp.co.za --bandwidth 18M -l 1400 --omit 2 -R -u
iperf 3.1.3
CYGWIN_NT-10.0 EDWARD-PC 2.5.1(0.297/5/3) 2016-04-21 22:14 x86_64
Time: Mon, 04 Mar 2019 17:31:36 GMT
Connecting to host queen.cisp.co.za, port 17001
Reverse mode, remote host queen.cisp.co.za is sending
Cookie: EDWARD-PC.1551720695.739760.4e9fb6ba
[ 4] local 192.168.0.104 port 57478 connected to 62.233.65.195 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.12 MBytes 17.8 Mbits/sec 0.555 ms 82/1670 (4.9%) (omitted)
[ 4] 1.00-2.00 sec 2.04 MBytes 17.1 Mbits/sec 0.449 ms 79/1606 (4.9%) (omitted)
[ 4] 0.00-1.00 sec 1.98 MBytes 16.6 Mbits/sec 0.456 ms 130/1610 (8.1%)
[ 4] 1.00-2.00 sec 2.02 MBytes 16.9 Mbits/sec 0.458 ms 91/1604 (5.7%)
[ 4] 2.00-3.00 sec 1.99 MBytes 16.7 Mbits/sec 0.553 ms 120/1611 (7.4%)
[ 4] 3.00-4.00 sec 2.04 MBytes 17.1 Mbits/sec 0.523 ms 87/1613 (5.4%)
[ 4] 4.00-5.00 sec 1.93 MBytes 16.2 Mbits/sec 0.381 ms 153/1599 (9.6%)
[ 4] 5.00-6.00 sec 1.93 MBytes 16.2 Mbits/sec 0.557 ms 160/1607 (10%)
[ 4] 6.00-7.00 sec 2.03 MBytes 17.1 Mbits/sec 0.451 ms 84/1608 (5.2%)
[ 4] 7.00-8.00 sec 2.00 MBytes 16.8 Mbits/sec 0.457 ms 107/1607 (6.7%)
[ 4] 8.00-9.00 sec 2.03 MBytes 17.0 Mbits/sec 0.398 ms 86/1607 (5.4%)
[ 4] 9.00-10.00 sec 2.01 MBytes 16.8 Mbits/sec 0.518 ms 102/1605 (6.4%)
- - - - - - - - - - - - - - - - - - - - - - - - -
Test Complete. Summary Results:
[ ID] Interval Transfer Bandwidth Jitter Lost/Total Datagrams
[ 4] 0.00-10.00 sec 22.0 MBytes 18.4 Mbits/sec 0.556 ms 1128/16390 (6.9%)
[ 4] Sent 16390 datagrams
CPU Utilization: local/receiver 4.6% (1.5%u/3.2%s), remote/sender 3.2% (0.5%u/2.7%s)

iperf Done.
Click to expand...
Not at all it just takes a lot of time depending on the fibre provider, as you can see as per a ton of the recent posts this is becoming a common issue.
 
PBCool said:
Not at all it just takes a lot of time depending on the fibre provider, as you can see as per a ton of the recent posts this is becoming a common issue.
Click to expand...
Well it's my fourth month sitting with this kind of line performance, that is one third of a full year. I can't do anything, the line has been getting worse and worse every week.

I was getting my hopes up on Friday when the proxy was giving me a decent experience when watching international streams but it doesn't help when the local speed is as bad as this.

Look I appreciate you guys trying to get this resolved but it is highly frustrating when I'm paying a lot of money for a service that doesn't work, more so when there is no feedback and not having any idea of what is being done about it.

I expect there to be some kind of progress within a period of four months, I don't think that is an unreasonable expectation?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X