Cool Ideas Fibre ISP - Feedback

[DrJohnZoidberg]

Seems Vuma has a lot of issues. Only had one issue so far with Octotel and they came to fix it without me even reporting anything.

 

[Arno4Jackie]

so we are on a old segment in Radiokop and surrounding areas?

 

[Yster21]

It's still happening, just less frequently. Also don't understand why we are on a legacy VLAN?

 

[CRE4MPIE]

Our fibre went in 3-4 months ago and had NO issues - now this crap ! I can't see how we're on a legacy VLAN ?

Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=191ms TTL=59
Reply from 154.0.13.95: bytes=32 time=15ms TTL=59
Reply from 154.0.13.95: bytes=32 time=18ms TTL=59
Reply from 154.0.13.95: bytes=32 time=6ms TTL=59
Reply from 154.0.13.95: bytes=32 time=4ms TTL=59
Reply from 154.0.13.95: bytes=32 time=4ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=4ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=5ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=4ms TTL=59
Reply from 154.0.13.95: bytes=32 time=5ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 154.0.13.95: bytes=32 time=7ms TTL=59
Reply from 154.0.13.95: bytes=32 time=13ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=11ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=7ms TTL=59
Reply from 154.0.13.95: bytes=32 time=25ms TTL=59
Reply from 154.0.13.95: bytes=32 time=4ms TTL=59
Reply from 154.0.13.95: bytes=32 time=11ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=5ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=6ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Request timed out.
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=1ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59

 

[Arno4Jackie]

our area is connecting to a legacy vlan. They probably havn't had time to move us over yet

 

[Yster21]

Wobbledy wobbledy

 

[rvanwyk]

Still issues. Vuma Aerial Wilgeheuwel

 

[mystic007]

I am also still experiencing packet loss. Vuma Aerial Ferndale. Is Ferndale on the legacy VLAN too?

 

[stiller26]

Third night with this issue

 

[aucampia]

Nope it should be resolved for now.

It was better last night but the problem is back again now and it actually seems allot worse tonight (Vumatel Aerial in Morningside, Johannesburg):

$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 ubnt000 (10.154.160.11) 0.351 ms 0.326 ms 0.327 ms
2 155.93.141.1 (155.93.141.1) 2.341 ms 2.394 ms 2.320 ms
3 c4x-backbone.coolideas.co.za (154.0.1.177) 3.247 ms 2.684 ms 2.626 ms
4 ci-backbone.coolideas.co.za (154.0.1.18) 3.431 ms 3.478 ms 3.524 ms
5 c3a-backbone.coolideas.co.za (154.0.2.118) 3.587 ms 3.683 ms 3.625 ms
6 154.0.4.42 (154.0.4.42) 4.202 ms 154.0.4.46 (154.0.4.46) 2.585 ms 2.575 ms
7 154.0.2.37 (154.0.2.37) 2.890 ms 2.705 ms 2.768 ms
8 google.ixp.joburg (196.60.8.166) 5.278 ms 5.340 ms 5.095 ms
9 72.14.239.33 (72.14.239.33) 3.261 ms 72.14.239.117 (72.14.239.117) 7.898 ms 7.899 ms
10 google-public-dns-a.google.com (8.8.8.8) 3.345 ms 2.512 ms 2.987 ms


--- 8.8.8.8 ping statistics ---
193 packets transmitted, 97 received, 49% packet loss, time 192435ms
rtt min/avg/max/mdev = 1.382/2.933/12.460/1.730 ms

--- 8.8.8.8 ping statistics ---
443 packets transmitted, 250 received, 43% packet loss, time 442758ms
rtt min/avg/max/mdev = 1.368/3.282/32.363/2.593 ms


--- 154.0.1.177 ping statistics ---
192 packets transmitted, 99 received, 48% packet loss, time 191727ms
rtt min/avg/max/mdev = 0.862/2.795/21.586/3.026 ms

--- 154.0.1.177 ping statistics ---
441 packets transmitted, 260 received, 41% packet loss, time 441511ms
rtt min/avg/max/mdev = 0.915/3.011/74.056/5.793 ms


--- 155.93.141.1 ping statistics ---
191 packets transmitted, 191 received, 0% packet loss, time 190286ms
rtt min/avg/max/mdev = 0.925/1.948/15.977/1.604 ms

--- 155.93.141.1 ping statistics ---
442 packets transmitted, 442 received, 0% packet loss, time 441657ms
rtt min/avg/max/mdev = 0.733/1.992/15.431/1.414 ms

 

[PBCool]

We have narrowed down something just working through the issue.

 

[mugikhan]

Okay so I recommended three of my family friends to get cool ideas and now they’re all having problems constantly. I guess it’s time I tell them to move with me to a better ISP.
One that will actually deliver and not increase prices while offering a subpar service! First packet loss and now intermittent connectivity, what a joke.
I’m extremely disappointed since I look like a fool for picking cool ideas as the isp for them.
@PBCool come next month I will leave and move on to better service delivery.

 

[Kloon]

Seems Vuma has a lot of issues. Only had one issue so far with Octotel and they came to fix it without me even reporting anything.

I am on Vumatel trenched and have not had a single issue since being live. The arial network I believe was a company they bought a while back and seem to be where the majority of issues are experienced.

 

[stiller26]

Okay so I recommended three of my family friends to get cool ideas and now they’re all having problems constantly. I guess it’s time I tell them to move with me to a better ISP.
One that will actually deliver and not increase prices while offering a subpar service! First packet loss and now intermittent connectivity, what a joke.
I’m extremely disappointed since I look like a fool for picking cool ideas as the isp for them.
@PBCool come next month I will leave and move on to better service delivery.

Is this a Coolideas or Vumatel issue?

 

[rvanwyk]

I am on Vumatel trenched and have not had a single issue since being live. The arial network I believe was a company they bought a while back and seem to be where the majority of issues are experienced.

Yeah, Fibrehoods

 

[CRE4MPIE]

Yeah, Fibrehoods

I would guess all ISPS using the Vuma Aerial network are affected. Some people seem to think not and that this is CISP only clients that are having issues.

 

[titeroper]

Can confirm:Vuma aeriel here in Waverley,JHB and internet very wobbly this evening...will log a ticket.
Miss the Crystal Web network email notifications to be honest...those were pretty useful.

 

[mugikhan]

Is this a Coolideas or Vumatel issue?

Definitely a cool ideas only, a friend of mine who lives a street down from me on mweb has no problems!

 

[mugikhan]

I would guess all ISPS using the Vuma Aerial network are affected. Some people seem to think not and that this is CISP only clients that are having issues.

Nope you would be wrong. Definitely a cool ideas issue.

 

[rvanwyk]

Any update @PBCool ?