Cool Ideas Fibre ISP - Feedback

Status
Not open for further replies.
Scoperzor said:
Mine is still down this morning after going down same time as yours, Wed afternoon. I was told by CI that I cannot escalate the issue with MFN because it's "still within the 24-48hr turnaround time". Why in this day and age do I need to wait 2 days for someone to acknowledge the issue and provide feedback on how it is being attended to :/

Edit: Apparently my link was never down after getting the logs from MFN, only that my router details were now incorrect. Would have checked those previously if I wasn't told it was a problem with the link.
Click to expand...

How does your router details change on its own? Or did they change the spec and then need you to make a change?
 
remoten said:
Yep mines been down since 9am ish.
Click to expand...

This is madness.

MFN will have to pay for my bill for the down time as I wont pay for a service that is not been provided.

I reported to CI and was told they will get back to me about 2 hours ago.
Thy have not done so with me updating the ticket with them twice in this 2 hours and also now holding for them as I type this.
 
We asked MFN around an outage and they aren't aware of it, but clearly there is something wrong.
 
LevanM said:
This is madness.

MFN will have to pay for my bill for the down time as I wont pay for a service that is not been provided.

I reported to CI and was told they will get back to me about 2 hours ago.
Thy have not done so with me updating the ticket with them twice in this 2 hours and also now holding for them as I type this.
Click to expand...
Have these links recovered as yet?
 
Installation process went very smoothly. Currently waiting on "ISP activation". Vumatel aerial here.

Do I have to contact Cool Ideas with regard to that and for the router?
 
Vernon said:
Installation process went very smoothly. Currently waiting on "ISP activation". Vumatel aerial here.

Do I have to contact Cool Ideas with regard to that and for the router?
Click to expand...
You can let connect know, drop them a mail. [email protected] but as the status changes we get the notice.
 
A question with regard to connection settings on the router.

PPPoE or DHCP?
I believe on Vumatel aerial (as opposed to trenched Vumatel) the setup is with a PPPoE username and password. Is that right?
 
Vernon said:
A question with regard to connection settings on the router.

PPPoE or DHCP?
I believe on Vumatel aerial (as opposed to trenched Vumatel) the setup is with a PPPoE username and password. Is that right?
Click to expand...
Yeap that's correct.
 
What would cause the below?

Ping has started…



PING tiz-cycling.racing (104.27.150.191): 56 data bytes

64 bytes from 104.27.150.191: icmp_seq=0 ttl=57 time=34.291 ms

64 bytes from 104.27.150.191: icmp_seq=1 ttl=57 time=71.166 ms

64 bytes from 104.27.150.191: icmp_seq=2 ttl=57 time=118.661 ms

64 bytes from 104.27.150.191: icmp_seq=3 ttl=57 time=170.228 ms

64 bytes from 104.27.150.191: icmp_seq=4 ttl=57 time=214.356 ms

64 bytes from 104.27.150.191: icmp_seq=5 ttl=57 time=262.934 ms

64 bytes from 104.27.150.191: icmp_seq=6 ttl=57 time=310.129 ms

64 bytes from 104.27.150.191: icmp_seq=7 ttl=57 time=8.101 ms

64 bytes from 104.27.150.191: icmp_seq=8 ttl=57 time=5.957 ms

64 bytes from 104.27.150.191: icmp_seq=9 ttl=57 time=5.822 ms

64 bytes from 104.27.150.191: icmp_seq=10 ttl=57 time=5.093 ms

64 bytes from 104.27.150.191: icmp_seq=11 ttl=57 time=28.125 ms

64 bytes from 104.27.150.191: icmp_seq=12 ttl=57 time=63.983 ms

64 bytes from 104.27.150.191: icmp_seq=13 ttl=57 time=117.183 ms

64 bytes from 104.27.150.191: icmp_seq=14 ttl=57 time=152.644 ms

64 bytes from 104.27.150.191: icmp_seq=15 ttl=57 time=198.180 ms

64 bytes from 104.27.150.191: icmp_seq=16 ttl=57 time=240.786 ms

64 bytes from 104.27.150.191: icmp_seq=17 ttl=57 time=299.998 ms

64 bytes from 104.27.150.191: icmp_seq=18 ttl=57 time=5.698 ms

64 bytes from 104.27.150.191: icmp_seq=19 ttl=57 time=4.903 ms

64 bytes from 104.27.150.191: icmp_seq=20 ttl=57 time=5.150 ms

64 bytes from 104.27.150.191: icmp_seq=21 ttl=57 time=7.551 ms

