South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Tracing route to 197-80-200-51.jhb.mweb.co.za [197.80.200.51]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 24 ms 24 ms 24 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
4 63 ms 65 ms 60 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 25 ms 28 ms 24 ms optinet.ixp.joburg [196.60.8.120]
6 26 ms 25 ms 26 ms 197-80-4-194.jhb.mweb.co.za [197.80.4.194]
7 39 ms 37 ms 36 ms bu-ether3.mca-pe-2.optinet.net [197.80.4.251]
8 74 ms 67 ms 63 ms bu-ether2.mca-pe-1.optinet.net [197.80.4.225]
9 129 ms 127 ms 128 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
10 127 ms 129 ms 129 ms 197-80-200-51.jhb.mweb.co.za [197.80.200.51]
Trace complete.
Playing perfectly on one server then on the next it was totally kuk.
140 ping constantly.
Code:Tracing route to 197-80-200-51.jhb.mweb.co.za [197.80.200.51] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.0.1 2 * * * Request timed out. 3 24 ms 24 ms 24 ms jhb-up7.ip.adsl.co.za [169.1.5.6] 4 63 ms 65 ms 60 ms jhb-net1.ip.adsl.co.za [169.1.5.52] 5 25 ms 28 ms 24 ms optinet.ixp.joburg [196.60.8.120] 6 26 ms 25 ms 26 ms 197-80-4-194.jhb.mweb.co.za [197.80.4.194] 7 39 ms 37 ms 36 ms bu-ether3.mca-pe-2.optinet.net [197.80.4.251] 8 74 ms 67 ms 63 ms bu-ether2.mca-pe-1.optinet.net [197.80.4.225] 9 129 ms 127 ms 128 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30] 10 127 ms 129 ms 129 ms 197-80-200-51.jhb.mweb.co.za [197.80.200.51] Trace complete.
Peering issue?
![]()
That's not good at all.... Is this to CS:GO servers?
Indeed.
Our NOC Team reported last night that latency issues have been resolved. Would you be able to test again, Rickster?
We do unfortunately shape P2P and HTTP downloads on our Uncapped accounts during peak periods. You do have the option to Turbocharge your Uncapped account if you want to unshaped your downloads.
@AfriGenie @AfriFella @AfriMan and any others listening.. this is the first time ive heard about Seacom having an issue since last year or the year before.. why does it have to be so hard to get any info about this?? i thought i was my line that was causing the issue or telkom or something?!?!?
im on 10mb business uncapped!
speedtest in feb: http://www.speedtest.net/result/6064399069.png
speedtest now same line same router nothing changed:
Telkom SA (SAIX)
Cape Town
Afrihost
169.0.x.x
PING
22 ms
DOWNLOAD
6.26 Mbps
UPLOAD
0.54 Mbps
Seacom Ltd
Johannesburg
Afrihost
169.0.x.x
PING
111 ms
DOWNLOAD
1.27 Mbps
UPLOAD
0.53 Mbps
Speedtest.net
New York City, NY
Afrihost
169.0.x.x
PING
223 ms
DOWNLOAD
1.95 Mbps
UPLOAD
0.52 Mbps
and on your business uncapped accounts do you shape p2p/ news as well? I only ask as my line is heavily shaped from about 5pm till 11pm every night even weekends!!


Ping still shot on teamspeak.
We don't use Seacom as our primary international link - good to know.
I think we should follow the basic troubleshooting steps here to make sure we're not looking in the wrong places. First, could you please make sure nothing is running on your system (preferably test over LAN with a single device and WiFi switched off). - im sure ive done a bit more than that in the last 8 days but anyways!
Please run a traceroute to a local URL and a local speedtest, and then the same with an international one so we can analyse. -as you wouldve seen above ive already posted local and international speedtests but here's some more just for good measure. sorry about the sarcasm im a wee bit pissed off so to speak.
Business can be shaped, but we generally aim not to shape unless we really have to. - even though it happens 7 out of 7 days??
Just want to remind you that with the same router in feb 2017 i was able to get 8.5 on the same line:
View attachment 431590
Vox Telecom
Cape Town
Afrihost
169.0.x.x
PING
6 ms
DOWNLOAD
6.21 Mbps
UPLOAD
0.48 Mbps
Tracing route to www.afrihost.com [104.20.31.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 7 ms 6 ms 6 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 8 ms 7 ms 7 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 6 ms 6 ms 6 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 23 ms 22 ms 22 ms 169-1-21-29.ip.afrihost.co.za [169.1.21.29]
7 23 ms 33 ms 34 ms cloudflare.ixp.joburg [196.60.8.198]
8 22 ms 22 ms 22 ms 104.20.31.244
Trace complete.
ISPnet, Inc
New York City, NY
Afrihost
169.0.x.x
PING
252 ms
DOWNLOAD
1.66 Mbps
UPLOAD
0.50 Mbps
Tracing route to star-mini.c10r.facebook.com [185.60.219.35]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 8 ms 7 ms 6 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 7 ms 6 ms 7 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 7 ms 7 ms 6 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 23 ms 22 ms 22 ms 169-1-21-29.ip.afrihost.co.za [169.1.21.29]
7 22 ms 23 ms 23 ms ae7.br02.jnb1.tfbnw.net [157.240.64.196]
8 22 ms 22 ms 22 ms po102.psw01.jnb1.tfbnw.net [157.240.41.249]
9 22 ms 22 ms 22 ms 173.252.67.11
10 22 ms 22 ms 22 ms 185.60.219.35
Trace complete.
hoepfully these can give you more of an idea too:
View attachment 431586
Which Teamspeak server are you connecting to at the moment?
That's a lot of variation in both speed and latency.![]()
Shaping would appear like that though it would only affect your P2P and HTTP downloads. Your speedtest results and latencies shouldn't change.
Do we manage your DSL line?
Unfortunately no. Telkom are still working on this though as it doesnt make any sense that the download speed would be 2mb lower than it should be was 2 months ago and for the last 3 years before.
You do have a TS server on your network, IP is 169.1.1.244From the trace, seems like it's hosted at optinet and the latency seems inconsistent once we're in their network
Not sure if we still have a TS server on our network, I know we were running a Mumble server as well. Perhaps if we can test with different server we can see if the results are different.