Cool Ideas Fibre ISP - Feedback

TheRoDent · Apr 1, 2019

I get a timeout. Here are the results:

Code:

ping netbank.nedsecure.co.za

Pinging netbank.nedsecure.co.za [168.142.204.33] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 154.72.97.213: Destination net unreachable.
Request timed out.

Ping statistics for 168.142.204.33:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss)
   
----------

ping www.scottshipping.co.za

Pinging www.scottshipping.co.za [197.242.151.196] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 154.72.97.213: Destination net unreachable.
Request timed out.

Ping statistics for 197.242.151.196:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss)
   
----------

ping 154.0.1.1

Pinging 154.0.1.1 with 32 bytes of data:
Reply from 154.0.1.1: bytes=32 time=5ms TTL=59
Reply from 154.0.1.1: bytes=32 time=4ms TTL=59
Reply from 154.0.1.1: bytes=32 time=5ms TTL=59
Reply from 154.0.1.1: bytes=32 time=4ms TTL=59

Ping statistics for 154.0.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 5ms, Average = 4ms
   
------------

nslookup netbank.nedsecure.co.za 154.0.1.1
Server:  cdns1.cisp.co.za
Address:  154.0.1.1

Non-authoritative answer:
Name:    netbank.nedsecure.co.za
Address:  168.142.204.33

And if using 1.1.1.1 as a DNS, with the same tests? Please PM me your current IP, or account details, this doesn't seem right at all. It should all resolve to the same IP's generally regardless of the DNS you are using....

Phinix · Apr 1, 2019

TheRoDent said:
And if using 1.1.1.1 as a DNS, with the same tests? Please PM me your current IP, or account details, this doesn't seem right at all. It should all resolve to the same IP's generally regardless of the DNS you are using....

PM sent.
Tests with 1.1.1.1

Code:

ping netbank.nedsecure.co.za

Pinging netbank.nedsecure.co.za [168.142.204.33] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 168.142.204.33:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

-----------

ping www.scottshipping.co.za

Pinging www.scottshipping.co.za [197.242.151.196] with 32 bytes of data:
Reply from 197.242.151.196: bytes=32 time=22ms TTL=54
Reply from 197.242.151.196: bytes=32 time=21ms TTL=54
Reply from 197.242.151.196: bytes=32 time=23ms TTL=54
Reply from 197.242.151.196: bytes=32 time=22ms TTL=54

Ping statistics for 197.242.151.196:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 23ms, Average = 22ms

------------

ping 154.0.1.1

Pinging 154.0.1.1 with 32 bytes of data:
Reply from 154.0.1.1: bytes=32 time=5ms TTL=59
Reply from 154.0.1.1: bytes=32 time=4ms TTL=59
Reply from 154.0.1.1: bytes=32 time=3ms TTL=59
Reply from 154.0.1.1: bytes=32 time=5ms TTL=59

Ping statistics for 154.0.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 5ms, Average = 4ms
  
------------

ping 1.1.1.1

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=4ms TTL=56
Reply from 1.1.1.1: bytes=32 time=3ms TTL=56
Reply from 1.1.1.1: bytes=32 time=5ms TTL=56
Reply from 1.1.1.1: bytes=32 time=4ms TTL=56

Ping statistics for 1.1.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 5ms, Average = 4ms

------------

nslookup netbank.nedsecure.co.za 154.0.1.1
Server:  cdns1.cisp.co.za
Address:  154.0.1.1

Non-authoritative answer:
Name:    netbank.nedsecure.co.za
Address:  168.142.204.33

------------

nslookup netbank.nedsecure.co.za 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    netbank.nedsecure.co.za
Address:  168.142.204.33

TheRoDent · Apr 1, 2019

Phinix said:

PM sent.
Tests with 1.1.1.1

Code:

ping netbank.nedsecure.co.za

Pinging netbank.nedsecure.co.za [168.142.204.33] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 168.142.204.33:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

