Telkom Internet Capped/Uncapped User Feedback (Pt2)

Email received
----------------------

Dear Subscriber,

Telkom Internet is aware that some customers in the Western and Eastern Cape may experience intermittent high latency on some international internet traffic during evenings. Initial investigations by our technical personnel have revealed that local broadband traffic is unaffected and running at normal speeds.

Telkom Internet’s technical team is currently working closely with its wholesale supplier in order to resolve the fault as quickly as possible.

Telkom Internet apologises to affected customers and assures you that the matter is receiving priority attention.

We thank you for your patience while we continue working towards resolving this matter.
Regards,
Telkom Internet Technical Support
 
MickeyD said:
Email received
----------------------

Dear Subscriber,

Telkom Internet is aware that some customers in the Western and Eastern Cape may experience intermittent high latency on some international internet traffic during evenings. Initial investigations by our technical personnel have revealed that local broadband traffic is unaffected and running at normal speeds.

Telkom Internet’s technical team is currently working closely with its wholesale supplier in order to resolve the fault as quickly as possible.

Telkom Internet apologises to affected customers and assures you that the matter is receiving priority attention.

We thank you for your patience while we continue working towards resolving this matter.
Regards,
Telkom Internet Technical Support
Click to expand...

Telkom-DSL-BRAS_last_604800.png

Clearly not just a international problem...
 
terabit said:
Ok well I used http://rosebank.spdtst.saix.net/ with the guest account and I got this :
Download Speed: 8536 kbps (1067 KB/sec transfer rate)
Upload Speed: 843 kbps (105.4 KB/sec transfer rate)
Latency: 14 ms
11/10/2015, 5:50:09 PM

So if the guest account works fine but my account doesn't what does it mean?
Click to expand...

I know this is going to sound a little silly, but double check that your Data portion speed matches your line speed. A long time ago I upgraded mine to a higher speed, but they only upgraded my lines speed and not my uncapped account speed, so I had a 4Meg line with a 2 Meg uncapped account.
 
LomWoss said:
I know this is going to sound a little silly, but double check that your Data portion speed matches your line speed. A long time ago I upgraded mine to a higher speed, but they only upgraded my lines speed and not my uncapped account speed, so I had a 4Meg line with a 2 Meg uncapped account.
Click to expand...

This might be the case. Whenever I run a speed test now it would start out at 8.6Mbps for like 2 seconds and then drop down to something around 4Mbps. Will definitely check that.
 
OMW net is crawling from 6pm - 11pm. On 100meg fiber and its bad!

C:\Users\i7>tracert capetown.spdtst.saix.net

Tracing route to wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 18 ms 16 ms 17 ms wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za [105.226.0.29]
4 37 ms 36 ms 40 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
5 16 ms 14 ms 12 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
6 12 ms 9 ms 10 ms wbs-ip-ll-1-wan.telkom-ipnet.co.za [165.165.221.153]
7 419 ms 409 ms 411 ms wbs-ip-hsll-1-gig-2-1-0.telkom-ipnet.co.za [196.43.52.62]
8 427 ms 416 ms 438 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
9 396 ms 407 ms 415 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]

Trace complete.

C:\Users\i7>
 
Excuse my ignorance guys, but why would a tracert to a capetown server trace to JHB? Above Tracert shows that.
 
Ok, quickly signed up with webafrica on a free adls package. And the ping is perfect when i used that on my fiber line. Obviously not the speed of the 100meg but latency is perfect!

SAD DAYS!! The problem is Telkom as a ISP.
 
traceroute to wbs-ip-dlr-1-1.telkom-ipnet.co.za (196.25.37.14), 64 hops max, 52 byte packets
1 10.0.0.2 (10.0.0.2) 0.717 ms 0.362 ms 0.315 ms
2 wblv-ip-bb-1.south.dsl.telkomsa.net (105.224.144.1) 395.056 ms 390.805 ms 392.658 ms
3 ipc-1-up.south.dsl.telkomsa.net (105.226.0.6) 438.241 ms 365.875 ms 347.326 ms
4 ipc-aggr-1.south.dsl.telkomsa.net (105.226.0.13) 338.030 ms 374.587 ms *
5 * wbs-ip-ll-1-wan.telkom-ipnet.co.za (165.165.221.153) 603.313 ms
196.25.103.93 (196.25.103.93) 535.432 ms
6 wbs-ip-hsll-1-gig-7-0-0.telkom-ipnet.co.za (196.43.52.66) 523.263 ms 542.755 ms 524.164 ms
7 wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za (196.25.37.2) 469.879 ms !X 421.487 ms !X *



