Telkom Internet Capped/Uncapped User Feedback (Pt2)

BradleyKZN said:
Google services are down again. Its happening 3-4 times a day.

Ranger, any news on when this will be fixed?
Click to expand...

Is this for KZN (location in your profile doesn't help)? Only select google services should be impacted im KZN at present (mainly Youtube videos), and the changes made in Gauteng should make it to the other regions soon if we see no problems.

If you mean other Google services (e.g. mail, search), there shouldn't be any problems. A traceroute to the specific service would help though
...
 
Grouter said:
Thanks, I thought so. Just wonder why I always get allocated the Durban and Rosebank DNS servers when I leave it on auto.
Click to expand...

Because wholesale has been bringing up new BNGs, and re-allocating old IPs without informing ISPs proactively. We currently assign DNS based on NAS-IP-Address (a different solution is in the works). We'll request a new list of IPs to region and ask that they inform us when this critical information (used for some other things as well) changes.
 
Grouter said:
3 43 ms 41 ms 40 ms ti-226-0-246.telkomadsl.co.za [105.226.0.246]
4 41 ms 41 ms 41 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
5 40 ms 40 ms 40 ms wbs-ip-ll-1-wan.telkom-ipnet.co.za [165.165.221.
153]
Click to expand...

105.226.0.* is Cape Town, 105.224.0.* is Gauteng, 105.229.0.* is Durban. We're busy migrating reverse DNS so you would be able to see more easily. If you request reverse dns for 105.226.0.13 from ns1.telkomsa.net or ns2.telkomsa.net, you'll see the records as they will be by default soon.
 
reactor_sa said:
Come 5pm I get timeout on the second hop (first one after the router) - google services are not accessible when this happens. Everything else seems to work but super slow. What course of action to take? Log a fault? Been like this since yesterday (that I'm aware of).

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\reactor>tracert www.google.co.za

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

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 9 ms 8 ms 8 ms ti-224-0-05.telkomadsl.co.za [105.224.0.5]
4 9 ms 9 ms 8 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
5 9 ms 8 ms 8 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
6 9 ms 9 ms 8 ms cen-pr-01-te7-22-vl2.net.telkomsa.net [105.187.2
49.98]
7 9 ms 11 ms 9 ms jb1-pr-01-te8-3.net.telkomsa.net [105.187.249.2]

8 9 ms 9 ms 10 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]

9 9 ms 9 ms 10 ms 72.14.237.239
10 9 ms 9 ms 10 ms jnb01s07-in-f23.1e100.net [74.125.233.23]

Trace complete.
Click to expand...

The weird timeout on the 'ESR'/'BRAS' hop seems to happen on some BNGs.
Code: 
$ traceroute www.google.com
traceroute to www.google.com (74.125.233.114), 30 hops max, 60 byte packets
 1  ti-224-216-01.telkomadsl.co.za (105.224.216.1)  10.785 ms  13.041 ms  15.387 ms
 2  ti-224-0-06.telkomadsl.co.za (105.224.0.6)  22.487 ms  24.375 ms  26.597 ms
 3  ti-224-0-13.telkomadsl.co.za (105.224.0.13)  29.384 ms  31.507 ms  33.740 ms
 4  cen-pr-01-te7-22-vl2.net.telkomsa.net (105.187.249.98)  36.398 ms  40.023 ms  40.986 ms
 5  jb1-pr-01-te8-3.net.telkomsa.net (105.187.249.2)  45.167 ms  48.688 ms  49.793 ms
 6  jb1-google-gw.net.telkomsa.net (105.187.249.22)  52.080 ms  43.917 ms  45.138 ms
 7  72.14.239.129 (72.14.239.129)  44.132 ms  38.724 ms  40.033 ms
 8  jnb01s08-in-f18.1e100.net (74.125.233.114)  40.307 ms  39.028 ms  40.514 ms


$ mtr -rw www.google.com
Start: Thu Oct 16 23:05:41 2014
HOST: media                                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- ti-224-216-01.telkomadsl.co.za         0.0%    10   10.4  10.4  10.0  10.9   0.0
  2.|-- ti-224-0-06.telkomadsl.co.za           0.0%    10   13.8  14.1  13.6  15.2   0.0
  3.|-- ti-224-0-13.telkomadsl.co.za           0.0%    10   13.8  14.0  13.5  14.9   0.0
  4.|-- cen-pr-01-te7-22-vl2.net.telkomsa.net  0.0%    10   13.9  18.7  13.9  41.6   9.6
  5.|-- jb1-pr-01-te8-3.net.telkomsa.net       0.0%    10   15.7  15.4  14.9  16.4   0.3
  6.|-- jb1-google-gw.net.telkomsa.net         0.0%    10   14.7  14.6  14.4  14.7   0.0
  7.|-- 72.14.239.129                          0.0%    10   14.7  14.7  14.2  15.7   0.0
  8.|-- jnb01s08-in-f17.1e100.net              0.0%    10   15.5  15.2  14.0  16.0   0.0

I seem to be on tbnb-ip-bng-1, which doesn't seem to have this issue. If you send me the first 3 octets of your IP, I will try and track down your BNG and see if we can have someone see why this happens.

Unfortunately, the maid turned off my router sometime this week, so the pppoe session on my box at home didn't recover and everything has been running on a different account since yesterday, so my stats for sites aren't representative of uncapped. I swapped back too late tonight to see what it is like at peak, but at 22h30 I got 410kB/s from dl.google.com.

Can you post a result using winmtr when you have a problem again? There is one more thing we are planning to do that may help a bit, just need to get approval for a maintenance window to do it.

C:\Users\reactor>tracert www.mybroadband.co.za

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

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 10 ms 9 ms 8 ms ti-224-0-05.telkomadsl.co.za [105.224.0.5]
4 9 ms 9 ms 8 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
5 9 ms 8 ms 9 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
6 10 ms 8 ms 9 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
7 9 ms 9 ms 9 ms rrba-ip-lir-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.52.42]
8 9 ms 9 ms 8 ms rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za [1
96.43.25.138]
9 9 ms 9 ms 9 ms internet-solutions-gw.telkom-ipnet.co.za [196.25
.127.182]
10 10 ms 9 ms 9 ms ar2-rba-gi0-0.ip.isnet.net [196.26.0.33]
11 10 ms 9 ms 10 ms mi-za-rba-gsrpe2-gi1-1-0.ip.isnet.net [168.209.8
6.250]
12 * * * Request timed out.
13 30 ms 30 ms 30 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.12.151]
14 31 ms 30 ms 30 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
15 31 ms 32 ms 31 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
16 33 ms 34 ms 33 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
17 29 ms 28 ms 30 ms 197.242.89.170