-----------

ping www.scottshipping.co.za

Pinging www.scottshipping.co.za [197.242.151.196] with 32 bytes of data:
Reply from 197.242.151.196: bytes=32 time=22ms TTL=54
Reply from 197.242.151.196: bytes=32 time=21ms TTL=54
Reply from 197.242.151.196: bytes=32 time=23ms TTL=54
Reply from 197.242.151.196: bytes=32 time=22ms TTL=54

Ping statistics for 197.242.151.196:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 23ms, Average = 22ms

------------

ping 154.0.1.1

Pinging 154.0.1.1 with 32 bytes of data:
Reply from 154.0.1.1: bytes=32 time=5ms TTL=59
Reply from 154.0.1.1: bytes=32 time=4ms TTL=59
Reply from 154.0.1.1: bytes=32 time=3ms TTL=59
Reply from 154.0.1.1: bytes=32 time=5ms TTL=59

Ping statistics for 154.0.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 5ms, Average = 4ms
 
------------

ping 1.1.1.1

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=4ms TTL=56
Reply from 1.1.1.1: bytes=32 time=3ms TTL=56
Reply from 1.1.1.1: bytes=32 time=5ms TTL=56
Reply from 1.1.1.1: bytes=32 time=4ms TTL=56

Ping statistics for 1.1.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 5ms, Average = 4ms

------------

nslookup netbank.nedsecure.co.za 154.0.1.1
Server:  cdns1.cisp.co.za
Address:  154.0.1.1

Non-authoritative answer:
Name:    netbank.nedsecure.co.za
Address:  168.142.204.33

------------

nslookup netbank.nedsecure.co.za 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    netbank.nedsecure.co.za
Address:  168.142.204.33

netbank.nedsecure.co.za wil always time out, they filter ICMP packets as a rule.

duanesf · Apr 1, 2019

Happy to report that I could play on local servers without any issues this evening - first time in 2 weeks!

Thanks for the help, CISP team!

CRE4MPIE · Apr 2, 2019

Jammed some RoE and Streamed for about 3 hours - no issues whatsoever ! Thank you @PBCool @CoolChick @TheRoDent. All seems to be back to normal !

On that note - mate of mine moved over to the 1000/100 package - speeds are BLAZING , even international :O

Guess I can't get that package on aerial ? What other differences are there between that an my 200/200 besides the obvious ?

Thanks
CP

Snoopster0303 · Apr 2, 2019

CRE4MPIE said:
Jammed some RoE and Streamed for about 3 hours - no issues whatsoever ! Thank you @PBCool @CoolChick @TheRoDent. All seems to be back to normal !

On that note - mate of mine moved over to the 1000/100 package - speeds are BLAZING , even international :O

Guess I can't get that package on aerial ? What other differences are there between that an my 200/200 besides the obvious ?

Thanks
CP

I see 1000/100 on Afrihost for Vuma Aerial

https://www.afrihost.com/fibre/provider/vuma-aerial#

Snoopster0303 · Apr 2, 2019

Current speed in Mount Edgecombe on Vumatel.

Connection is stable again, thanks for sorting the issues out Cool Ideas.

Fcon_Vpro · Apr 2, 2019

Did anyone else have disconnects through the night?
Im on SADV in Fourways/Lonehill.

Wasp_21 · Apr 2, 2019

Have been having disconnects from online gaming over the last 2 days. In Durban, Openserve, 10/5 Cool ideas. Anyone know if there are issues? Also Netflix is streaming poorly.

stroebs · Apr 2, 2019

Couldn't be bothered anymore actually. Cancelled with Cool Ideas yesterday due to them blocking websites, or not knowing how to route traffic to MTN and IS.

Traffic being filtered by eNetworks routers upstream from them and they say "Telkom is blocking your traffic". Wish someone technical would get involved and give an actual explanation. Oh well. Cheers Cool Ideas.

