Cool Ideas Fibre ISP – Feedback Thread 2

John Tempus

Expert Member
Joined
Aug 8, 2017
Messages
2,487
Not London, JHB-CPT. Still asleep it seems.
My ping from CPT->JHB seems fine.

The issue or was at time of my previous thread comment between CPT->EU and CPT->USA east particulary in this example.

Right now the US East ping is much lower from previous 335ms down to 237ms so much more usable but still curious where the 215ms flat went but less concerned now seeing that its at least not over 300ms anymore.

My main concern is that now its during the day and it seems to be better until we get to around 8pm then suddenly the international ping shoots up to the 335ms route.
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
6,419
My ping from CPT->JHB seems fine.

The issue or was at time of my previous thread comment between CPT->EU and CPT->USA east particulary in this example.

Right now the US East ping is much lower from previous 335ms down to 237ms so much more usable but still curious where the 215ms flat went but less concerned now seeing that its at least not over 300ms anymore.

My main concern is that now its during the day and it seems to be better until we get to around 8pm then suddenly the international ping shoots up to the 335ms route.
Yes but the increased latency is due to packets travelling to JHB first then back to you, but as mentioned that should be resolved as of yesterday. Post a trace if you see it again, or PM me the IP in question?
 

John Tempus

Expert Member
Joined
Aug 8, 2017
Messages
2,487
Yes but the increased latency is due to packets travelling to JHB first then back to you, but as mentioned that should be resolved as of yesterday. Post a trace if you see it again, or PM me the IP in question?
Did it always route from CPT->JHB->EU / USA ? If this is new then that would explain why there is extra 22ms added to the USA route right now from the ideal 215ms before to 237ms now. It would also explain why the EU ping went up from 145ms to 167ms now also 22ms difference.

I will pm you my mtr to my server in US East. I don't recall the previous routes with the 215ms final ping.
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
6,419
Did it always route from CPT->JHB->EU / USA ? If this is new then that would explain why there is extra 22ms added to the USA route right now from the ideal 215ms before to 237ms now. It would also explain why the EU ping went up from 145ms to 167ms now also 22ms difference.
No the default route out of CPT has always been, CPT-London-EU/USA, if you have the server IP for me I can do some more granular tests.
 

blunt

Expert Member
Joined
May 1, 2006
Messages
2,336
beacon seems fine from here (despite the crappy pings), second one same as yours

Code:
Start: Wed May 22 12:23:18 2019
HOST: debian.ibox.za.net                       Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.ibox.za.net (10.23.23.1)           0.0%    10    1.4   1.5   1.0   1.9   0.0
  2.|-- u33m-cust.coolideas.co.za (154.0.15.178) 40.0%    10    4.1   4.2   3.6   5.8   0.6
  3.|-- u33l-cust.coolideas.co.za (154.0.15.177)  0.0%    10    3.8   4.1   3.7   4.6   0.0
  4.|-- enetworks.ixp.capetown (196.10.140.139)   0.0%    10   22.8  55.9  22.2 262.2  77.5
  5.|-- beacon.enetworks.net (45.220.128.9)       0.0%    10   23.0  23.6  22.7  26.4   0.9