395ms to the first jump ... :cry:
 
Snake Blisken said:
5 16 ms 14 ms 12 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
6 12 ms 9 ms 10 ms wbs-ip-ll-1-wan.telkom-ipnet.co.za [165.165.221.153]
7 419 ms 409 ms 411 ms wbs-ip-hsll-1-gig-2-1-0.telkom-ipnet.co.za [196.43.52.62]
Click to expand...

This specific problem has been reported to Telkom Wholesale / Openserve, as it is clearly on their side.

When you see this behaviour, could you check whether the same occurs to other destinations that don't go via SAIX? For example traceroute to www.google.com .
 
ranger said:
This specific problem has been reported to Telkom Wholesale / Openserve, as it is clearly on their side.

When you see this behaviour, could you check whether the same occurs to other destinations that don't go via SAIX? For example traceroute to www.google.com .
Click to expand...

@streaker has been working on some initiatives over the past few months (related to our IPC upgrade), which were completed late last week. That allowed us to, in cooperation with Telkom Wholesale / Openserve, migrate traffic off one of their IPC offload routers seems to have been contributing to this problem, on Monday morning.

As far as we can see/test, it looks like the crazy latency is no longer present, but we will keep an eye on it.
 
What's the average latency one should expect on the ipc for a 2Mb/s line?

Code: 
traceroute to 152.111.192.244 (152.111.192.244), 30 hops max, 60 byte packets
 1  gateway (10.0.0.2)  1.525 ms  1.742 ms  2.265 ms
 2  * * *
 3  ipc-1-up.east.dsl.telkomsa.net (105.229.0.21)  61.751 ms  63.024 ms  65.450 ms
 4  ipc-1-up.east.dsl.telkomsa.net (105.229.0.22)  69.654 ms  70.052 ms  72.011 ms
 5  ipc-aggr-2.east.dsl.telkomsa.net (105.229.0.13)  75.542 ms *  78.345 ms
 6  dbn-pr-01-be200-vl1.net.telkosma.net (105.229.0.34)  80.905 ms  52.425 ms  55.189 ms

The above seems a bit excessive and I could have sworn I've had better latency in the past on a 1Mb/s line.

When I play csgo my latency is usually one of the worst of all players in the game.
 
ranger said:
@streaker has been working on some initiatives over the past few months (related to our IPC upgrade), which were completed late last week. That allowed us to, in cooperation with Telkom Wholesale / Openserve, migrate traffic off one of their IPC offload routers seems to have been contributing to this problem, on Monday morning.

As far as we can see/test, it looks like the crazy latency is no longer present, but we will keep an eye on it.
Click to expand...

Telkom-DSL-BRAS_last_604800.png

Still there...

Vs Internet Solutions:

IS-Telkom-BRAS_last_604800.png
 
GhostR,

Are you sending ping to your default gateway? You will be connecting on the same BRAS and should not be seeing this excessive difference
 
11:10am - 10MB Telkom uncapped ... unable to stream 240p video from Youtube. WOW, THIS SUCKS!
 
Last edited:
hi there , I hope someone can explain what is going with my traceroute as I cant load any webpages at all ,the strange thing is all lights is green on my router (DSL & Internet Lights)

C:\Users\>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.244.68]
over a maximum of 30 hops:

1 2 ms 1 ms <1 ms home.gateway [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 11 ms 11 ms * ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 * * 12 ms 165.165.214.213
7 * * 155 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
8 155 ms * * ldn-b5-link.telia.net [62.115.35.89]
9 155 ms * * atos-ic-151907-ldn-b5.c.telia.net [80.239.132.142]
10 * * * Request timed out.
11 * * * Request timed out.
12 * 190 ms * 132.185.255.149
13 156 ms 156 ms * bbc-vip113.telhc.bbc.co.uk [212.58.244.68]
14 * 156 ms * bbc-vip113.telhc.bbc.co.uk [212.58.244.68]
15 * 155 ms * bbc-vip113.telhc.bbc.co.uk [212.58.244.68]
16 * * * Request timed out.
17 * * * Request timed out.
18 156 ms * * bbc-vip113.telhc.bbc.co.uk [212.58.244.68]
19 * * * Request timed out.
20 156 ms * * bbc-vip113.telhc.bbc.co.uk [212.58.244.68]
21 * * 156 ms bbc-vip113.telhc.bbc.co.uk [212.58.244.68]

Trace complete.
 
Spamhater said:
hi there , I hope someone can explain what is going with my traceroute as I cant load any webpages at all ,the strange thing is all lights is green on my router (DSL & Internet Lights)
Click to expand...

TelkomZA has been investigating the packet loss I'm seeing on hop 3 but otherwise bbc.co.uk is OK from PE:
Code: 
[mick@house ~]$ mtr -rc 20 bbc.co.uk
Start: Thu Nov 19 17:40:12 2015
HOST: house                       Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- newcop                     0.0%    20    3.4   3.6   3.1   5.6   0.3
  2.|-- ???                       100.0    20    0.0   0.0   0.0   0.0   0.0
  3.|-- wbs-ip-hsll-2-gi4-0-0-vl1 45.0%    20   26.0  27.3  25.8  30.4   1.7
  4.|-- ipc-2-up.south.dsl.telkom  0.0%    20   27.8  29.5  26.0  42.4   4.7
  5.|-- ipc-aggr-2.south.dsl.telk  0.0%    20   33.3  34.9  32.8  48.7   3.9
  6.|-- 165.165.214.213            0.0%    20   32.7  34.7  32.5  45.3   3.6
  7.|-- lon-ip-dir-telecity-pos-1  0.0%    20  212.4 255.1 212.4 274.9  17.4
  8.|-- ldn-b5-link.telia.net      0.0%    20  173.5 179.7 171.9 215.3  10.6
  9.|-- atos-ic-151907-ldn-b5.c.t  0.0%    20  219.9 246.2 206.9 264.7  13.0
 10.|-- ???                       100.0    20    0.0   0.0   0.0   0.0   0.0
 11.|-- ae0.er01.telhc.bbc.co.uk   0.0%    20  223.5 246.0 206.4 273.2  14.6
 12.|-- 132.185.255.149            0.0%    20  171.6 177.0 171.3 196.9   6.3
 13.|-- fmt-vip71.telhc.bbc.co.uk  0.0%    20  174.1 175.9 169.6 188.7   6.0
 
MickZA said:
TelkomZA has been investigating the packet loss I'm seeing on hop 3 but otherwise bbc.co.uk is OK from PE:
Code: 
[mick@house ~]$ mtr -rc 20 bbc.co.uk
Start: Thu Nov 19 17:40:12 2015
HOST: house                       Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- newcop                     0.0%    20    3.4   3.6   3.1   5.6   0.3
  2.|-- ???                       100.0    20    0.0   0.0   0.0   0.0   0.0
  3.|-- wbs-ip-hsll-2-gi4-0-0-vl1 45.0%    20   26.0  27.3  25.8  30.4   1.7
  4.|-- ipc-2-up.south.dsl.telkom  0.0%    20   27.8  29.5  26.0  42.4   4.7
  5.|-- ipc-aggr-2.south.dsl.telk  0.0%    20   33.3  34.9  32.8  48.7   3.9
  6.|-- 165.165.214.213            0.0%    20   32.7  34.7  32.5  45.3   3.6
  7.|-- lon-ip-dir-telecity-pos-1  0.0%    20  212.4 255.1 212.4 274.9  17.4
  8.|-- ldn-b5-link.telia.net      0.0%    20  173.5 179.7 171.9 215.3  10.6
  9.|-- atos-ic-151907-ldn-b5.c.t  0.0%    20  219.9 246.2 206.9 264.7  13.0
 10.|-- ???                       100.0    20    0.0   0.0   0.0   0.0   0.0
 11.|-- ae0.er01.telhc.bbc.co.uk   0.0%    20  223.5 246.0 206.4 273.2  14.6
 12.|-- 132.185.255.149            0.0%    20  171.6 177.0 171.3 196.9   6.3
 13.|-- fmt-vip71.telhc.bbc.co.uk  0.0%    20  174.1 175.9 169.6 188.7   6.0
Click to expand...

I`m having a time out from hop 2 to 4 does this mean that my exchange is having problems
 
Spamhater said:
I`m having a time out from hop 2 to 4 does this mean that my exchange is having problems
Click to expand...
Not qualified to comment I'm afraid, are you using the TI DNS because the routing seems really screwy.

Have you got another ISP account to test with?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X