Telkom Internet Uncapped User Feedback.

Status
Not open for further replies.
ranger said:
That might be a different problem. Please post the URL and a traceroute to the server.
Click to expand...
Thx Ranger it downloaded with the correct hash.

The other 8 attempts were in the previous 3 weeks.


Edit:
These are GT5 (PS3) updates.
They don't download correctly either.

http://b0.ww.np.dl.playstation.net/...S00569_00-0000000000000000-A0109-V0100-PE.pkg
Sha 1 - f4d8b80f471ac9c5ef9b72cb443c02dfbeb826f2

http://b0.ww.np.dl.playstation.net/...S00569_00-0000000000000000-A0111-V0101-PE.pkg
SHA 1 - babbdbcb0a203058a90faf69b0f88df1716b018a

http://b0.ww.np.dl.playstation.net/...S00569_00-0000000000000000-A0112-V0100-PE.pkg

SHA 1 - 251e7e0b95a97f44a3938fd8c220148599cab404

There are many more and some are much bigger, but in general the hash files does not match.
 
Last edited:
Telkom phoned me after I tweeted them, they said they have passed on details etc to a third party who is investigating the latency issues etc for them....
 
Not telkom for a change, im getting excellent local speedtest results as well (35ms/8mbps/.8mbps)

Not sure whats happening between hops 5 and 6 though, anyone know?

Tracing route to www.supersport.com [196.28.29.136]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms ***.dsl.subscriber.telkomsa.net [*.*.*.*]
3 21 ms 21 ms 20 ms 105.228.0.6
4 21 ms 20 ms 21 ms 105.228.0.13
5 21 ms 19 ms 20 ms rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.41]
6 188 ms 191 ms 188 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
7 190 ms 190 ms 194 ms lon-up-1.mweb.co.za [195.66.224.149]
8 224 ms 226 ms 226 ms 176.67.177.235
9 226 ms 226 ms 222 ms 176.67.177.145
10 189 ms 193 ms 190 ms 176.67.177.227
11 187 ms 186 ms * 196.22.169.86
12 189 ms 189 ms 188 ms 252.29.28.196.mweb.co.za [196.28.29.252]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * ^C
 
Early this morning, I created two really basic batch files to log the tracert to a local server (telkom.co.za) and international server (riot.de). The reason I did this is because my ping only decreases between certain times of the day, and wanted to find where the issue may be. I hope this helps in resolving the issue. The files can be found here:
tracertinternational.txt
tracertlocal.txt

Source code for anyone wanting to do this themselves.
@echo off
:1
echo === %date% %time% === >> tracertinternational.txt
tracert riot.de >> tracertinternational.txt
goto 1

@echo off
:1
echo === %date% %time% === >> tracertlocal.txt
tracert telkom.co.za >> tracertlocal.txt
goto 1

To delay each tracert by a certain time, you can add:
ping localhost -n delay_integer > nul


The ping starts increasing at ~8:45 and more time-outs occur.
EDIT: forgot to mention speeds are running fine (4-6mbps on 10mbps line)
 
Last edited:
Ooooo youtube 1080p with no buffering, OMFG Ranger what ever you guys did worked a treat. Dont let anyone else touch the network now!!!
 
Streaming and downloads are perfect. Understandable that daytime downloads would be shaped.

Please fix the gaming issues. Matchmaking in xbox doesnt work on xbox live.
 
Subways81 said:
Not telkom for a change, im getting excellent local speedtest results as well (35ms/8mbps/.8mbps)

Not sure whats happening between hops 5 and 6 though, anyone know?

Tracing route to www.supersport.com [196.28.29.136]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms ***.dsl.subscriber.telkomsa.net [*.*.*.*]
3 21 ms 21 ms 20 ms 105.228.0.6
4 21 ms 20 ms 21 ms 105.228.0.13
5 21 ms 19 ms 20 ms rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.41]
6 188 ms 191 ms 188 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
7 190 ms 190 ms 194 ms lon-up-1.mweb.co.za [195.66.224.149]
8 224 ms 226 ms 226 ms 176.67.177.235
9 226 ms 226 ms 222 ms 176.67.177.145
10 189 ms 193 ms 190 ms 176.67.177.227
11 187 ms 186 ms * 196.22.169.86
12 189 ms 189 ms 188 ms 252.29.28.196.mweb.co.za [196.28.29.252]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * ^C
Click to expand...

