Cool Ideas Fibre ISP - Feedback

Status
Not open for further replies.
Waylander said:
Phuma is on Vuma and Ajan is on Openserve

So, looks general to CISP’s CPT region
Click to expand...
All openserve traffic is still routing via JHB so two seperate long haul providers, which is why I doubt that's the case. Latency and capacity from JHB to CPT is all normal. There was a spike to 40ms from about 20:00 to 22:00 yesterday as per phuma, that was logged with the long haul provider.
 
Waylander said:
@PBCool

The higher latencies in the evenings bring back memories of DSL exchange congestion. Do you suspect that it's the fibre network's problem or is it related to contention on your network?
Click to expand...
The higher latency was over the long haul between JHB and CPT for 2 hours. It's not something that happens every night. Do you have a ticket number with examples? And are you on the aerial network by chance?
 
I am on a fibre line, in Bellville in Cape Town. I am with Vuma.
 
phuma said:
I am on a fibre line, in Bellville in Cape Town. I am with Vuma.
Click to expand...
Yeah so your increased latency between JHB and CPT was related to the long haul as mentioned.
 
@PBCool

As previously mentioned I recently signed up with CISP and I was told (via email) that you guys would be placing the MTN orders from the 1st of November. I then went on to cancel my account with MTN (it cancels on the 22nd) but now when I emailed the connect team asking if I would need to do anything on my side for the change over, they told me they haven't received the final order forms from MTN and that they will inform me when to cancel with my current provider...
I'm sure you can see where the problem is. What can I do in this situation?
 
Speed23 said:
@PBCool

As previously mentioned I recently signed up with CISP and I was told (via email) that you guys would be placing the MTN orders from the 1st of November. I then went on to cancel my account with MTN (it cancels on the 22nd) but now when I emailed the connect team asking if I would need to do anything on my side for the change over, they told me they haven't received the final order forms from MTN and that they will inform me when to cancel with my current provider...
I'm sure you can see where the problem is. What can I do in this situation?
Click to expand...
I'll follow up in the morning for you.
 
@PBCool, can you please escalate this, my 100mb line has been running like this since Thursday, logged a ticket on Friday, #COOL-20171110-52629... All tests on cable before support desk asks again...
ef7b17df9b067d52108667fbcc7df300.jpg
 
DWJ said:
@PBCool, can you please escalate this, my 100mb line has been running like this since Thursday, logged a ticket on Friday, #COOL-20171110-52629... All tests on cable before support desk asks again...
ef7b17df9b067d52108667fbcc7df300.jpg
Click to expand...
Sure but it will be logged with the provider which can take some time to resolve. Will push from my side.
 
Evening All ! Any issues to EU at the moment ! I am getting massive packet loss and high latency locally ! Logged a call with CISP

Experiencing some terrible connectivity to EU and some local ping variation.Massive packet loss to EU.

Please see attached speedtest

http://beta.speedtest.net/result/6790411848

Please advise if there are any affected services !

ping -t www.cisp.co.za
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=5ms TTL=59
Reply from 154.0.13.95: bytes=32 time=5ms TTL=59
Reply from 154.0.13.95: bytes=32 time=4ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=5ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=640ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=642ms TTL=59
Reply from 154.0.13.95: bytes=32 time=5ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=6ms TTL=59
Reply from 154.0.13.95: bytes=32 time=9ms TTL=59
Reply from 154.0.13.95: bytes=32 time=7ms TTL=59
Reply from 154.0.13.95: bytes=32 time=12ms TTL=59
Reply from 154.0.13.95: bytes=32 time=7ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=7ms TTL=59
Reply from 154.0.13.95: bytes=32 time=8ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59

ping -t www.bbc.co.uk

