Cool Ideas Fibre ISP - Feedback

[Fjorko]

Interestingly enough I'm not seeing the SACS routing at all - all of my traffic is flowing through the normal routes.
@PBCool did you disable the SACS routes?

Dont think its live yet ( I mean CISP isnt live on it yet )

 

[SeaSickMama]

Dont think its live yet ( I mean CISP isnt live on it yet )

Mine routed via the Angolacable when I tested it with the cloudflare dns. But since then I don’t think it’s working, although the way my dns is setup is very complicated

 

[PBCool]

We have disabled the SACS service for now whilst we strategize the implementation further.

 

[PBCool]

Don't really get these prices though..

https://www.cisp.co.za/ftth/openserve-residential/

R1499 for 100/50 with line.
R1219 for 100/50 no line.

So they're charging R280 for a 100mb fibre line?

Well no but it's a combined rate so it is always going to be more cost effective with the line included.

 

[PBCool]

Dont think its live yet ( I mean CISP isnt live on it yet )

We are

To Fortaleza:

Tracing route to 138-36-3-214.texnet.net.br [138.36.3.214]
over a maximum of 30 hops:

4 2 ms 2 ms 2 ms 154.0.3.114
5 24 ms 24 ms 24 ms 154.0.1.246
6 24 ms 31 ms 24 ms 154.0.4.162
7 23 ms 23 ms 25 ms 102.130.64.13
8 65 ms 57 ms 57 ms pe2-nc028.ang.sgn.as37468.angolacables.ao [197.149.151.194]
9 116 ms 116 ms 116 ms 170.238.232.145
10 124 ms 116 ms 124 ms pe1-nc013.br.ftz.as37468.angolacables.ao [170.238.232.81]
11 115 ms 115 ms 117 ms 170.238.235.18
12 116 ms 116 ms 117 ms 187.120.30.6.cliente.primelinelatam.com.br [187.120.30.6]
13 114 ms 114 ms 115 ms 192.168.128.38
14 230 ms 230 ms 230 ms 192.168.128.54
15 119 ms * 116 ms 138-36-0-38.texnet.net.br [138.36.0.38]
16 116 ms 116 ms 115 ms 138-36-3-214.texnet.net.br [138.36.3.214]

 

[requiem]

Traffic internationally gone to a ball of **** again.

Cool ideas on Vumatel Blairgowrie

 

[requiem]

Local seems fine, but anything international is coming down at snails pace.

@PBCool is it a known problem?

Sucks having to use 3G as my fibre with you and Vumatel is essentially unusable

 

[rolandos]

International gone all streaming is stuffed thanks Vuma my sunday night NFL is shot sigh.. Morningside Vuma Aerial

 

[Sinbad]

Same here
https://www.speedtest.net/my-result/a/4356621029

Cisp/vuma ae/Blairgowrie

 

[Looney]

I’m also experiencing slow international. Streaming is crap. 200mb CISP Vuma Aerial Glenhazel.

 

[Bionic]

International is useless for streaming services. Started last night.

 

[macedon]

Same here... Cool Ideas your internet connection is becoming a joke!

 

[PBCool]

It looks like a Vumatel interface was reaching its limit, have shifted some traffic around and things should be back to normal.

 

[Bionic]

But I'm on Metro?

 

[Sinbad]

It looks like a Vumatel interface was reaching its limit, have shifted some traffic around and things should be back to normal.

Have a bell's, sir.

 

[jasweb]

Metrofibre.. Centurion. To Paris (France). Not too bad.

 

[Bionic]

Better now. Thanks! It would have been great if this was fixed from last night though.

 

[PBCool]

Better now. Thanks! It would have been great if this was fixed from last night though.

Last night was still using some of the SACS routing, so unrelated unfortunately.

 

[PBCool]

But I'm on Metro?

MFN shouldn't be affected unless they are having congestion.

 

[Fjorko]

We are

To Fortaleza:

Tracing route to 138-36-3-214.texnet.net.br [138.36.3.214]
over a maximum of 30 hops:

4 2 ms 2 ms 2 ms 154.0.3.114
5 24 ms 24 ms 24 ms 154.0.1.246
6 24 ms 31 ms 24 ms 154.0.4.162
7 23 ms 23 ms 25 ms 102.130.64.13
8 65 ms 57 ms 57 ms pe2-nc028.ang.sgn.as37468.angolacables.ao [197.149.151.194]
9 116 ms 116 ms 116 ms 170.238.232.145
10 124 ms 116 ms 124 ms pe1-nc013.br.ftz.as37468.angolacables.ao [170.238.232.81]
11 115 ms 115 ms 117 ms 170.238.235.18
12 116 ms 116 ms 117 ms 187.120.30.6.cliente.primelinelatam.com.br [187.120.30.6]
13 114 ms 114 ms 115 ms 192.168.128.38
14 230 ms 230 ms 230 ms 192.168.128.54
15 119 ms * 116 ms 138-36-0-38.texnet.net.br [138.36.0.38]
16 116 ms 116 ms 115 ms 138-36-3-214.texnet.net.br [138.36.3.214]

OK - I stand corrected then. So which traffic goes over the SACS cable ?