Start: Wed May 22 12:23:50 2019
HOST: debian.ibox.za.net                                      Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.ibox.za.net (10.23.23.1)                          0.0%    10    0.9   1.2   0.9   1.7   0.0
  2.|-- u33m-cust.coolideas.co.za (154.0.15.178)                60.0%    10    3.7   3.8   3.4   4.3   0.0
  3.|-- u33l-cust.coolideas.co.za (154.0.15.177)                 0.0%    10    5.6   4.4   3.3   5.6   0.5
  4.|-- c1l-backbone.coolideas.co.za (154.0.2.57)                0.0%    10    5.0   4.7   3.6   8.8   1.5
  5.|-- 196.26.90.82                                             0.0%    10    5.4   5.6   4.4   7.9   0.8
  6.|-- mi-za-cpt-p8-te0-7-0-0.ip.isnet.net (168.209.2.13)       0.0%    10    6.1   6.9   4.9  16.9   3.5
  7.|-- mi-za-cpt-p7-te-0-0-1-1-141.ip.isnet.net (168.209.0.69)  0.0%    10   21.2  21.2  20.7  22.5   0.3
  8.|-- pr2-pkl-xe-2-2-0.ip.isnet.net (168.209.1.179)            0.0%    10   20.3  20.5  19.8  21.4   0.3
  9.|-- telkom-internet.ixp.joburg (196.60.8.241)                0.0%    10   23.0  23.8  22.6  27.8   1.2
 10.|-- 105-187-234-94.telkomsa.net (105.187.234.94)             0.0%    10   24.2  26.5  24.2  39.1   4.4
 11.|-- 105-187-234-94.telkomsa.net (105.187.234.94)             0.0%    10   23.8  24.4  23.7  25.2   0.0
 12.|-- ipc-aggr-2.north.telkomsa.net (105.228.0.14)             0.0%    10   24.1  24.6  24.1  25.5   0.0
 13.|-- ???                                                     100.0    10    0.0   0.0   0.0   0.0   0.0
 14.|-- wwg-ip-bb-1.south.dsl.telkomsa.net (105.184.160.1)      30.0%    10  7513. 7337. 7164. 7513. 128.4
 15.|-- ???                                                     100.0    10    0.0   0.0   0.0   0.0   0.0
 

Tinuva

The Magician
Joined
Feb 10, 2005
Messages
8,650
I did check now? The IS transit thing to SAIX is still an ongoing thing.
Yeah I know the SAIX one is separate, but that trace is to TelkomSA-ISP which is different, you should be able to peer with them on NapAfrica settlement free.
 

Tinuva

The Magician
Joined
Feb 10, 2005
Messages
8,650
beacon seems fine from here (despite the crappy pings), second one same as yours

Code:
Start: Wed May 22 12:23:18 2019
HOST: debian.ibox.za.net                       Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.ibox.za.net (10.23.23.1)           0.0%    10    1.4   1.5   1.0   1.9   0.0
  2.|-- u33m-cust.coolideas.co.za (154.0.15.178) 40.0%    10    4.1   4.2   3.6   5.8   0.6
  3.|-- u33l-cust.coolideas.co.za (154.0.15.177)  0.0%    10    3.8   4.1   3.7   4.6   0.0
  4.|-- enetworks.ixp.capetown (196.10.140.139)   0.0%    10   22.8  55.9  22.2 262.2  77.5
  5.|-- beacon.enetworks.net (45.220.128.9)       0.0%    10   23.0  23.6  22.7  26.4   0.9

Start: Wed May 22 12:23:50 2019
HOST: debian.ibox.za.net                                      Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- router.ibox.za.net (10.23.23.1)                          0.0%    10    0.9   1.2   0.9   1.7   0.0
  2.|-- u33m-cust.coolideas.co.za (154.0.15.178)                60.0%    10    3.7   3.8   3.4   4.3   0.0
  3.|-- u33l-cust.coolideas.co.za (154.0.15.177)                 0.0%    10    5.6   4.4   3.3   5.6   0.5
  4.|-- c1l-backbone.coolideas.co.za (154.0.2.57)                0.0%    10    5.0   4.7   3.6   8.8   1.5
  5.|-- 196.26.90.82                                             0.0%    10    5.4   5.6   4.4   7.9   0.8
  6.|-- mi-za-cpt-p8-te0-7-0-0.ip.isnet.net (168.209.2.13)       0.0%    10    6.1   6.9   4.9  16.9   3.5
  7.|-- mi-za-cpt-p7-te-0-0-1-1-141.ip.isnet.net (168.209.0.69)  0.0%    10   21.2  21.2  20.7  22.5   0.3
  8.|-- pr2-pkl-xe-2-2-0.ip.isnet.net (168.209.1.179)            0.0%    10   20.3  20.5  19.8  21.4   0.3
  9.|-- telkom-internet.ixp.joburg (196.60.8.241)                0.0%    10   23.0  23.8  22.6  27.8   1.2
