Telkom Internet Capped/Uncapped User Feedback (Pt2)

dmw said:
Is anyone experiencing latency issues? My ping in games is going anywhere from 230-600ms and streaming Youtube, Iplayer etc is stuttering all the time.
I would call Telkom directly but they wont talk to me as I am not named on the account even though we went physically into Hatfield outlet and gave them proof of residence and I.D.
Click to expand...

Several people here have similar issues... hopefully Ranger has good news for us soon:)
 
ranger said:
Patch Tuesday. We delivered a *lot* of Windows updates between abput 7h30 and 10h00. Some work we have done to change how Windows Updates are delivered paid off in one way, but we may have to do a bit more tuning to prevent the IPC from congesting.
Click to expand...

Thanks, things have improved somewhat but streaming and some other services aren't as snappy as they usually are.
 
acp said:
I think at this stage it would be fair to conclude that all is not well with Telkom Internet, much like another well known South African parastatal...

Perhaps Telkom should initiate "bandwidth-shedding". This way, everyone with TI might have some form of working internet, some of the time.
Click to expand...
Interesting idea which might have some traction now that the most outspoken fans are rebelling :D
 
had to switch to an alternate account.....this time not for my ping issues, but router keeps on giving me "LPC DOWN", working fine on AH and another ISP
 
After a day or two away, I return home to this...

2782293723.png

Am I the only one?
 
acp said:
After a day or two away, I return home to this...

Am I the only one?
Click to expand...

Mine's been like that for a week. Trying to call them for a port reset since my 1st hop on tracert is 500ms but keep hanging up after 45min wait on the call.
 
Crabby said:
Mine's been like that for a week. Trying to call them for a port reset since my 1st hop on tracert is 500ms but keep hanging up after 45min wait on the call.
Click to expand...

Oh, the joys... Sounds about right. How could anyone expect a call to the call centre to be answered within 45 minutes? That would not be supportive of the African agenda and be truly counter-revolutionary.

I logged fault online last night. Usually these are attended to quite fast although I always escalate them to TelkomZA online team of isolated champions. No category imo for what I'm experiencing, so selected 'TI problems', and tried to provide a short description of the issue.

I cannot put my finger on whether this is TI-related or whether I have a congested exchange. Tests with alternative ISPs last night proved to be just as slow, with fast, normal bouts in between for all.

Right now, this is what I'm getting:

speedof.me_14-12-15 (1).jpg

Better, but not where it should be. However, makes me believe with all the happy-holiday-heavy-downloaders at home roasting their connections, it could be exchange related.

Then again, it does not explain the slower international daytime speeds beginning of Dec until Friday...
Therefore, a mystery.
Most likely a lot easier to find the Kruger millions than figuring out what's wrong at Telkom, apart from the obvious ;)
 

Attachments

  • speedof.me_14-12-15.jpg
    speedof.me_14-12-15.jpg
    32.1 KB · Views: 175
bwana said:
10mbps goodness?

View attachment 175431
Click to expand...

Same here, local is fine but there seems to be problem overseas, see hop 8:

Code: 
[mick@mick1 Backups]$ mtr -rc 10 bbc.co.uk
Start: Mon Dec 15 13:50:51 2014
HOST: mick1.mickza                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- newcop                     0.0%    10    0.1   0.2   0.1   0.3   0.0
  2.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- wblv-ip-hsll-2-gi-3-0-0-v  0.0%    10   23.5  30.7  23.0  95.9  22.9
  4.|-- ipc-3-up.south.dsl.telkom  0.0%    10   22.7  23.4  22.7  24.1   0.0
  5.|-- ipc-aggr-1.south.dsl.telk  0.0%    10   23.2  23.5  23.2  23.9   0.0
  6.|-- wbs-ip-ll-1-wan.telkom-ip  0.0%    10   23.9  23.9  23.5  24.3   0.0
  7.|-- lon-ip-hsll-1-gig-0-1-0.t  0.0%    10  167.0 167.5 167.0 167.7   0.0
  8.|-- xe-0-1-0-19.r00.londen10. 40.0%    10  529.1 522.0 511.6 529.1   6.4
  9.|-- ae-7.r23.londen03.uk.bb.g  0.0%    10  503.7 442.9 167.4 518.8 144.8
 10.|-- bbc-linx.pr01.rbsov.bbc.c  0.0%    10  168.3 167.9 167.5 168.3   0.0
 11.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
 12.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
 13.|-- ae0.er01.telhc.bbc.co.uk   0.0%    10  174.6 174.5 174.3 174.9   0.0
 14.|-- 132.185.255.149            0.0%    10  175.3 175.4 174.9 176.1   0.0
 15.|-- fmt-vip72.telhc.bbc.co.uk  0.0%    10  174.8 174.6 174.2 175.3   0.0
