High Ping (100 - 233)

S

sturshel

Member
Joined
Jul 8, 2014
Messages
22
Reaction score
0
Howzit!

Last cople of days, since 11th, very slow internet and high pings, in the hundreds to two hundreds.

Anyone got any advice?
 
My Axxess backup 1 gb account is working perfectly with 29 ms ping so definitely Telkom ISP at fault.
 
Last edited:
Looks like it is their servers when checking on the tracert that is the problem so the game servers must be using a different one.

Well changing DNS is doing nothing so must be an internal problem with the ISP.
 
Last edited:
Same story with me. Noticed it for about two weeks now. Mornings are perfect. Im on a telkom capped account.

Afrihost
Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=21ms TTL=244
Reply from 196.43.22.222: bytes=32 time=21ms TTL=244
Reply from 196.43.22.222: bytes=32 time=21ms TTL=244
Reply from 196.43.22.222: bytes=32 time=21ms TTL=244

Telkom:
Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=309ms TTL=246
Reply from 196.43.22.222: bytes=32 time=310ms TTL=246
Reply from 196.43.22.222: bytes=32 time=314ms TTL=246
Reply from 196.43.22.222: bytes=32 time=318ms TTL=246

Tracert shows the slowdown as soon as you in the Telkom network.

Afrihost:

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 105-236-14-1-esr-lo.mtnbusiness.co.za [105.236.14.1]
3 16 ms 16 ms 16 ms 41.181.221.218
4 35 ms 16 ms 16 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
5 17 ms 16 ms 17 ms rb-cr-1.za--rb-dca-2.mtnns.net [196.44.31.122]
6 17 ms 31 ms 16 ms 41.181.139.109
7 18 ms 17 ms 18 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.17]
8 18 ms 18 ms 18 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [196.43.25.137]
9 18 ms 18 ms 17 ms 196.43.39.166
10 18 ms 18 ms 18 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
11 21 ms 21 ms 21 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
12 * 21 ms 20 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]


Telkom:
Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 6 ms ti-224-228-01.telkomadsl.co.za [105.224.228.1]
3 310 ms 314 ms 313 ms 105.229.0.22
4 311 ms 312 ms 316 ms 105.229.0.13
5 322 ms 308 ms 298 ms 165.165.233.249
6 339 ms 339 ms 330 ms 196.43.39.166
7 335 ms 336 ms 339 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
8 301 ms 305 ms 304 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
9 315 ms 317 ms 319 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]

Trace complete.
 
mrudling said:
Same story with me. Noticed it for about two weeks now. Mornings are perfect. Im on a telkom capped account.

Afrihost
Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=21ms TTL=244
Reply from 196.43.22.222: bytes=32 time=21ms TTL=244
Reply from 196.43.22.222: bytes=32 time=21ms TTL=244
Reply from 196.43.22.222: bytes=32 time=21ms TTL=244

Telkom:
Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=309ms TTL=246
Reply from 196.43.22.222: bytes=32 time=310ms TTL=246
Reply from 196.43.22.222: bytes=32 time=314ms TTL=246
Reply from 196.43.22.222: bytes=32 time=318ms TTL=246

Tracert shows the slowdown as soon as you in the Telkom network.

Afrihost:

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 105-236-14-1-esr-lo.mtnbusiness.co.za [105.236.14.1]
3 16 ms 16 ms 16 ms 41.181.221.218
4 35 ms 16 ms 16 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
5 17 ms 16 ms 17 ms rb-cr-1.za--rb-dca-2.mtnns.net [196.44.31.122]
6 17 ms 31 ms 16 ms 41.181.139.109
7 18 ms 17 ms 18 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.17]
8 18 ms 18 ms 18 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [196.43.25.137]
9 18 ms 18 ms 17 ms 196.43.39.166
10 18 ms 18 ms 18 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
11 21 ms 21 ms 21 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
12 * 21 ms 20 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]


Telkom:
Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 6 ms ti-224-228-01.telkomadsl.co.za [105.224.228.1]
3 310 ms 314 ms 313 ms 105.229.0.22
4 311 ms 312 ms 316 ms 105.229.0.13
5 322 ms 308 ms 298 ms 165.165.233.249
6 339 ms 339 ms 330 ms 196.43.39.166
7 335 ms 336 ms 339 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
8 301 ms 305 ms 304 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
9 315 ms 317 ms 319 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]

Trace complete.
Click to expand...

Same thing with my tracert here it has been off and on last few days and now its been bad the whole day with 300 ms and have reported it to Telkom on facebook and they investigating it hopefully they will find something.

Tracing route to saix.net [196.25.1.204]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.3
2 10 ms 10 ms 10 ms ti-224-164-01.telkomadsl.co.za [105.224.164.1]
3 234 ms 234 ms 236 ms 105.229.0.6
4 253 ms 251 ms 256 ms 105.229.0.29
5 238 ms 237 ms 232 ms tbnb-ip-hsll-1-wan.telkom-ipnet.co.za [165.165.235.173]
6 254 ms 256 ms 259 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30]
7 * wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30] reports: Destination net unreachable.

Trace complete.
 
Seems like a couple of people are bitching about Telkom atm...theres a thread on mygaming as well
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X