Jordan_Za · Apr 2, 2019

Wasp_21 said:
Have been having disconnects from online gaming over the last 2 days. In Durban, Openserve, 10/5 Cool ideas. Anyone know if there are issues? Also Netflix is streaming poorly.

Something is weird in Durban. Evenings are shocking for me (17:00 to 22:00). During the day, I'm getting ~80mbps to JHB test servers. Pings, Traces, MTRs show no losses (all day). but come night time... no speed.

You're on Openserve and having issues, my mate on Openserve in Hillcrest says no problems at all. Snoopster up there is Mt Edgecome (must be trenched if 1gbps) and getting what appears to be decent throughput.
I'm Vuma Aerial, in Kloof, having issues... maybe we all need 1Gbps lines to get actual 100Mbps at night?

VegOtter · Apr 2, 2019

Snoopster0303 said:
View attachment 640686

Current speed in Mount Edgecombe on Vumatel.

Connection is stable again, thanks for sorting the issues out Cool Ideas.

I cannot wrap my head around the reality of having those kinds of speeds at home.

VegOtter · Apr 2, 2019

Wasp_21 said:
Have been having disconnects from online gaming over the last 2 days. In Durban, Openserve, 10/5 Cool ideas. Anyone know if there are issues? Also Netflix is streaming poorly.

I'm on OpenServe with CellC Fibre and can confirm I was having issues last night too. High latency in games and was struggling to maintain constant stream.

Think it might have been Durban OpenServe issue.

EDIT: It was fine as of this morning though. So not sure if it is peak time congestion or something else.

CoolChick · Apr 2, 2019

stroebs said:
Couldn't be bothered anymore actually. Cancelled with Cool Ideas yesterday due to them blocking websites, or not knowing how to route traffic to MTN and IS.

Traffic being filtered by eNetworks routers upstream from them and they say "Telkom is blocking your traffic". Wish someone technical would get involved and give an actual explanation. Oh well. Cheers Cool Ideas.

Hi @stroebs , I have replied to your ticket and have spoken to the network engineers at Cool Ideas to investigate. They are currently looking into it.

Sargeant · Apr 2, 2019

@PBCool
Can you please follow up on ticket #COOL-20190120-204693. It was opened on 20 January and I was told on 14 February it is being referred to "senior technicians whey (sic) will investigate and resolve". No word since and now it seems the ticket has just been closed. Really have not been happy with the support from CISP!

CoolChick · Apr 2, 2019

Sargeant said:
@PBCool
Can you please follow up on ticket #COOL-20190120-204693. It was opened on 20 January and I was told on 14 February it is being referred to "senior technicians whey (sic) will investigate and resolve". No word since and now it seems the ticket has just been closed. Really have not been happy with the support from CISP!

Hi @Sargeant - sincere apologies for this. I am following up on your query with the relevant tech who has been dealing with your ticket. I will be sure to have a tech revert back to you with their findings.

SNaidoo · Apr 2, 2019

@CoolChick , please see my PM and revert.

CoolChick · Apr 2, 2019

SNaidoo said:
@CoolChick , please see my PM and revert.

i have reverted back to you via pm

derp90 · Apr 2, 2019

PBCool said:
I got it, connect will have to try claim your B number tomorrow morning. Is your line in the holding pool?

Any updates? Still no response from support.

Orihalcon · Apr 2, 2019

Seems to be all cleared for me at least.

First hiccup I've had with CISP. It happens.

Cool Ideas Fibre ISP - Feedback

Cool Ideas Rep

Expert Member

Cool Ideas Rep

Active Member

Well-Known Member

Active Member

Active Member

Expert Member

Expert Member

Expert Member

Attachments

Well-Known Member

Senior Member

Senior Member

Cool Ideas Rep

Active Member

Cool Ideas Rep

Active Member

Cool Ideas Rep

Senior Member

Expert Member