[mick@mick1 Backups]$
 
acp said:
Then again, it does not explain the slower international daytime speeds beginning of Dec until Friday...
Therefore, a mystery.
Most likely a lot easier to find the Kruger millions than figuring out what's wrong at Telkom, apart from the obvious ;)
Click to expand...

They made some changes if on ADSL2 as posted by cavedog

Hoping ranger-san can give us more insight into this on a technical level :D.
 
MickZA said:
Same here, local is fine but there seems to be problem overseas, see hop 8:

Code: 
[mick@mick1 Backups]$ mtr -rc 10 bbc.co.uk
Start: Mon Dec 15 13:50:51 2014
HOST: mick1.mickza                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- newcop                     0.0%    10    0.1   0.2   0.1   0.3   0.0
  2.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- wblv-ip-hsll-2-gi-3-0-0-v  0.0%    10   23.5  30.7  23.0  95.9  22.9
  4.|-- ipc-3-up.south.dsl.telkom  0.0%    10   22.7  23.4  22.7  24.1   0.0
  5.|-- ipc-aggr-1.south.dsl.telk  0.0%    10   23.2  23.5  23.2  23.9   0.0
  6.|-- wbs-ip-ll-1-wan.telkom-ip  0.0%    10   23.9  23.9  23.5  24.3   0.0
  7.|-- lon-ip-hsll-1-gig-0-1-0.t  0.0%    10  167.0 167.5 167.0 167.7   0.0
  8.|-- xe-0-1-0-19.r00.londen10. 40.0%    10  529.1 522.0 511.6 529.1   6.4
  9.|-- ae-7.r23.londen03.uk.bb.g  0.0%    10  503.7 442.9 167.4 518.8 144.8
 10.|-- bbc-linx.pr01.rbsov.bbc.c  0.0%    10  168.3 167.9 167.5 168.3   0.0
 11.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
 12.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
 13.|-- ae0.er01.telhc.bbc.co.uk   0.0%    10  174.6 174.5 174.3 174.9   0.0
 14.|-- 132.185.255.149            0.0%    10  175.3 175.4 174.9 176.1   0.0
 15.|-- fmt-vip72.telhc.bbc.co.uk  0.0%    10  174.8 174.6 174.2 175.3   0.0
[mick@mick1 Backups]$
Click to expand...

This one is quite telling, proves it isn't us but wholesale ... will escalate on Wednesday. We should have stats highlighting this, but there were other priorities today.
 
I would just like to let the people affected by the Cape Town site's limited IPC capacity that we received and accepted a proposal for upgrading the IPC capacity on the new transmission today. Since the build portion was completed before the network change freeze, it should be possible to get this implemented on Wednesday. However, we need to make changes on our side after the IPC cspacity is available. Hopefully the experience should be better on Thursday. There are still some minor issues that came up in the mean time that we need to deal with ...
 
Kids are complaining - cannot connect to DOTA, etc.

Trace route:

C:\Documents and Settings\>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.244.18] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 8 ms eltg-ip-bb-1.south.dsl.telkomsa.net [105.224.140.1]
3 21 ms 20 ms 23 ms ipc-2-up.south.dsl.telkomsa.net [105.226.0.22]
4 27 ms 27 ms 27 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 27 ms 26 ms 26 ms 196.25.190.209
6 171 ms 179 ms 183 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
7 500 ms 498 ms * xe-0-1-0-19.r00.londen10.uk.bb.gin.ntt.net [83.231.146.245]
8 499 ms 510 ms 202 ms ae-7.r23.londen03.uk.bb.gin.ntt.net [129.250.6.54]
9 205 ms 185 ms 205 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
10 * * * Request timed out.
11 * * * Request timed out.
12 515 ms * 496 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
13 191 ms 191 ms 195 ms 132.185.255.149
14 188 ms 188 ms 188 ms fmt-vip72.telhc.bbc.co.uk [212.58.244.18]

Trace complete.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X