10.|-- 105-187-234-94.telkomsa.net (105.187.234.94)             0.0%    10   24.2  26.5  24.2  39.1   4.4
11.|-- 105-187-234-94.telkomsa.net (105.187.234.94)             0.0%    10   23.8  24.4  23.7  25.2   0.0
12.|-- ipc-aggr-2.north.telkomsa.net (105.228.0.14)             0.0%    10   24.1  24.6  24.1  25.5   0.0
13.|-- ???                                                     100.0    10    0.0   0.0   0.0   0.0   0.0
14.|-- wwg-ip-bb-1.south.dsl.telkomsa.net (105.184.160.1)      30.0%    10  7513. 7337. 7164. 7513. 128.4
15.|-- ???                                                     100.0    10    0.0   0.0   0.0   0.0   0.0
Strange, if you look at the Smokeping history, beacon used to be very low latency, as in in CPT. Perhaps it routes back wrong for now.
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
6,419
Yeah I know the SAIX one is separate, but that trace is to TelkomSA-ISP which is different, you should be able to peer with them on NapAfrica settlement free.
Strange, if you look at the Smokeping history, beacon used to be very low latency, as in in CPT. Perhaps it routes back wrong for now.
It seems like they are using anycast, if we trace from JHB then the host is in KZN.
Yeah I know the SAIX one is separate, but that trace is to TelkomSA-ISP which is different, you should be able to peer with them on NapAfrica settlement free.
It's more around what they are accepting as prefixes, as they peer with the RS' at Teraco. I have dropped them a mail in the meantime. re eNetworks it looks like it's an anycast address, and since dropping our transit with them we have since peered. I have tried to selectively announce regionally to them, let me know if it improves.
 

Charmingmage10

Well-Known Member
Joined
Aug 6, 2015
Messages
194
It seems like they are using anycast, if we trace from JHB then the host is in KZN.

It's more around what they are accepting as prefixes, as they peer with the RS' at Teraco. I have dropped them a mail in the meantime. re eNetworks it looks like it's an anycast address, and since dropping our transit with them we have since peered. I have tried to selectively announce regionally to them, let me know if it improves.
when are you guys enabling IPC for KZN?
 

DeatheCore

Well-Known Member
Joined
Dec 4, 2006
Messages
434
@PBCool What are the chances that Vumatel's CPT upgrades will solve my slow international throughput due to packetloss? I've been told by support that there's no point in opening a ticket with Vumatel until their upgrades are complete as they often close these types of tickets without asking for further information or tests.

I have had great correspondence from Gumani from your support team :thumbsup: but as mentioned, I've been dealing with these issues on a daily basis for months and I'm no closer to any sort of solution. No requests to monitor the line, Vuma tickets, anything.

It's becoming increasingly more frustrating as time goes on... now I have to simply wait until mid-June when Vuma hopefully complete their upgrades in the hopes it'll magically fix my line.

Plus this upcoming Vumatel upgrade is not the first one in CPT that I've hoped will solve these issues and didn't help at all, see: https://coolzone.cisp.co.za/index.php?rp=/announcements/1185/Vumatel-Maintenance--Bothasig-Monte-Vista-Panorama-Parow-North-Boston-and-Tygerdal-.html

Is there no way to isolate the fault to my actual line, or Vuma PoP backhaul, etc?
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
6,419
@PBCool What are the chances that Vumatel's CPT upgrades will solve my slow international throughput due to packetloss? I've been told by support that there's no point in opening a ticket with Vumatel until their upgrades are complete as they often close these types of tickets without asking for further information or tests.

I have had great correspondence from Gumani from your support team :thumbsup: but as mentioned, I've been dealing with these issues on a daily basis for months and I'm no closer to any sort of solution. No requests to monitor the line, Vuma tickets, anything.

It's becoming increasingly more frustrating as time goes on... now I have to simply wait until mid-June when Vuma hopefully complete their upgrades in the hopes it'll magically fix my line.

