Fulcrum29
Honorary Master
I don't know how true this may be, but rumour has it that there is contractor/supplier delays. It is also worth noting that they have several issues at this time. Flooding, vandalism, etc.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: If you were buying a TV today, which brand would you choose?
Cool Ideas Fibre ISP – Feedback Thread 6
- Thread starter CoolEscalator
- Start date
- Joined
- Aug 14, 2018
- Messages
- 660
- Reaction score
- 294
Good day All,
We sincerely apologise for the inconvenience caused.
Should you still have an issue, please send us a private message with your details and we will further assist.
Thank you.
We sincerely apologise for the inconvenience caused.
Should you still have an issue, please send us a private message with your details and we will further assist.
Thank you.
How about you put a proper status up.
HI all, apologies for the delay.
There has been a few outages for Frogfoot in the Western and Eastern Cape today.
For majority of customers in WC/EC
I know they say ISP specific here, however I have confirmation that this affected other ISP's as well
More details on the cause will be shared should FF provide more details.
Services does seem stable since around 15:00-15:35pm
For clients in Milnerton
Franschhoek
There was also an outage in PLZ Summerstrand which was resolved
There has been a few outages for Frogfoot in the Western and Eastern Cape today.
For majority of customers in WC/EC
I know they say ISP specific here, however I have confirmation that this affected other ISP's as well
More details on the cause will be shared should FF provide more details.
Services does seem stable since around 15:00-15:35pm
Code:
Outage Title: Outage | WC & EC | Cool Ideas | Intermittent
Details: ISP Specific
Outage Ref(solid): FRG13161479
Impact Start Time: 2026-05-16 05:45:00
Impact: Intermittent
Latest Update: We have identified a network outage affecting clients in the Eastern Cape and Western Cape area. Our advanced support team has been informed to identify the cause of the impact.For clients in Milnerton
Code:
Outage Update
Outage Title: Outage | CPT | Milpark | Intermittent
Details: Node
Outage Ref(solid): FRG13159250
Impact Start Time: 2026-05-16 06:36:00
Impact: Intermittent
Latest Update: Our Frogfoot Maintenance Team has arrived on site to investigate and found that the equipment is faulty on site. Team is currently organizing stock.
Outage History:
2026-05-16
-- 15:36 -- Our initial checks have been completed, and a fault has been logged with our Advanced Support Team to investigate the cause of the impact.
-- 16:08 -- Our Advanced Support Team has advised that they suspect the issue to be on our fibre service providers side and a fault has been logged with our fibre service provider to investigate the incident on site.Franschhoek
Code:
Outage Update
Outage Title: Outage | CPT | Franschhoek | Partial
Details: OLT2 | LC2 | PON8
Outage Ref(solid): FRG13160792
Impact Start Time: 2026-05-16 11:16:36
Impact: Hard Down
Latest Update: Our Frogfoot Maintenance technician is en route to investigate the outage onsite.
Outage History:
2026-05-16
-- 17:23 -- We have identified a network outage affecting the Franschhoek area. Our Frogfoot maintenance team has been notified to identify the cause of the impact.There was also an outage in PLZ Summerstrand which was resolved
Code:
Outage Resolved
Outage Title: Outage | PLZ | Summerstrand | Node | Down | Change Overrun FRG12843598
Details: Node
Outage Ref(solid): FRG13152213
Impact Start Time: 2026-05-16 07:00:00
Impact Stop Time: 2026-05-16 10:58:00
Impact: Hard Down
Final Update: The outage has been resolved, and services are restored. Continuous monitoring remains in place to ensure sustained stability across your links.
Outage History:
2026-05-16
-- 07:53 -- Our initial checks have been completed, and the fault was logged with our fibre service provider maintenance team to investigate the incident on site.
-- 09:00 -- Our fibre service provider maintenance team has arrived onsite.lightpixel
Well-Known Member
- Joined
- Jun 15, 2019
- Messages
- 423
- Reaction score
- 189
My ISP Atomic is not giving me any updates so I hope you don't mind if I tag along. This is the only update thread. Thanks for the update.
AsianSpaceman
Well-Known Member
- Joined
- May 9, 2019
- Messages
- 299
- Reaction score
- 103
Kind of sounds like you know which ISP you should move to lolMy ISP Atomic is not giving me any updates so I hope you don't mind if I tag along. This is the only update thread. Thanks for the update.
Welcome welcomeMy ISP Atomic is not giving me any updates so I hope you don't mind if I tag along. This is the only update thread. Thanks for the update.
WC/EC has been resolved
Code:
Outage History:
2026-05-16
-- 17:59 -- We have identified a network outage affecting clients in the Eastern Cape and Western Cape area. Our advanced support team has been informed to identify the cause of the impact.
-- 20:30 -- The outage has been resolved, and all affected services are now being monitored for stability.Milnerton update:
Code:
Outage History:
2026-05-16
-- 15:36 -- Our initial checks have been completed, and a fault has been logged with our Advanced Support Team to investigate the cause of the impact.
-- 16:08 -- Our Advanced Support Team has advised that they suspect the issue to be on our fibre service providers side and a fault has been logged with our fibre service provider to investigate the incident on site.
-- 18:35 -- Our Frogfoot Maintenance Team has arrived on site to investigate and found that the equipment is faulty on site. Team is currently organizing stock.
-- 20:54 -- Our Frogfoot Maintenance Team has advised that tech has been granted after hours access and is enroute to collect stock from stores.
Best to log a ticket man. They can't really do much without knowing who you are. Looks more like your fibre is intermittent than anything else
ripclaw
Expert Member
- Joined
- Dec 4, 2006
- Messages
- 1,238
- Reaction score
- 160
Good morning, @CoolEscalator
My issue was temporarily resolved on Saturday morning but it's reared its head again this morning. I've logged #COOL-20260518-2673439.
HI there, Vuma is actually outside your premises at the moment, are you able to open up for them?
But yes I see the system closed the ticket, No worries I have opened it again
ripclaw
Expert Member
- Joined
- Dec 4, 2006
- Messages
- 1,238
- Reaction score
- 160
Thanks, @CoolEscalator. I've opened up for Milton and his team. Long story short: they swapped me over to another port on the wall box on my boundary fence. Seems to be fine, for now.
Last edited:
Great, thank you for confirming
Please let us know should the Intermittency issue persist.
HI there, apologies for the delay and inconvenience, ae you still experiencing issues?
Hi @Brenvh @Chris_Auc @Nikaidoboss
Please note, MFN has confirmed the upgrade has been completed. Please let me know if you continue to experience any issues during peak time.
Please note, MFN has confirmed the upgrade has been completed. Please let me know if you continue to experience any issues during peak time.
CVRChameleon
Well-Known Member
Good day @CoolEscalator , I DM'd you the ticket I managed to create finally.
OpenServe network
#COOL-20260518-2674093
Please assist,
Thanks!
OpenServe network
#COOL-20260518-2674093
Please assist,
Thanks!
netstrider
Executive Member
- Joined
- Nov 1, 2006
- Messages
- 5,686
- Reaction score
- 4,774
Something up with the one of the core switches?
Code:
C:\Users\user>tracert speedtest.co.za
Tracing route to speedtest.co.za [41.203.16.67]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms OpenWrt.lan [192.168.7.30]
2 3 ms 2 ms 2 ms 100-100-101-61.loopback [100.100.101.61]
3 3 ms 3 ms 2 ms u21-cust.coolideas.co.za [154.0.0.73]
4 3 ms 2 ms 3 ms u2a-cust.coolideas.co.za [154.0.0.82]
5 4 ms 3 ms 4 ms 196-60-9-23.ixp.joburg [196.60.9.23]
6 7 ms 7 ms 12 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
7 4 ms 4 ms 4 ms dedi67.jnb2.host-h.net [41.203.16.67]
Trace complete.
C:\Users\user>ping -n 30 197.189.193.1
Pinging 197.189.193.1 with 32 bytes of data:
Reply from 197.189.193.1: bytes=32 time=8ms TTL=58
Reply from 197.189.193.1: bytes=32 time=10ms TTL=58
Reply from 197.189.193.1: bytes=32 time=20ms TTL=58
Reply from 197.189.193.1: bytes=32 time=4ms TTL=58
Reply from 197.189.193.1: bytes=32 time=5ms TTL=58
Reply from 197.189.193.1: bytes=32 time=12ms TTL=58
Reply from 197.189.193.1: bytes=32 time=11ms TTL=58
Reply from 197.189.193.1: bytes=32 time=4ms TTL=58
Reply from 197.189.193.1: bytes=32 time=5ms TTL=58
Reply from 197.189.193.1: bytes=32 time=11ms TTL=58
Reply from 197.189.193.1: bytes=32 time=8ms TTL=58
Reply from 197.189.193.1: bytes=32 time=25ms TTL=58
Reply from 197.189.193.1: bytes=32 time=44ms TTL=58
Reply from 197.189.193.1: bytes=32 time=16ms TTL=58
Reply from 197.189.193.1: bytes=32 time=8ms TTL=58
Reply from 197.189.193.1: bytes=32 time=6ms TTL=58
Reply from 197.189.193.1: bytes=32 time=9ms TTL=58
Reply from 197.189.193.1: bytes=32 time=44ms TTL=58
Reply from 197.189.193.1: bytes=32 time=40ms TTL=58
Reply from 197.189.193.1: bytes=32 time=5ms TTL=58
Reply from 197.189.193.1: bytes=32 time=5ms TTL=58
Reply from 197.189.193.1: bytes=32 time=7ms TTL=58
Reply from 197.189.193.1: bytes=32 time=6ms TTL=58
Reply from 197.189.193.1: bytes=32 time=12ms TTL=58
Reply from 197.189.193.1: bytes=32 time=8ms TTL=58
Reply from 197.189.193.1: bytes=32 time=4ms TTL=58
Reply from 197.189.193.1: bytes=32 time=15ms TTL=58
Reply from 197.189.193.1: bytes=32 time=6ms TTL=58
Reply from 197.189.193.1: bytes=32 time=4ms TTL=58
Reply from 197.189.193.1: bytes=32 time=6ms TTL=58
Ping statistics for 197.189.193.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 44ms, Average = 12msHI there, Nope that trace is clean, Since the latency doesn't carry to the destination hop
That would be ICMP rate limiting.