South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
That looks like an mweb problem though. Plus, I wouldn't be surprised if news24 were being subject to some DDoS attacks by now, given their censorship movespings down the crapper again, 200+ pings to local
![]()
poor form
That looks like an mweb problem though. Plus, I wouldn't be surprised if news24 were being subject to some DDoS attacks by now, given their censorship moves
Hmmm. Been streaming live source quality Twitch the last 2 hours without any problems.
I only started using my 100GB fatpipe special this month. [I am in cape town]
I created a ticket for Vox to look into my issues this morning (in progress). Thought I'd share my initial findings:
- Mweb had 2x faster ping to a European game server (BSGO).
- Battlefield 4 local game servers: all over 180ms ping...
- I did speed tests tonight - Vox shows 150 to 180ms (local server).
- I get 11ms with Axxess (used them as I had some data left with them).
- Ping to news24.co.za used to be about 11ms with mweb, its 185ms avg with Vox...
I did some speed tests now:
Vox speed tests:
1) http://www.speedtest.net/my-result/4650058686
2) http://www.speedtest.net/my-result/4650063395
Axxess speed tests:
http://www.speedtest.net/my-result/4650082169
Hopefully they can sort out whatever this is, otherwise it's back to trusty old mweb (just wish mweb could get cheaper).
You are actually right. Compared pings to local BF4 servers and say a 120ms difference between VoX and another ISP. Granted it is not like this everyday.Streaming is fine, it's the high pings that is the bigger issue.
You are actually right. Compared pings to local BF4 servers and say a 120ms difference between VoX and another ISP. Granted it is not like this everyday.
A fix was deployed this morning for CT, so will compare tonight again.
The fix was yesterday morning - so issues should already have been sorted last night.
Fatpipe seems a little sluggish for me today - general browsing / streaming.
Grab a traceroute or something to help narrow this down, it's not our network capacity ... (sneak peak, don't share... http://i.imgur.com/j2Mw100.png)
Grab a traceroute or something to help narrow this down, it's not our network capacity ... (sneak peak, don't share... http://i.imgur.com/j2Mw100.png)
What's the IP of the server you're having trouble with. Maybe cvanwie can advise where/what the bottleneck is, if you can paste a tracerouteOk So any response to my statement?
I expected the fix to reduce pings but this has not happened at all.
What's the IP of the server you're having trouble with. Maybe cvanwie can advise where/what the bottleneck is, if you can paste a traceroute
Grab a traceroute or something to help narrow this down, it's not our network capacity ... (sneak peak, don't share... http://i.imgur.com/j2Mw100.png)
Ok So any response to my statement?
I expected the fix to reduce pings but this has not happened at all.
So did I Electric.
I just walked out of a meeting (because it was over) with the Network team. I showed them the reports/graphs/forum reports for the last few months to validate that there was some misaligned configuration between the way we do things in JHB and the way we handle CPT.
The difference was found, and changes applied to CPT to fall in line with how JHB is handled.
Please run through tests tonight and report back here please.