64 bytes from 104.27.150.191: icmp_seq=22 ttl=57 time=8.452 ms

64 bytes from 104.27.150.191: icmp_seq=23 ttl=57 time=39.319 ms

64 bytes from 104.27.150.191: icmp_seq=24 ttl=57 time=88.041 ms

64 bytes from 104.27.150.191: icmp_seq=25 ttl=57 time=134.442 ms

64 bytes from 104.27.150.191: icmp_seq=26 ttl=57 time=185.086 ms

64 bytes from 104.27.150.191: icmp_seq=27 ttl=57 time=230.373 ms

64 bytes from 104.27.150.191: icmp_seq=28 ttl=57 time=272.638 ms

64 bytes from 104.27.150.191: icmp_seq=29 ttl=57 time=5.178 ms

64 bytes from 104.27.150.191: icmp_seq=30 ttl=57 time=5.095 ms

64 bytes from 104.27.150.191: icmp_seq=31 ttl=57 time=5.339 ms

64 bytes from 104.27.150.191: icmp_seq=32 ttl=57 time=7.083 ms

64 bytes from 104.27.150.191: icmp_seq=33 ttl=57 time=5.898 ms

64 bytes from 104.27.150.191: icmp_seq=34 ttl=57 time=25.584 ms

64 bytes from 104.27.150.191: icmp_seq=35 ttl=57 time=94.713 ms

64 bytes from 104.27.150.191: icmp_seq=36 ttl=57 time=119.998 ms

64 bytes from 104.27.150.191: icmp_seq=37 ttl=57 time=168.872 ms

64 bytes from 104.27.150.191: icmp_seq=38 ttl=57 time=216.477 ms

64 bytes from 104.27.150.191: icmp_seq=39 ttl=57 time=261.832 ms

64 bytes from 104.27.150.191: icmp_seq=40 ttl=57 time=305.192 ms

64 bytes from 104.27.150.191: icmp_seq=41 ttl=57 time=4.527 ms

64 bytes from 104.27.150.191: icmp_seq=42 ttl=57 time=5.148 ms

64 bytes from 104.27.150.191: icmp_seq=43 ttl=57 time=5.517 ms

64 bytes from 104.27.150.191: icmp_seq=44 ttl=57 time=4.828 ms

64 bytes from 104.27.150.191: icmp_seq=45 ttl=57 time=18.928 ms

64 bytes from 104.27.150.191: icmp_seq=46 ttl=57 time=64.230 ms

64 bytes from 104.27.150.191: icmp_seq=47 ttl=57 time=110.278 ms

64 bytes from 104.27.150.191: icmp_seq=48 ttl=57 time=156.113 ms

64 bytes from 104.27.150.191: icmp_seq=49 ttl=57 time=202.244 ms



--- tiz-cycling.racing ping statistics ---

50 packets transmitted, 50 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 4.527/101.647/310.129/100.580 ms
 
Furbz said:
What would cause the below?

Ping has started…



PING tiz-cycling.racing (104.27.150.191): 56 data bytes

64 bytes from 104.27.150.191: icmp_seq=0 ttl=57 time=34.291 ms

64 bytes from 104.27.150.191: icmp_seq=1 ttl=57 time=71.166 ms

64 bytes from 104.27.150.191: icmp_seq=2 ttl=57 time=118.661 ms

64 bytes from 104.27.150.191: icmp_seq=3 ttl=57 time=170.228 ms

64 bytes from 104.27.150.191: icmp_seq=4 ttl=57 time=214.356 ms

64 bytes from 104.27.150.191: icmp_seq=5 ttl=57 time=262.934 ms

64 bytes from 104.27.150.191: icmp_seq=6 ttl=57 time=310.129 ms

64 bytes from 104.27.150.191: icmp_seq=7 ttl=57 time=8.101 ms

64 bytes from 104.27.150.191: icmp_seq=8 ttl=57 time=5.957 ms

64 bytes from 104.27.150.191: icmp_seq=9 ttl=57 time=5.822 ms

64 bytes from 104.27.150.191: icmp_seq=10 ttl=57 time=5.093 ms

64 bytes from 104.27.150.191: icmp_seq=11 ttl=57 time=28.125 ms

64 bytes from 104.27.150.191: icmp_seq=12 ttl=57 time=63.983 ms

64 bytes from 104.27.150.191: icmp_seq=13 ttl=57 time=117.183 ms

64 bytes from 104.27.150.191: icmp_seq=14 ttl=57 time=152.644 ms

64 bytes from 104.27.150.191: icmp_seq=15 ttl=57 time=198.180 ms

