Cool Ideas Fibre ISP – Feedback Thread 3

Status
Not open for further replies.
Will you let support know?
That trace is fine ironically.

Just got home and it seems to be working again :) will monitor it thanks

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms RT-AC1200G+-64A8 [192.168.1.1]
2 2 ms 2 ms 2 ms nnpd-cust.coolideas.co.za [102.132.248.1]
3 1 ms 1 ms 1 ms n9d9-cust.coolideas.co.za [102.132.175.109]
4 1 ms 1 ms 1 ms ump-cust.coolideas.co.za [154.0.3.49]
5 1 ms 1 ms 1 ms 100.98.0.4
6 2 ms 2 ms 1 ms cloudflare.ixp.capetown [196.60.70.198]
7 1 ms 1 ms 1 ms one.one.one.one [1.1.1.1]
 
I'm just curious what causes it. Congestion?
Nope could be a change in backhaul etc, that sort of variance is well within the normal operating levels of a PON network.
 
The thing with cables to different locations over the world, it only works well if you keep your peers and transit providers consistent over the globe and the reason for this is, it keeps routing simpler and more efficient.
/bgp
 
The thing with cables to different locations over the world, it only works well if you keep your peers and transit providers consistent over the globe and the reason for this is, it keeps routing simpler and more efficient.
/bgp
Yerp, even so on the transit front we tried this with London, Sao Paulo and New York with HE, we still had asymmetry with certain routes. The only effective and persistent method we have seen is direct peering.
 
Having latency issues in Cape Town on Openserve at the moment. 5ms to 192.168.10.5 (not internal, not sure where exactly), and 105+ms thereafter. Any ideas of what's up? :)

Code:
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
 1  d-link (10.0.0.2)  3.021 ms  2.403 ms  2.055 ms
 2  * * *
 3  192.168.10.5 (192.168.10.5)  8.220 ms  9.764 ms  7.815 ms
 4  192.168.11.6 (192.168.11.6)  100.282 ms  80.245 ms  60.516 ms
 5  100.98.0.1 (100.98.0.1)  69.504 ms  56.578 ms  76.029 ms
 6  100.98.0.4 (100.98.0.4)  73.761 ms  85.396 ms  102.497 ms
 7  cloudflare.ixp.capetown (196.60.70.198)  111.373 ms  103.244 ms  102.527 ms
 8  one.one.one.one (1.1.1.1)  111.948 ms  107.807 ms  113.457 ms
 
Having latency issues in Cape Town on Openserve at the moment. 5ms to 192.168.10.5 (not internal, not sure where exactly), and 105+ms thereafter. Any ideas of what's up? :)

Code:
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
1  d-link (10.0.0.2)  3.021 ms  2.403 ms  2.055 ms
2  * * *
3  192.168.10.5 (192.168.10.5)  8.220 ms  9.764 ms  7.815 ms
4  192.168.11.6 (192.168.11.6)  100.282 ms  80.245 ms  60.516 ms
5  100.98.0.1 (100.98.0.1)  69.504 ms  56.578 ms  76.029 ms
6  100.98.0.4 (100.98.0.4)  73.761 ms  85.396 ms  102.497 ms
7  cloudflare.ixp.capetown (196.60.70.198)  111.373 ms  103.244 ms  102.527 ms
8  one.one.one.one (1.1.1.1)  111.948 ms  107.807 ms  113.457 ms

Must be an Openserve issue.

EDIT: your own router is inducing 2 - 3ms latency, check it, something not well on it.

Vuma trenched, Brackenfell, CPT.

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            192.168.88.1 -    0 |   19 |   19 |    0 |    0 |    0 |    0 |
|                            155.93.237.1 -    0 |   19 |   19 |    2 |    2 |   14 |    2 |
|                          102.132.175.34 -    0 |   19 |   19 |    2 |    2 |    6 |    3 |
|                         102.132.175.113 -    0 |   19 |   19 |    0 |    0 |    1 |    1 |
|                              100.98.0.2 -    0 |   19 |   19 |    0 |    0 |    1 |    1 |
|                              100.98.0.4 -    0 |   19 |   19 |    0 |    0 |    1 |    1 |
|                           196.60.70.198 -    0 |   19 |   19 |    1 |    3 |   21 |    2 |
|                                 1.1.1.1 -    0 |   19 |   19 |    1 |    1 |    1 |    1 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Having latency issues in Cape Town on Openserve at the moment. 5ms to 192.168.10.5 (not internal, not sure where exactly), and 105+ms thereafter. Any ideas of what's up? :)