Plus this upcoming Vumatel upgrade is not the first one in CPT that I've hoped will solve these issues and didn't help at all, see: https://coolzone.cisp.co.za/index.php?rp=/announcements/1185/Vumatel-Maintenance--Bothasig-Monte-Vista-Panorama-Parow-North-Boston-and-Tygerdal-.html

Is there no way to isolate the fault to my actual line, or Vuma PoP backhaul, etc?
It's usually backhaul or cisco license limitation, device limitation etc. And we can log tickets with Vumatel all they will check is levels on your line then close the ticket. So the short answer is basically we need to wait for the changes then take it from there.
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
6,419
@PBCool What are the chances that Vumatel's CPT upgrades will solve my slow international throughput due to packetloss? I've been told by support that there's no point in opening a ticket with Vumatel until their upgrades are complete as they often close these types of tickets without asking for further information or tests.

I have had great correspondence from Gumani from your support team :thumbsup: but as mentioned, I've been dealing with these issues on a daily basis for months and I'm no closer to any sort of solution. No requests to monitor the line, Vuma tickets, anything.

It's becoming increasingly more frustrating as time goes on... now I have to simply wait until mid-June when Vuma hopefully complete their upgrades in the hopes it'll magically fix my line.

Plus this upcoming Vumatel upgrade is not the first one in CPT that I've hoped will solve these issues and didn't help at all, see: https://coolzone.cisp.co.za/index.php?rp=/announcements/1185/Vumatel-Maintenance--Bothasig-Monte-Vista-Panorama-Parow-North-Boston-and-Tygerdal-.html

Is there no way to isolate the fault to my actual line, or Vuma PoP backhaul, etc?
Also which area are you in?
 

DeatheCore

Well-Known Member
Joined
Dec 4, 2006
Messages
434
It's usually backhaul or cisco license limitation, device limitation etc. And we can log tickets with Vumatel all they will check is levels on your line then close the ticket. So the short answer is basically we need to wait for the changes then take it from there.
Also which area are you in?
Ahh okay :( Guess that I'm just going to have to be more patient until then. Vuma trenched in Panorama, Cape Town.
 

PBCool

Cool Ideas
Company Rep
Joined
Jan 11, 2016
Messages
6,419
Ahh okay :( Guess that I'm just going to have to be more patient until then. Vuma trenched in Panorama, Cape Town.
Can you PM me your IP?

On the 11th of June 2019 at 00:05 we will be moving the following PoPs from master node Capetown1 to master node Capetown4:


Edenpark
Vredekloof
Stellenberg
La-Rochelle
Oakdale
Protea Heights East
Protea Heights West
Kuilsrivier North
Kuilsrivier South
Boston
Northpine
 

DeatheCore

Well-Known Member
Joined
Dec 4, 2006
Messages
434
Can you PM me your IP?

On the 11th of June 2019 at 00:05 we will be moving the following PoPs from master node Capetown1 to master node Capetown4:


Edenpark
Vredekloof
Stellenberg
La-Rochelle
Oakdale
Protea Heights East
Protea Heights West
Kuilsrivier North
Kuilsrivier South
Boston
Northpine
PM'd you my IP.

My area is not on that list, although I'm not sure where my PoP is actually located.
 

blunt

Expert Member
Joined
May 1, 2006
Messages
2,336
@PBCool any reason why our IP's have no reverse dns / hostnames? Avoiding successful spam deliveries?
 

Tinuva

The Magician
Joined
Feb 10, 2005
Messages
8,650
Can you PM me your IP?

On the 11th of June 2019 at 00:05 we will be moving the following PoPs from master node Capetown1 to master node Capetown4:


Edenpark
Vredekloof
Stellenberg
La-Rochelle
Oakdale
Protea Heights East
Protea Heights West
Kuilsrivier North
Kuilsrivier South
Boston
Northpine
Hmm wasn't aware my area (PoP) had issues, but good to know it will also get moved.
 
Top