TelkomZA

Yeah in game pings of 1400ms, TS ping (local server) of 900ms.

Throughput is terrible as well. TelkomZA eventually responded to my Twitter message (telling me no reported problems - I struggle to believe it) and asked me to send traceroutes but twitter is a rubbish medium of communication, especially for this sort of thing. Love the fact that they are present here on MyBB! Just waiting for that magic response of - we believe you, we are attending to it!
 
It took me from Friday morning, until Monday afternoon to convince someone at Telkom that my ADSL was syncing, but I could not connect to any ISP. :D
 
TelkomZA please help.
For the last month or so, every now and then, mainly late mornings and late evenings my ping goes crazy.
Tonight is one of those times.
I have 2 ISP accounts: Mweb nocap and OpenWeb nocap and both present the probem:

C:\>ping www.mweb.co.za

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=364ms TTL=117
Reply from 196.2.63.110: bytes=32 time=367ms TTL=117
Reply from 196.2.63.110: bytes=32 time=376ms TTL=117
Reply from 196.2.63.110: bytes=32 time=373ms TTL=117

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 364ms, Maximum = 376ms, Average = 370ms

C:\>ping www.mybroadband.co.za

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=376ms TTL=48
Reply from 41.203.21.137: bytes=32 time=334ms TTL=48
Reply from 41.203.21.137: bytes=32 time=329ms TTL=48
Reply from 41.203.21.137: bytes=32 time=329ms TTL=48

Ping statistics for 41.203.21.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 329ms, Maximum = 376ms, Average = 342ms

C:\>
 
ProAsm said:
TelkomZA please help.
For the last month or so, every now and then, mainly late mornings and late evenings my ping goes crazy.
Tonight is one of those times.
I have 2 ISP accounts: Mweb nocap and OpenWeb nocap and both present the probem:

C:\>ping www.mweb.co.za

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=364ms TTL=117
Reply from 196.2.63.110: bytes=32 time=367ms TTL=117
Reply from 196.2.63.110: bytes=32 time=376ms TTL=117
Reply from 196.2.63.110: bytes=32 time=373ms TTL=117

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 364ms, Maximum = 376ms, Average = 370ms

C:\>ping www.mybroadband.co.za

Pinging www.mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=376ms TTL=48
Reply from 41.203.21.137: bytes=32 time=334ms TTL=48
Reply from 41.203.21.137: bytes=32 time=329ms TTL=48
Reply from 41.203.21.137: bytes=32 time=329ms TTL=48

Ping statistics for 41.203.21.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 329ms, Maximum = 376ms, Average = 342ms

C:\>
Click to expand...

Hi there ProAsm - I suggest you post the results of a traceroute. You get it the same way you would a ping, just type in this at the command prompt: tracert www.telkom.co.za

This helps them diagnose where the connection is going wonky.
 
Thanks StevenC

Here it is:

ISP = Mweb:

C:\>tracert www.telkom.co.za

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 280 ms 259 ms 272 ms 41-133-48-1.dsl.mweb.co.za [41.133.48.1]
3 281 ms 300 ms 279 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 248 ms 245 ms 240 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 208 ms 219 ms 213 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
6 150 ms 139 ms 139 ms jhb.telkom-ipnet.co.za [197.80.4.117]
7 138 ms 145 ms 142 ms 196.43.25.137
8 159 ms 160 ms 159 ms 196.43.51.78
9 telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports:
Destination net unreachable.

Trace complete.

C:\>

ISP = OpenWeb:

C:\>tracert www.telkom.co.za

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

1 <1 ms 1 ms <1 ms 192.168.1.254
2 8 ms 7 ms 7 ms 41-66-69-1.digichilli.co.za [41.66.69.1]
3 121 ms 126 ms 118 ms 196.44.238.54
4 132 ms 135 ms 137 ms 196.44.239.50
5 95 ms 92 ms 92 ms rndf-ip-ll-1-wan.telkom-ipnet.co.za [196.25.200.45]
6 97 ms 98 ms 105 ms 196.43.51.78
7 * telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports:
Destination net unreachable.

Trace complete.

C:\>
 
Last edited:
As promised, here is a traceroute during the day to show the difference and most likely why the exchange looks fine when tested during the day. This is how it used to be in the evenings and it was a pleasure to have. This also further proves that there is not an issue with my line, ISP or any hardware I am using.

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

1 <1 ms 1 ms <1 ms 192.168.0.1
2 12 ms 12 ms 11 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 14 ms 13 ms 12 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 14 ms 13 ms 13 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 19 ms 15 ms 18 ms TenGigE0-0-0-2.11.cpt-p-2.mweb.co.za [196.28.178.98]
6 13 ms 13 ms 13 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 15 ms 14 ms 13 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 13 ms 13 ms 13 ms 196.43.25.205
9 38 ms 37 ms 37 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
10 * telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination net unreachable.

Trace complete.
 
StevenC said:
As promised, here is a traceroute during the day to show the difference and most likely why the exchange looks fine when tested during the day. This is how it used to be in the evenings and it was a pleasure to have. This also further proves that there is not an issue with my line, ISP or any hardware I am using.

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

