Still waiting for a response of when my issue will be resolved....
Still no response. No update to ticket for a month. Still not solved.
When will this be corrected...
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Still waiting for a response of when my issue will be resolved....
I stream on DSTV now absolutely fine. No issues at all, so not CISP. How much bandwidth do they have? An IP to test?whats really annoying me of late is i stream the F1 from morning streams and i cant stream the 1080p stream at 6Mbps but when i stream it on my rain mobile at that rate its 100% fine, something is not right with the cisp network at the moment @TheRoDent @PBCool
Does that mean update on Monday?Sorry for the delay will look into this for you.
Hmm says coming soon on the cisp page?You can already, do it from your Vuma Portal, I am on 1Gbps, but only for Trenched right now.
You can already, do it from your Vuma Portal, I am on 1Gbps, but only for Trenched right now.

What is going on ? Int speeds are just fantastic ?
View attachment 639726
never had this issue before
Think this is tending towards some network complications all over the place. twitch for the first time since i have been a CISP customer is giving me such a kak experience for the past few days. Also ping now to the EU is kak 180ms vs users on axxess who are at 150ms and also jhb based, just not sure what is going onNot sure what is going on, but trying the watch the F1 on DSTV Now is very frustrating. Runs fine and then pixelates, then comes back then pixelates again.
Not sure if it's DSTV, CISP or Vuma
Getting some really weird **** going on ... Happens randomly all the time.
Reply from 212.58.244.66: bytes=32 time=168ms TTL=51
Reply from 212.58.244.66: bytes=32 time=168ms TTL=51
Reply from 154.0.1.17: Destination net unreachable.
Reply from 212.58.244.66: bytes=32 time=175ms TTL=51
Reply from 154.0.1.17: Destination net unreachable.
Reply from 154.0.1.17: Destination net unreachable.
Reply from 154.0.1.17: Destination net unreachable.
Reply from 212.58.244.66: bytes=32 time=174ms TTL=51
Reply from 154.0.1.17: Destination net unreachable.
Reply from 154.0.1.17: Destination net unreachable.
Reply from 154.0.1.17: Destination net unreachable.
Reply from 154.0.1.17: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.244.66: bytes=32 time=168ms TTL=51
Only on international ... local is fine
Getting some really weird **** going on ... Happens randomly all the time.
Reply from 212.58.244.66: bytes=32 time=168ms TTL=51
Reply from 212.58.244.66: bytes=32 time=168ms TTL=51
Reply from 154.0.1.17: Destination net unreachable.
Reply from 212.58.244.66: bytes=32 time=175ms TTL=51
Reply from 154.0.1.17: Destination net unreachable.
Reply from 154.0.1.17: Destination net unreachable.
Reply from 154.0.1.17: Destination net unreachable.
Reply from 212.58.244.66: bytes=32 time=174ms TTL=51
Reply from 154.0.1.17: Destination net unreachable.
Reply from 154.0.1.17: Destination net unreachable.
Reply from 154.0.1.17: Destination net unreachable.
Reply from 154.0.1.17: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.58.244.66: bytes=32 time=168ms TTL=51
Only on international ... local is fine
Not actually sure, but this issue keeps happening at 9 PM this whole week, and no information about why... Might be time to start looking into itIs it hard to change ISP's on fibre?