South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Speedtest not even opening for me.How?
View attachment 362318
I even got 3 sixes in mine, devil's taunting me. I am going to have to wake up at 4am and do a speedtest, just have to make sure to plug in a LAN cable as well.
Speedtest not even opening for me.
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=29ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=42ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 42ms, Average = 26ms
We've definitely come to realize that a network isn't something that you just setup once and leave, there is a lot of tweaking and optimization that takes place.
Would you mind testing tonight and letting me know how it goes.

Can you please run the same tests again, now that the changes have been put into effect, and then mail them to me on [email protected] along with your contact details and I'll make sure we work with you to find the cause of the issue.
Going to speedtest the same city.
EDIT: using beta.speedtest.net
View attachment 362302
Considering I am in cape Town, that's a ~20ms increase in normal ping, I am also the only one in the household using my net, so should be getting ~8.4Mbps down and 0.8Mbps up.
Im to lazy to post in the mobile thread, but are there any issues on the mobile side? Connection has been up and down this morning.
Mine really bad in Durban. a ping from my Afrihost ADSL to an Afrihost hosted server not reliable:
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=8 ttl=52 time=94.9 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=9 ttl=52 time=62.7 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=10 ttl=53 time=38.7 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=11 ttl=52 time=85.8 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=12 ttl=52 time=39.0 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=13 ttl=53 time=75.2 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=14 ttl=53 time=39.7 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=15 ttl=53 time=38.0 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=16 ttl=53 time=89.7 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=17 ttl=53 time=74.9 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=18 ttl=52 time=36.2 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=19 ttl=53 time=35.8 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=20 ttl=52 time=40.6 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=21 ttl=53 time=36.4 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=22 ttl=53 time=36.7 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=23 ttl=53 time=64.8 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=24 ttl=53 time=107 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=25 ttl=53 time=35.5 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=26 ttl=52 time=36.6 ms
Can't even watch Youtube
Streaming has been better tonight, I'm still seeing latency of 14 seconds to and from the broadcaster but that I can live with.
View attachment 362328
Mail sent
For the record, last night's test revealed that all things are well on the Eastern front.
Apologies for the tone in my posts yesterday, but it is rather annoying when one has a genuine issue and the response from your service provider is the rhetoric copy and paste stuff ......... if only the response reflected that the system was being tweaked with a request to hang in there for another day or two(at least then a problem is acknowledged and the end user is advised that improvement is in progress).
Kind regards
It's difficult to say definitively with speedtest, it should only be used as an general indicator. Sometimes the server or data centre could be the issue. As far as I know, many servers are "voluntarily" offered by hosting providers, so they are not always of the same standard and performance levelI think international speeds can be expected to fluctuate more as the distance, network links, etc are increased greatly.
That is a terrible excuse considering that LaraC did a speedtest to the same server and got lower latency even though she is further away, same for my speedtest to Vienna which is normally great. (latency difference also a lot more noticeable, I should be having ~185ms ping to Vienna, I had 210ms). Also throughput.
There is something wrong with the Cape Town IPC/connection to the international lines.
EDIT: while I was downloading
View attachment 362358
Notice the latency difference even though I was using my line at the same time?
It does demonstrate my point that a speedtest can show differing results depending on the timing, and also the specific server you test with. Speedtests are definitely useful but traceroutes and file downloads are more accurate and can be specifically replicated.
Same server. I am talking about the latency and not the download/upload. Every evening my latency increases by ~20-25ms and throughput drops. This includes torrents (which should increase in speed considering that everyone in the states turns their PCs when we go to bed). Also, the server is a 10Gbit one, I've tested it in Vienna with a 300Mbps link and got full speed, so throughput is probably not an issue, definitely not with a measly 10Mbps line.
AfriTeam,
Just a confirmation please, 169.1.3.1 & 169.1.3.2 are Durban DNS servers?
I need to configure some devices manually on my Network.