1 <1 ms 1 ms <1 ms 192.168.0.1
2 12 ms 12 ms 11 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 14 ms 13 ms 12 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 14 ms 13 ms 13 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 19 ms 15 ms 18 ms TenGigE0-0-0-2.11.cpt-p-2.mweb.co.za [196.28.178.98]
6 13 ms 13 ms 13 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 15 ms 14 ms 13 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 13 ms 13 ms 13 ms 196.43.25.205
9 38 ms 37 ms 37 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
10 * telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination net unreachable.

Trace complete.
Click to expand...

Yes, mine does pretty much the same. Here is a trace route from last night. I tested with unshaped account and telkom account and makes no difference. TelkomZA send me a PM today saying their tech is looking into it today, during the day it tests fine.

Tracing route to google.co.za [74.125.233.88]
over a maximum of 30 hops:

1 8 ms 15 ms 10 ms . [192.168.2.1]
2 231 ms 252 ms 286 ms ti-224-76-01.telkomadsl.co.za [105.224.76.1]
3 301 ms 310 ms 305 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 254 ms 314 ms 359 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 331 ms 291 ms 261 ms 165.165.216.221
6 349 ms 340 ms 289 ms rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.
43.11.134]
7 244 ms 270 ms 261 ms 196.43.26.106
8 206 ms 228 ms 215 ms 72.14.212.1
9 242 ms 200 ms 191 ms 64.233.174.57
10 352 ms 333 ms 283 ms jnb01s02-in-f24.1e100.net [74.125.233.88]

Trace complete.
 
sakkiemotto said:
Yes, mine does pretty much the same. Here is a trace route from last night. I tested with unshaped account and telkom account and makes no difference. TelkomZA send me a PM today saying their tech is looking into it today, during the day it tests fine.

Tracing route to google.co.za [74.125.233.88]
over a maximum of 30 hops:

1 8 ms 15 ms 10 ms . [192.168.2.1]
2 231 ms 252 ms 286 ms ti-224-76-01.telkomadsl.co.za [105.224.76.1]
3 301 ms 310 ms 305 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 254 ms 314 ms 359 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 331 ms 291 ms 261 ms 165.165.216.221
6 349 ms 340 ms 289 ms rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.
43.11.134]
7 244 ms 270 ms 261 ms 196.43.26.106
8 206 ms 228 ms 215 ms 72.14.212.1
9 242 ms 200 ms 191 ms 64.233.174.57
10 352 ms 333 ms 283 ms jnb01s02-in-f24.1e100.net [74.125.233.88]

Trace complete.
Click to expand...

TelkomZA also sent me a PM that a tech is looking into the exchange
 
nerf said:
TelkomZA also sent me a PM that a tech is looking into the exchange
Click to expand...

Well seeing as i got the exact same problem does that mean a fix for me to? The techie i spoke to said he is going to request that they open more ports or something? Not really sure.... mine got bad last night at around 6pm, was perfect before then.
 
Darkon Iramus said:
Well seeing as i got the exact same problem does that mean a fix for me to? The techie i spoke to said he is going to request that they open more ports or something? Not really sure.... mine got bad last night at around 6pm, was perfect before then.
Click to expand...

Well the Telkom Technician just left my house, same old storie I have heard a dozen times before -line tests fine and there is no problem - followed by the sms "Fault was restored" ect. Well the problem is every evening when my ping goes to infinity and beyond, I definitely notice a problem :mad:
TelkomZA please help resolve this :cry:
 
sakkiemotto said:
Well the Telkom Technician just left my house, same old storie I have heard a dozen times before -line tests fine and there is no problem - followed by the sms "Fault was restored" ect. Well the problem is every evening when my ping goes to infinity and beyond, I definitely notice a problem :mad:
TelkomZA please help resolve this :cry:
Click to expand...

Technician came to my house I explained the problem and he said there are too many customers on the Card at the DSLAM im connected to, he said he was going to move me to another card. Will see tonight how it goes
 
nerf said:
Technician came to my house I explained the problem and he said there are too many customers on the Card at the DSLAM im connected to, he said he was going to move me to another card. Will see tonight how it goes
Click to expand...

TelkomZA has escalated my fault, so lets see what happens.
 
sakkiemotto said:
Well the Telkom Technician just left my house, same old storie I have heard a dozen times before -line tests fine and there is no problem - followed by the sms "Fault was restored" ect. Well the problem is every evening when my ping goes to infinity and beyond, I definitely notice a problem :mad:
TelkomZA please help resolve this :cry:
Click to expand...

same thing for me, TelkomZA also escalated my fault
 
Right in the middle of a PvP match this happens =(

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

1 2 ms <1 ms <1 ms 192.168.0.1
2 687 ms 738 ms 728 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 659 ms 737 ms 835 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 856 ms 831 ms 770 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 826 ms 827 ms 848 ms TenGigE0-0-0-2.11.cpt-p-2.mweb.co.za [196.28.178.98]
6 839 ms 764 ms 740 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 802 ms 823 ms 859 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 700 ms 777 ms 767 ms 196.43.25.205
9 909 ms 943 ms 903 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
10 * * * Request timed out.
11 telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination net unreachable.

Trace complete.

Thank you TelkomZA for getting back to me on PM, eager to hear what the outcome is!
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X