Trace complete.

C:\Users\reactor>
Click to expand...

We hope to shorten this path soon ...
 
Grouter said:
So, breaking down my traceroute, can I assume I'm looking at:

1 <1 ms <1 ms <1 ms 192.168.1.1 -My Router

2 17 ms 17 ms 16 ms ti-224-4-01.telkomadsl.co.za [105.224.4.1] - Sedgefield Exchange
Click to expand...

esdw-ip-esr-3

I don't know the IPNet abbreviations that well, but maybe MickeyD can tell you what esdw is.

3 43 ms 41 ms 40 ms ti-226-0-246.telkomadsl.co.za [105.226.0.246] - Knysna
Click to expand...

$ dig +noall +answer @ns2.telkomsa.net -x 105.226.0.246
246.0.226.105.in-addr.arpa. 86400 IN PTR ipc-3-up.south.dsl.telkomsa.net.

(Cape Town)

4 41 ms 41 ms 41 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13] - George
Click to expand...

$ dig +noall +answer @ns2.telkomsa.net -x 105.226.0.13
13.0.226.105.in-addr.arpa. 86400 IN PTR ipc-aggr-1.south.dsl.telkomsa.net.

(Cape Town) The ~1ms hop means it's quite close.

5 40 ms 40 ms 40 ms wbs-ip-ll-1-wan.telkom-ipnet.co.za [165.165.221.153] - Barrack Street Cape Town

Oui?
Click to expand...

Correct. But even though it seems about 1ms, this hop is a few km away.

Code: 
#ping 165.165.221.153 source 105.226.0.13
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 165.165.221.153, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
 
Torrent speeds have been very low over the last few days during night time. Daytime browsing and streaming seem fine though.
 
