Telkom Internet Capped/Uncapped User Feedback (Pt2)

retired · May 3, 2016

Sadly small town with no LTE towers yet and I am guessing a good few years away from fibre being installed.

Geoff.D · May 3, 2016

retired said:
Sadly small town with no LTE towers yet and I am guessing a good few years away from fibre being installed.

which small town? And how do the mobile operators connect their base stations to the network at the moment? Via Telkom provided links? It may be that a little more investigation is required before you automatically assume that a mobile connection will be better than what you have at the moment.

Grouter · May 3, 2016

I seem to remember "retired" is in Knysna...

20 Km away to the west here in Sedgefield we have no LTE, but ADSL services are good if you live in the town centre or Myoli Beach (which has it's own msan / isam, not sure which).

Knysna Municipality recently announced http://www.knysnaon.co.za/ , ( http://www.knysna.gov.za/weeklynews/knysna-leads-from-the-front-with-knysnaon-high-speed-broadband/ )but sadly the roadmap for deployment is woefully long, and Sedgefield has been promised only a lousy microwave link to Knysna as part of the project, so no direct FTTH as such. I foresee myself sticking with ADSL for some years to come.

retired · May 3, 2016

Yes Knysna it is. George has a couple of LTE towers but my contacts within Telkom here have indicated that its not on the horizon for us. Our mobile connection is via 3g or 4g. So far so good.

Geoff.D · May 3, 2016

So okay, what we need then is for @Retired to post some line stats for the ADSL service as per the diagnostics available on the ADSL modem, plus the results obtained when running Zertops line test routine. With these results we should be able to establish just how "bad" or "good" the ADSL connection is at the moment.

http://mybroadband.co.za/vb/showthr...eport-Tool?p=12372998&viewfull=1#post12372998

aapkop · May 3, 2016

I know everybody don't get good service from telkom.

This is what happened my line went down Sunday and reported the fault, in less than 24hrs it was fixed.

Was fixed before 10'o clock the confirmations only appeared at that times

Drunkard #1 · May 4, 2016

The **** is wrong with telkom's international speeds?

My usual 8Mbps to Jo'burg.
1Mbps to USA.

Been going to since last night! I'm not happy! I wanted to watch youtube last night!

Drunkard #1 · May 4, 2016

The **** is wrong with telkom's international speeds?

My usual 8Mbps to Jo'burg.
1Mbps to USA.

Been going to since last night! I'm not happy! I wanted to watch youtube last night!

WiseCrack · May 4, 2016

Have a look at your line speed on your router settings page. Mine changed from 5mb to 2mb and have been stuck like that ever since.

A3@MBB · May 4, 2016

Anyone having issues tonight? My line is crawling along at 8kb/s download.
Ping is also 300ms+ to google servers.
Paarl WC

Geoff.D · May 4, 2016

A3@MBB said:
Anyone having issues tonight? My line is crawling along at 8kb/s download.
Ping is also 300ms+ to google servers.
Paarl WC

This morning, results to google.co.za was 9 hops an in the region of 13 ms.

Right now, to the same destination IP address, over 10 hops is of the order of 70 ms. The increased delay is within Telkom's network by the looks of things.

The google IP address is 216.58.223.35

I presume you should be accessing a google server in CT?

Drunkard #1 · May 5, 2016

Excellent work telkom. Who wants fast internet anyway. </sarcasm>

Drunkard #1 · May 5, 2016

Excellent work telkom. Who wants fast internet anyway. </sarcasm>

View attachment 359830

Geoff.D · May 5, 2016

last night there were known network issues experienced by many, so a once off speedtest while illustrating that a fault condition existed does not mean permanent bad service ......

Just that last night there were problems.

Networks go down, they do fail at times and they get fixed .....

Drunkard #1 · May 5, 2016

daniellgr said:
last night there were known network issues experienced by many, so a once off speedtest while illustrating that a fault condition existed does not mean permanent bad service ......

Just that last night there were problems.

Networks go down, they do fail at times and they get fixed .....

Look up. Second morning in a row.

Drunkard #1 · May 5, 2016

daniellgr said:
last night there were known network issues experienced by many, so a once off speedtest while illustrating that a fault condition existed does not mean permanent bad service ......

Just that last night there were problems.

Networks go down, they do fail at times and they get fixed .....

Look up. Second morning in a row.

Geoff.D · May 5, 2016

I would be very interested in a tracert done from your location. Here is the one I did this morning.

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

1 1 ms 1 ms 1 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 * 12 ms 13 ms ipc-up-2.north.telkomsa.net [105.228.0.6]
5 12 ms 12 ms 11 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
6 13 ms 13 ms 13 ms jb1-pr-02-te0-1-0.net.telkomsa.net [105.187.249.2]
7 13 ms 13 ms 13 ms cloudflare.jb1.napafrica.net [196.46.25.198]
8 13 ms 13 ms 13 ms 104.20.72.110

For example, why do you get so many double posts happening?

Drunkard #1 · May 5, 2016

Code:

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

  1    <1 ms    <1 ms    <1 ms  router [192.168.88.1]
  2     *        *        *     Request timed out.
  3     *       11 ms    10 ms  ipc-3-up.north.dsl.telkomsa.net [105.224.x.xx]
  4    10 ms     8 ms    10 ms  ipc-up-2.north.telkomsa.net [105.228.0.6]
  5    10 ms     9 ms     9 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6    10 ms    10 ms    10 ms  jb1-pr-02-te0-1-0.net.telkomsa.net [105.187.249.2]
  7    11 ms    11 ms    11 ms  cloudflare.jb1.napafrica.net [196.46.25.198]
  8    10 ms    10 ms    10 ms  104.20.71.110

Trace complete.

Who knows about the double posts. I can't delete them for some reason.

Anyway local is fine. International is forked.

Code:

Tracing route to [url]www.amazon.com[/url] [54.239.25.208]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router [192.168.88.1]
  2     *        *        *     Request timed out.
  3    56 ms    56 ms    55 ms  ipc-3-up.north.dsl.telkomsa.net [105.224.x.xx]
  4    55 ms    54 ms    53 ms  ipc-3-up.north.dsl.telkomsa.net [105.224.0.50]
  5    11 ms    10 ms    10 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6    10 ms    10 ms    10 ms  cen-pr-02-be200-vl1.net.telkomsa.net [105.228.0.17]
  7    11 ms    11 ms    10 ms  rrba-ip-hsll-2-wan.telkom-ipnet.co.za [196.25.166.225]
  8   174 ms   177 ms   173 ms  196.43.9.86
  9   190 ms   191 ms   190 ms  ldn-b5-link.telia.net [62.115.35.89]
 10   190 ms   191 ms   198 ms  ldn-bb2-link.telia.net [80.91.246.146]
 11   261 ms   262 ms   262 ms  ash-bb4-link.telia.net [213.248.65.210]
 12   263 ms   262 ms   265 ms  ash-b1-link.telia.net [213.155.130.59]
 13   262 ms   263 ms   263 ms  vadata-ic-157232-ash-bb1.c.telia.net [62.115.9.66]
 14   204 ms   277 ms   291 ms  54.239.108.38
 15   261 ms   262 ms   260 ms  54.239.108.61
 16   262 ms     *      260 ms  205.251.245.230
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *      278 ms     *     205.251.245.230
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

ranger · May 6, 2016

Drunkard #1 said:

Code:

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

  1    <1 ms    <1 ms    <1 ms  router [192.168.88.1]
  2     *        *        *     Request timed out.
  3     *       11 ms    10 ms  ipc-3-up.north.dsl.telkomsa.net [105.224.x.xx]
  4    10 ms     8 ms    10 ms  ipc-up-2.north.telkomsa.net [105.228.0.6]
  5    10 ms     9 ms     9 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6    10 ms    10 ms    10 ms  jb1-pr-02-te0-1-0.net.telkomsa.net [105.187.249.2]
  7    11 ms    11 ms    11 ms  cloudflare.jb1.napafrica.net [196.46.25.198]
  8    10 ms    10 ms    10 ms  104.20.71.110

Trace complete.

Who knows about the double posts. I can't delete them for some reason.

Anyway local is fine. International is forked.

Code:

Tracing route to [url]www.amazon.com[/url] [54.239.25.208]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router [192.168.88.1]
  2     *        *        *     Request timed out.
  3    56 ms    56 ms    55 ms  ipc-3-up.north.dsl.telkomsa.net [105.224.x.xx]
  4    55 ms    54 ms    53 ms  ipc-3-up.north.dsl.telkomsa.net [105.224.0.50]
  5    11 ms    10 ms    10 ms  ipc-aggr-1.north.telkomsa.net [105.224.0.13]
  6    10 ms    10 ms    10 ms  cen-pr-02-be200-vl1.net.telkomsa.net [105.228.0.17]
  7    11 ms    11 ms    10 ms  rrba-ip-hsll-2-wan.telkom-ipnet.co.za [196.25.166.225]
  8   174 ms   177 ms   173 ms  196.43.9.86
  9   190 ms   191 ms   190 ms  ldn-b5-link.telia.net [62.115.35.89]
 10   190 ms   191 ms   198 ms  ldn-bb2-link.telia.net [80.91.246.146]
 11   261 ms   262 ms   262 ms  ash-bb4-link.telia.net [213.248.65.210]
 12   263 ms   262 ms   265 ms  ash-b1-link.telia.net [213.155.130.59]
 13   262 ms   263 ms   263 ms  vadata-ic-157232-ash-bb1.c.telia.net [62.115.9.66]
 14   204 ms   277 ms   291 ms  54.239.108.38
 15   261 ms   262 ms   260 ms  54.239.108.61
 16   262 ms     *      260 ms  205.251.245.230
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *      278 ms     *     205.251.245.230
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Please test with mtr or winmtr or maybe pingplotter. The intetational latency looks ok (190ms to London is acceptable), but the 50ms to where the IPC terminates on our side is not. The fact that the latency on hops after that is lower may indicate that the latency is not stable, but to see where it is you need to be testing all the hops at the same time (which traceroute doesn't do, but mtr and winmtr and maybe pingplotter - which I haven't used much - do).

There have been no real issues on our side this week. There was transmission failure last week Friday (29 April) that affected Gauteng resulting in slow response from 09h00 to 14h00.

alternate · May 6, 2016

No connectivity on two Telkom Internet accounts. Other ISPs working fine in Stellenboch.

Join the MyBroadband community

Get started

Telkom Internet Capped/Uncapped User Feedback (Pt2)

Well-Known Member

Honorary Master

Executive Member

Well-Known Member

Honorary Master

Expert Member

Expert Member

Expert Member

Expert Member

Expert Member

Honorary Master

Expert Member

Expert Member

Honorary Master

Expert Member

Expert Member

Honorary Master

Expert Member

Expert Member

Expert Member