Reply from 212.58.244.27: bytes=32 time=191ms TTL=51
Reply from 212.58.244.27: bytes=32 time=186ms TTL=51
Request timed out.
Request timed out.
Reply from 212.58.244.27: bytes=32 time=194ms TTL=51
Reply from 212.58.244.27: bytes=32 time=192ms TTL=51
Request timed out.
Request timed out.
Reply from 212.58.244.27: bytes=32 time=199ms TTL=51
Request timed out.
Request timed out.
Reply from 212.58.244.27: bytes=32 time=189ms TTL=51
Reply from 212.58.244.27: bytes=32 time=184ms TTL=51
Reply from 212.58.244.27: bytes=32 time=189ms TTL=51
Reply from 212.58.244.27: bytes=32 time=186ms TTL=51
Request timed out.
Reply from 212.58.244.27: bytes=32 time=194ms TTL=51
Request timed out.
Reply from 212.58.244.27: bytes=32 time=195ms TTL=51
Request timed out.
Reply from 212.58.244.27: bytes=32 time=219ms TTL=51
Reply from 212.58.244.27: bytes=32 time=184ms TTL=51
Request timed out.
Request timed out.
Reply from 212.58.244.27: bytes=32 time=204ms TTL=51
Reply from 212.58.244.27: bytes=32 time=181ms TTL=51
Reply from 212.58.244.27: bytes=32 time=188ms TTL=51
Request timed out.
Reply from 212.58.244.27: bytes=32 time=186ms TTL=51
 
CRE4MPIE said:
Evening All ! Any issues to EU at the moment ! I am getting massive packet loss and high latency locally ! Logged a call with CISP

Experiencing some terrible connectivity to EU and some local ping variation.Massive packet loss to EU.

Please see attached speedtest

http://beta.speedtest.net/result/6790411848

Please advise if there are any affected services !

ping -t www.cisp.co.za
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=5ms TTL=59
Reply from 154.0.13.95: bytes=32 time=5ms TTL=59
Reply from 154.0.13.95: bytes=32 time=4ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=5ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=640ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=642ms TTL=59
Reply from 154.0.13.95: bytes=32 time=5ms TTL=59
Reply from 154.0.13.95: bytes=32 time=3ms TTL=59
Reply from 154.0.13.95: bytes=32 time=6ms TTL=59
Reply from 154.0.13.95: bytes=32 time=9ms TTL=59
Reply from 154.0.13.95: bytes=32 time=7ms TTL=59
Reply from 154.0.13.95: bytes=32 time=12ms TTL=59
Reply from 154.0.13.95: bytes=32 time=7ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59
Reply from 154.0.13.95: bytes=32 time=7ms TTL=59
Reply from 154.0.13.95: bytes=32 time=8ms TTL=59
Reply from 154.0.13.95: bytes=32 time=2ms TTL=59

ping -t www.bbc.co.uk

Reply from 212.58.244.27: bytes=32 time=191ms TTL=51
Reply from 212.58.244.27: bytes=32 time=186ms TTL=51
Request timed out.
Request timed out.
Reply from 212.58.244.27: bytes=32 time=194ms TTL=51
Reply from 212.58.244.27: bytes=32 time=192ms TTL=51
Request timed out.
Request timed out.
Reply from 212.58.244.27: bytes=32 time=199ms TTL=51
Request timed out.
Request timed out.
Reply from 212.58.244.27: bytes=32 time=189ms TTL=51
Reply from 212.58.244.27: bytes=32 time=184ms TTL=51
Reply from 212.58.244.27: bytes=32 time=189ms TTL=51
Reply from 212.58.244.27: bytes=32 time=186ms TTL=51
Request timed out.
Reply from 212.58.244.27: bytes=32 time=194ms TTL=51
Request timed out.
Reply from 212.58.244.27: bytes=32 time=195ms TTL=51
Request timed out.
Reply from 212.58.244.27: bytes=32 time=219ms TTL=51
Reply from 212.58.244.27: bytes=32 time=184ms TTL=51
Request timed out.
Request timed out.
Reply from 212.58.244.27: bytes=32 time=204ms TTL=51
Reply from 212.58.244.27: bytes=32 time=181ms TTL=51
Reply from 212.58.244.27: bytes=32 time=188ms TTL=51
Request timed out.
Reply from 212.58.244.27: bytes=32 time=186ms TTL=51
Click to expand...

Yeah, something broken my end too...

 
All you guys in Gauteng? Here in Cape Town things are working fine, streaming, downloading and browsing. Was also gaming earlier.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X