Cool Ideas Fibre ISP – Feedback Thread 6

netstrider said:
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 = 12ms
Click to expand...

That IP is also on Xneelo's network and not CISPs, so it would be under their control, there are a couple of threads and articles posted today that Xneelo are experiencing a DDoS attack, so not suprising that their routers & switches would deprioritize ICMP packets.
 
Last edited:
Jason-ZA said:
That IP is also on Xneelo's network and not CISPs, so it would be under their control, there are a couple of threads and articles posted today that Xneelo are experiencing a DDoS attack, so not suprising that their routers & switches would deprioritize ICMP packets.
Click to expand...
Yeah I am aware of the Xneelo issue. Wasn't sure whose switch it is.

Was asking because running a speedtest shows insane latency.
 
Hey @CoolEscalator, happy to report it looks like the packet loss is gone during peak time now. :) "touch wood."
Huge thanks for all your effort, & please pass along for everyone who helped :)

I'm going to monitor for a few days, then I will close the ticket.
 
Chris_Auc said:
Hey @CoolEscalator, happy to report it looks like the packet loss is gone during peak time now. :) "touch wood."
Huge thanks for all your effort, & please pass along for everyone who helped :)

I'm going to monitor for a few days, then I will close the ticket.
Click to expand...
Awesome I'm glad that that did the trick. Let me know if it continues :)
 
PBCool said:
So we are ready to deploy, Vumatel said they need to do it per vlan and cant mass deploy. So we have given them all the allocations. So we're just waiting on them.

But some is deployed, have you tried to enable on your router as yet?
Click to expand...
@PBCool any updates on IPv6 deployment on Vuma AE? Tried enabling again this morning without luck.
 
Hi there @CoolEscalator hope you are well.

Tonight, not a good night it seems, not sure what's happening on hop 3 but it's bad
1779302383581.png
1779302853595.png
 
Last edited:
KaboomZA said:
Hi there @CoolEscalator hope you are well.

Tonight, not a good night it seems, not sure what's happening on hop 3 but it's bad
View attachment 1909526
View attachment 1909528
Click to expand...
HI there, Thank you for reaching out.
Its only really an issue if the loss carries through to the end destination,
For both traces, one shows 0.5% and the other nothing on the last hop, - which would not cause you any noticeable impact at all.

From my monitoring in JHB, I don't see any issues towards international, apart from a 14ms latency increase between Lisbon and London, possibly due to an issue on the lower latency terrestrial path.

Can you show the timegraph as well?

1779303632439.png
 
CoolEscalator said:
HI there, Thank you for reaching out.
Its only really an issue if the loss carries through to the end destination,
For both traces, one shows 0.5% and the other nothing on the last hop, - which would not cause you any noticeable impact at all.

From my monitoring in JHB, I don't see any issues towards international, apart from a 14ms latency increase between Lisbon and London, possibly due to an issue on the lower latency terrestrial path.

Can you show the timegraph as well?

View attachment 1909534
Click to expand...
Thanks for the info

yeah here is the full capture, I typically sit at like 160ms to that destination, so slightly higher tonight
1779303953812.png
 
KaboomZA said:
Thanks for the info

yeah here is the full capture, I typically sit at like 160ms to that destination, so slightly higher tonight
View attachment 1909537
Click to expand...
Yeah this trace would be nothing to worry about, as the loss was not occurring for very long (a few seconds) and didn't continue.


What you should be looking for is something like this .Then it's a problem (aka: looks like a barcode)
1779304210591.png

Or something like this
1779304370690.png
 
Last edited:
I love metrofibre, been dead since early morningScreenshot 2026-05-23 093958.png
 

Attachments

  • Screenshot 2026-05-23 093921.png
    Screenshot 2026-05-23 093921.png
    42.8 KB · Views: 14
Is metrofibre down in Durban, Sydenham? No connectivity
 

Attachments

  • 20260523_111540.jpg
    20260523_111540.jpg
    124.3 KB · Views: 15
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X