ranger said:
Is this for KZN (location in your profile doesn't help)? Only select google services should be impacted im KZN at present (mainly Youtube videos), and the changes made in Gauteng should make it to the other regions soon if we see no problems.

If you mean other Google services (e.g. mail, search), there shouldn't be any problems. A traceroute to the specific service would help though
...
Click to expand...

Yeah, that was a fail on my part.

Im in JHB, and the problem is google search, gdrive, youtube, and gmail from what I have tested. I'll tracert next time it happens.
 
NZB downloads using news.saix were stuck on 0 kilobytes per second this morning at 06:30 when I checked on them. Also, over the past few days many a NZB has failed to download due to "not enough repair blocks" or "out of servers retention" despite it being 1 day old NZBs. Anybody shed any light on this?
 
Kaito said:
Torrent speeds have been very low over the last few days during night time. Daytime browsing and streaming seem fine though.
Click to expand...
What he said ^

I stayed up late and didn't see speeds rise beyond 140kb/s. (Normal is around 230)
It also dipped very low most of the time.

Speedtest is normal, as is tracert etc

My streaming has been on the low end, and online gaming has been bad.
 
ranger said:
The weird timeout on the 'ESR'/'BRAS' hop seems to happen on some BNGs.
Code: 
$ traceroute www.google.com
traceroute to www.google.com (74.125.233.114), 30 hops max, 60 byte packets
 1  ti-224-216-01.telkomadsl.co.za (105.224.216.1)  10.785 ms  13.041 ms  15.387 ms
 2  ti-224-0-06.telkomadsl.co.za (105.224.0.6)  22.487 ms  24.375 ms  26.597 ms
 3  ti-224-0-13.telkomadsl.co.za (105.224.0.13)  29.384 ms  31.507 ms  33.740 ms
 4  cen-pr-01-te7-22-vl2.net.telkomsa.net (105.187.249.98)  36.398 ms  40.023 ms  40.986 ms
 5  jb1-pr-01-te8-3.net.telkomsa.net (105.187.249.2)  45.167 ms  48.688 ms  49.793 ms
 6  jb1-google-gw.net.telkomsa.net (105.187.249.22)  52.080 ms  43.917 ms  45.138 ms
 7  72.14.239.129 (72.14.239.129)  44.132 ms  38.724 ms  40.033 ms
 8  jnb01s08-in-f18.1e100.net (74.125.233.114)  40.307 ms  39.028 ms  40.514 ms


$ mtr -rw www.google.com
Start: Thu Oct 16 23:05:41 2014
HOST: media                                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- ti-224-216-01.telkomadsl.co.za         0.0%    10   10.4  10.4  10.0  10.9   0.0
  2.|-- ti-224-0-06.telkomadsl.co.za           0.0%    10   13.8  14.1  13.6  15.2   0.0
  3.|-- ti-224-0-13.telkomadsl.co.za           0.0%    10   13.8  14.0  13.5  14.9   0.0
  4.|-- cen-pr-01-te7-22-vl2.net.telkomsa.net  0.0%    10   13.9  18.7  13.9  41.6   9.6
  5.|-- jb1-pr-01-te8-3.net.telkomsa.net       0.0%    10   15.7  15.4  14.9  16.4   0.3
  6.|-- jb1-google-gw.net.telkomsa.net         0.0%    10   14.7  14.6  14.4  14.7   0.0
  7.|-- 72.14.239.129                          0.0%    10   14.7  14.7  14.2  15.7   0.0
  8.|-- jnb01s08-in-f17.1e100.net              0.0%    10   15.5  15.2  14.0  16.0   0.0

I seem to be on tbnb-ip-bng-1, which doesn't seem to have this issue. If you send me the first 3 octets of your IP, I will try and track down your BNG and see if we can have someone see why this happens.

Unfortunately, the maid turned off my router sometime this week, so the pppoe session on my box at home didn't recover and everything has been running on a different account since yesterday, so my stats for sites aren't representative of uncapped. I swapped back too late tonight to see what it is like at peak, but at 22h30 I got 410kB/s from dl.google.com.

Can you post a result using winmtr when you have a problem again? There is one more thing we are planning to do that may help a bit, just need to get approval for a maintenance window to do it.



We hope to shorten this path soon ...
Click to expand...

Hi Ranger, doesnt matter what time of day, seem to always get no response from hop 2 (first external hop)
Code: 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                  DD-WRT -    0 |   47 |   47 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   10 |    0 |    0 |    0 |    0 |    0 |
|            ti-224-0-05.telkomadsl.co.za -    0 |   47 |   47 |    9 |   19 |   91 |   13 |
|            ti-224-0-06.telkomadsl.co.za -    0 |   47 |   47 |    8 |   11 |   52 |    9 |
|            ti-224-0-13.telkomadsl.co.za -    0 |   47 |   47 |    8 |   12 |   55 |    8 |
|   cen-pr-01-te7-22-vl2.net.telkomsa.net -    0 |   47 |   47 |    9 |   15 |   60 |   12 |
|        jb1-pr-01-te8-3.net.telkomsa.net -    0 |   47 |   47 |   15 |   20 |   62 |   15 |
|          jb1-google-gw.net.telkomsa.net -    0 |   47 |   47 |    9 |   18 |   58 |   16 |
|                           72.14.239.129 -    0 |   47 |   47 |   12 |   21 |   63 |   12 |
|               jnb01s08-in-f24.1e100.net -    0 |   47 |   47 |    9 |   15 |   55 |   14 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Last edited:
Im also seem to be having this issue.

C:\Users\Admin>tracert bbc.com

Tracing route to bbc.com [212.58.244.20]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 7 ms 7 ms 105-229-0-21.dsl.telkomsa.net [105.229.0.21]
4 8 ms 6 ms 7 ms 105-229-0-22.dsl.telkomsa.net [105.229.0.22]
5 46 ms 88 ms 126 ms 105-229-0-13.dsl.telkomsa.net [105.229.0.13]
6 106 ms 103 ms 110 ms ndn-ip-hsll-1.telkom-ipnet.co.za [165.165.233.24
9]
7 205 ms 205 ms 205 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
8 218 ms 312 ms 319 ms xe-0-1-0-19.r00.londen10.uk.bb.gin.ntt.net [83.2
31.146.245]
9 206 ms 206 ms 196 ms ae-7.r23.londen03.uk.bb.gin.ntt.net [129.250.6.5
4]
10 195 ms 196 ms 196 ms bbc-linx.pr01.rbsov.bbc.co.uk [195.66.236.103]
11 * * * Request timed out.
12 * * * Request timed out.
13 196 ms 196 ms 195 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
14 207 ms 207 ms 206 ms 132.185.255.149
15 298 ms 301 ms 196 ms fmt-vip71.telhc.bbc.co.uk [212.58.244.20]

Trace complete.
Click to expand...
 
Here:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 28 | 28 | 0 | 0 | 6 | 0 |
| No response from host - 100 | 5 | 0 | 0 | 0 | 0 | 0 |
| 105-229-0-21.dsl.telkomsa.net - 0 | 28 | 28 | 8 | 26 | 176 | 17 |
| 105-229-0-22.dsl.telkomsa.net - 0 | 28 | 28 | 13 | 20 | 29 | 13 |
| 105-229-0-13.dsl.telkomsa.net - 0 | 28 | 28 | 10 | 19 | 68 | 10 |
| ndn-ip-hsll-1.telkom-ipnet.co.za - 0 | 28 | 28 | 13 | 21 | 65 | 20 |
|lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za - 0 | 28 | 28 | 195 | 203 | 251 | 200 |
|xe-0-1-0-19.r00.londen10.uk.bb.gin.ntt.net - 0 | 27 | 27 | 207 | 214 | 248 | 212 |
| ae-6.r22.londen03.uk.bb.gin.ntt.net - 5 | 24 | 23 | 196 | 202 | 242 | 199 |
| bbc-linx.pr01.thdow.bbc.co.uk - 0 | 28 | 28 | 204 | 217 | 276 | 211 |
| No response from host - 100 | 5 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 5 | 0 | 0 | 0 | 0 | 0 |
| ae0.er01.telhc.bbc.co.uk - 0 | 28 | 28 | 196 | 205 | 241 | 212 |
| 132.185.255.149 - 0 | 28 | 28 | 196 | 198 | 239 | 198 |
| fmt-vip72.telhc.bbc.co.uk - 0 | 28 | 28 | 196 | 204 | 235 | 207 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Click to expand...
 
I don't normally use torrents, but I had to download something and the speeds are pathetic :mad:, averaging 94.8 kB/s over three days (three days to download 6.32 GB :mad:)

NNTP on the other hand works great ;)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X