MWEB seems to making a lot of routing changes, without considering some local peering links resulting in more specific routes advertised over their international links. I'll log some more requests again, but they probably won't be ayyended to before Monday.
 
ranger said:
MWEB seems to making a lot of routing changes, without considering some local peering links resulting in more specific routes advertised over their international links. I'll log some more requests again, but they probably won't be ayyended to before Monday.
Click to expand...

Just noticed that the tracert is to the wrong server. Should have been supersport.co.za. I think the site is being hammered or their servers are up to ****.
 
Streaming and downloads have been excellent the past few days, but today it's been even better ! No dips at all with the dl speed and absolutely zero buffering on YouTube. This is the internet experience I'm more than happy paying for :)
 
Has Gaming priority been lowered? My CS GO ping to UK was ~170ms earlier this week and now its 190 - 200ms

Telkom:
Tracing route to 91.227.223.191 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms home.gateway [10.0.0.2]
2 9 ms 11 ms 10 ms 224-80-1.dsl.subscriber.telkomsa.net [105.224.80
.1]
3 13 ms 11 ms 10 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 11 ms 10 ms 11 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 10 ms 11 ms 10 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 159 ms 156 ms 156 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
7 * * * Request timed out.
8 211 ms 208 ms 206 ms rtr-peer-02.maid.v4.custdc.net [109.74.255.2]
9 194 ms 193 ms 190 ms mai-core-rou2.vooservers.com [109.74.247.139]
10 190 ms 190 ms 190 ms 91.227.223.191

Trace complete.

Afrihost:
Tracing route to 91.227.223.191 over a maximum of 30 hops

1 10 ms 10 ms 11 ms 105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.
4.193]
2 35 ms 34 ms 33 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

3 17 ms 12 ms 10 ms 41.181.184.28
4 12 ms 10 ms 12 ms compj-cpt-1.mtnns.net [196.44.18.2]
5 157 ms 157 ms 158 ms ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]

6 184 ms 186 ms 185 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.20
1]
7 157 ms 154 ms 153 ms peer-08-linx.thn.v4.custdc.net [195.66.224.139]

8 158 ms 159 ms 158 ms rtr-peer-02.maid.v4.custdc.net [109.74.255.2]
9 159 ms 157 ms 158 ms mai-core-rou2.vooservers.com [109.74.247.139]
10 177 ms 177 ms 178 ms 91.227.223.191
 
Last edited:
Very slow youtube streaming this side (Paarl) - hoping a reset will fix things... This is getting a bit tedious...
 
Hi guys and gals i have a question that i hope can be answered,i am on a 1 MB line just how far is too far from the exchange to where you live.I stay more or less 5-6 km from my exchange,reason i am asking is that i want to up my line to 2MB but unsure if distance may impede that decision, in other words should i stay on 1MB or up it to 2MB,I get 89-94 Kb/s at the moment,do not want to screw things up now.
 
s1n1ster said:
Hi guys and gals i have a question that i hope can be answered,i am on a 1 MB line just how far is too far from the exchange to where you live.I stay more or less 5-6 km from my exchange,reason i am asking is that i want to up my line to 2MB but unsure if distance may impede that decision, in other words should i stay on 1MB or up it to 2MB,I get 89-94 Kb/s at the moment,do not want to screw things up now.
Click to expand...

Log in to your router and post your line stats. That will give a good indication on what your line is capable of.
 
s1n1ster said:
Not to sound foolish not sure how to post line stats:confused:
Click to expand...

Log in to your router and find the option which displays your line stats (pretty much all routers have this they just call it different names).

Copy the text.

Paste is in a new post here on the forum.

or

Take screenshot of line stats and post it the forum.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X