Code:
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
1  d-link (10.0.0.2)  3.021 ms  2.403 ms  2.055 ms
2  * * *
3  192.168.10.5 (192.168.10.5)  8.220 ms  9.764 ms  7.815 ms
4  192.168.11.6 (192.168.11.6)  100.282 ms  80.245 ms  60.516 ms
5  100.98.0.1 (100.98.0.1)  69.504 ms  56.578 ms  76.029 ms
6  100.98.0.4 (100.98.0.4)  73.761 ms  85.396 ms  102.497 ms
7  cloudflare.ixp.capetown (196.60.70.198)  111.373 ms  103.244 ms  102.527 ms
8  one.one.one.one (1.1.1.1)  111.948 ms  107.807 ms  113.457 ms
Try reboot everything if you have not, had a friend who had similar issue in PTA last night, rebooted and everything went back to normal
 
What is the model of the "free router" included?

Would it be advisable to just use my own (does have a WAN port)
 
Seems to be resolved now... guessing Vuma/SADV will never get reasons.. anyway thanks for the help.
I'll be back next month when the line drops again ...

sigh, as predicated ... link is down.

ticket number: #COOL-20200716-474679

description:
All lights are on and steady on the ONT.
651 error when connecting directly to ONT. happens every so often

Entire complex is down - Bedfordview area , usually if there are issue in Senderwood JHB they effect us.

FNO = SADV / Vumatel.

@PBCool @TheRoDent please help escalate this ...

At the time of the post - I could not see any related outages on the announcement page ...



***Update: seems to be okay now - but not sure if stable...? Please still investigate?

Issue started around 10:50

Jul 16 10:50 WAN Connection: Fail to connect with some issues.
Jul 16 10:52 pppd[448]: Timeout waiting for PADO packets
Jul 16 10:53 pppd[448]: Timeout waiting for PADO packets
...
Jul 16 11:05 WAN Connection: WAN was restored
...
Jul 16 11:12 WAN Connection: Fail to connect with some issues.
...
Jul 16 11:13 WAN Connection: WAN was restored.

Regards.
 
Last edited:
Must be an Openserve issue.

EDIT: your own router is inducing 2 - 3ms latency, check it, something not well on it.

Vuma trenched, Brackenfell, CPT.

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            192.168.88.1 -    0 |   19 |   19 |    0 |    0 |    0 |    0 |
|                            155.93.237.1 -    0 |   19 |   19 |    2 |    2 |   14 |    2 |
|                          102.132.175.34 -    0 |   19 |   19 |    2 |    2 |    6 |    3 |
|                         102.132.175.113 -    0 |   19 |   19 |    0 |    0 |    1 |    1 |
|                              100.98.0.2 -    0 |   19 |   19 |    0 |    0 |    1 |    1 |
|                              100.98.0.4 -    0 |   19 |   19 |    0 |    0 |    1 |    1 |
|                           196.60.70.198 -    0 |   19 |   19 |    1 |    3 |   21 |    2 |
|                                 1.1.1.1 -    0 |   19 |   19 |    1 |    1 |    1 |    1 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Thanks! Yeah, I was on Wifi for that link, hence the router latency. However eth has the same issue. I have a feeling that openserve peering is currently crying somewhere down the link. However, seems to be restoring slowly. Thanks, though!
 
What is the model of the "free router" included?

Would it be advisable to just use my own (does have a WAN port)
Which package are you signing up for?
 
Thanks! Yeah, I was on Wifi for that link, hence the router latency. However eth has the same issue. I have a feeling that openserve peering is currently crying somewhere down the link. However, seems to be restoring slowly. Thanks, though!
That hop is between OS and ourselves, so possibly a backhaul related issue with OS.
 
@PBCool

Please assist, I've been complaining about random disconnects that last between 5 and 10 minutes. It started roughly three months ago. I tend to experience bad paclet loss and then it disconnects, it reconnects and then the packet loss is gone but returns again after a while. I need this to be escalated so that it can receive attention and be fixed.

COOL-20200611-452892
 
@PBCool

Please assist, I've been complaining about random disconnects that last between 5 and 10 minutes. It started roughly three months ago. I tend to experience bad paclet loss and then it disconnects, it reconnects and then the packet loss is gone but returns again after a while. I need this to be escalated so that it can receive attention and be fixed.

COOL-20200611-452892
Sure will look into it for you.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X