64 bytes from 104.27.150.191: icmp_seq=16 ttl=57 time=240.786 ms

64 bytes from 104.27.150.191: icmp_seq=17 ttl=57 time=299.998 ms

64 bytes from 104.27.150.191: icmp_seq=18 ttl=57 time=5.698 ms

64 bytes from 104.27.150.191: icmp_seq=19 ttl=57 time=4.903 ms

64 bytes from 104.27.150.191: icmp_seq=20 ttl=57 time=5.150 ms

64 bytes from 104.27.150.191: icmp_seq=21 ttl=57 time=7.551 ms

64 bytes from 104.27.150.191: icmp_seq=22 ttl=57 time=8.452 ms

64 bytes from 104.27.150.191: icmp_seq=23 ttl=57 time=39.319 ms

64 bytes from 104.27.150.191: icmp_seq=24 ttl=57 time=88.041 ms

64 bytes from 104.27.150.191: icmp_seq=25 ttl=57 time=134.442 ms

64 bytes from 104.27.150.191: icmp_seq=26 ttl=57 time=185.086 ms

64 bytes from 104.27.150.191: icmp_seq=27 ttl=57 time=230.373 ms

64 bytes from 104.27.150.191: icmp_seq=28 ttl=57 time=272.638 ms

64 bytes from 104.27.150.191: icmp_seq=29 ttl=57 time=5.178 ms

64 bytes from 104.27.150.191: icmp_seq=30 ttl=57 time=5.095 ms

64 bytes from 104.27.150.191: icmp_seq=31 ttl=57 time=5.339 ms

64 bytes from 104.27.150.191: icmp_seq=32 ttl=57 time=7.083 ms

64 bytes from 104.27.150.191: icmp_seq=33 ttl=57 time=5.898 ms

64 bytes from 104.27.150.191: icmp_seq=34 ttl=57 time=25.584 ms

64 bytes from 104.27.150.191: icmp_seq=35 ttl=57 time=94.713 ms

64 bytes from 104.27.150.191: icmp_seq=36 ttl=57 time=119.998 ms

64 bytes from 104.27.150.191: icmp_seq=37 ttl=57 time=168.872 ms

64 bytes from 104.27.150.191: icmp_seq=38 ttl=57 time=216.477 ms

64 bytes from 104.27.150.191: icmp_seq=39 ttl=57 time=261.832 ms

64 bytes from 104.27.150.191: icmp_seq=40 ttl=57 time=305.192 ms

64 bytes from 104.27.150.191: icmp_seq=41 ttl=57 time=4.527 ms

64 bytes from 104.27.150.191: icmp_seq=42 ttl=57 time=5.148 ms

64 bytes from 104.27.150.191: icmp_seq=43 ttl=57 time=5.517 ms

64 bytes from 104.27.150.191: icmp_seq=44 ttl=57 time=4.828 ms

64 bytes from 104.27.150.191: icmp_seq=45 ttl=57 time=18.928 ms

64 bytes from 104.27.150.191: icmp_seq=46 ttl=57 time=64.230 ms

64 bytes from 104.27.150.191: icmp_seq=47 ttl=57 time=110.278 ms

64 bytes from 104.27.150.191: icmp_seq=48 ttl=57 time=156.113 ms

64 bytes from 104.27.150.191: icmp_seq=49 ttl=57 time=202.244 ms



--- tiz-cycling.racing ping statistics ---

50 packets transmitted, 50 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 4.527/101.647/310.129/100.580 ms
Click to expand...
What does an MTR look like? Looks like ecmp one local path one international. So traffic flips between each.
 
@PBCool Openserve installing Fibre today at my place, got Cell C LTE through Axxess as I was told that fibre would only be live in 2 months. Will you guys activate the fibre now or would you be able to wait until 1 October?
 
Koosie said:
@PBCool Openserve installing Fibre today at my place, got Cell C LTE through Axxess as I was told that fibre would only be live in 2 months. Will you guys activate the fibre now or would you be able to wait until 1 October?
Click to expand...
We would need to start billing on installation as billing for the line starts from OS the same time.
 
Was there an internation issue just now? Could barely do screen share with MS Teams. Internation downloads was also struggling at 300Kb/s.
All of a sudden it's back to normal again.
 
If I choose Cool Ideas as ISP, how long does it take to have the fibre installed/activated/router delivered in a apartment complex where the fibre lines is pre-installed in each unit? Actually, I am not the sure if the fibre has been taken to each unit, but there is a duct at least, not too sure of the logistics. But it should just be hauling of the fibre worst case.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X