Telkom Internet Uncapped User Feedback.

Status
Not open for further replies.
slight improvement now. 1.2 mbps. still shocking when compare to fnb. (my line syncs at 6mbps - for anyone wondering why the fnb is so quick)
 
iceman23 said:
slight improvement now. 1.2 mbps. still shocking when compare to fnb. (my line syncs at 6mbps - for anyone wondering why the fnb is so quick)
Click to expand...

Please post a traceroute. We believe all problems in our Cape Town site are resolved (you will see 105.226.0.* in the first few hops of the traceroute).

We are finalising new links for the Gauteng site, where Gauteng and KZN and some other regions are served from via separate links (105.224.0.* and 105.228.0.*), and we believe those links should be up and carrying traffic by early Saturday morning. The link carrying traffic to 105.228.0.* is running very close to capacity and may be congesting from time to time. The link carrying traffic to 105.224.0.* seems ok for now.
 
ranger said:
Please post a traceroute. We believe all problems in our Cape Town site are resolved (you will see 105.226.0.* in the first few hops of the traceroute).

We are finalising new links for the Gauteng site, where Gauteng and KZN and some other regions are served from via separate links (105.224.0.* and 105.228.0.*), and we believe those links should be up and carrying traffic by early Saturday morning. The link carrying traffic to 105.228.0.* is running very close to capacity and may be congesting from time to time. The link carrying traffic to 105.224.0.* seems ok for now.
Click to expand...

Will this finally solve the latency problems in games?It's been 10 days now that I cannot use my account for online gaming,although latency has improved the last few days to the point where i'm getting 300-400ms(not the ridiculous 1000+ms anymore)it is not the desired 200-210 i used to have.
 
hi there, i am in pmb.

here is a traceroute to m$.

C:\Windows\system32>tracert www.microsoft.com

Tracing route to lb1.www.ms.akadns.net [64.4.11.42]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [10.13.0.1]
2 75 ms 18 ms 7 ms 224-164-1.dsl.subscriber.telkomsa.net [105.224.1
64.1]
3 60 ms 22 ms 40 ms 105.228.0.6
4 36 ms 63 ms 64 ms 105.228.0.13
5 317 ms 213 ms 184 ms rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.41]
6 380 ms 417 ms 496 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
7 * * * Request timed out.

timeouts from here on in...
 
iceman23 said:
hi there, i am in pmb.

here is a traceroute to m$.

C:\Windows\system32>tracert www.microsoft.com

Tracing route to lb1.www.ms.akadns.net [64.4.11.42]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [10.13.0.1]
2 75 ms 18 ms 7 ms 224-164-1.dsl.subscriber.telkomsa.net [105.224.1
64.1]
3 60 ms 22 ms 40 ms 105.228.0.6
4 36 ms 63 ms 64 ms 105.228.0.13
5 317 ms 213 ms 184 ms rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.41]
6 380 ms 417 ms 496 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
7 * * * Request timed out.

timeouts from here on in...
Click to expand...

Hi, Im not sure if you know this but there was cable stolen which cause major disruption... http://mybroadband.co.za/news/telec...eves-cause-major-disruption-to-thousands.html

This is probably this reason why you are getting the timeouts...
 
lol. I just started a usenet download and its at 430kbps...

No didn't actually know that. may explain it
 
Subways81 said:
Hopped over to FNB Connect and got 648KBps... Thanks Telkom!!
Click to expand...

This was happening to me most of last month and the free data I got from Afrihost and FNB connect really helped when I needed the internet because not only was my downloading down to speeds a 56kbps line used to get (yet Im paying for a 10Mbps line) but when I was browsing on the net there was a lot of lagging and pages loading slow.... so I echo, Thanks Telkom!
 
I hope i'm not jinxing myself again here, but my line is a lot better today. What ever changes Telkom and ranger are making, looks like things are starting to look up.

here my trace route from 7:35 this morning :

C:\>tracert bbc.co.uk

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 8 ms 8 ms 224-40-1.dsl.subscriber.telkomsa.net [105.224.40.1]
3 11 ms 10 ms 10 ms 224-0-6.dsl.subscriber.telkomsa.net [105.224.0.6]
4 11 ms 11 ms 11 ms 224-0-13.dsl.subscriber.telkomsa.net [105.224.0.13]
5 11 ms 12 ms 12 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.37]
6 180 ms 179 ms 179 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.43.9.46]
7 197 ms 198 ms 198 ms 93-126-245-83.packetexchange.net [83.245.126.93]
8 * * * Request timed out.
9 197 ms 197 ms 197 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
10 197 ms 196 ms 197 ms 132.185.255.156
11 207 ms 208 ms 206 ms www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Trace complete.

and now 1 at 10:00 :

C:\>tracert bbc.co.uk

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 9 ms 8 ms 224-40-1.dsl.subscriber.telkomsa.net [105.224.40.1]
3 57 ms 148 ms 57 ms 224-0-6.dsl.subscriber.telkomsa.net [105.224.0.6]
4 63 ms 64 ms 184 ms 224-0-13.dsl.subscriber.telkomsa.net [105.224.0.13]
5 73 ms 71 ms 72 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.37]
6 235 ms 255 ms 235 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
7 259 ms 258 ms 264 ms 93-126-245-83.packetexchange.net [83.245.126.93]
8 * * * Request timed out.
9 * * * Request timed out.
10 244 ms 278 ms 248 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 243 ms 243 ms 243 ms 132.185.255.140
12 336 ms 247 ms 338 ms www-vip.telhc.bbc.co.uk [212.58.251.195]

Trace complete.

So the third hop still goes up, but at least it is a good 100ms lower than what it was yesterday. And websites actually open without timing out.
 
Was also struggling with all protocols for the past month on both my lines.

Since yesterday my one line was running perfect; full speed on http, nttp, p2p and most importantly normal-ish latency.

Other line still buggered though:confused:
 
This is how the TI uncapped thread should be.
Quiet, with no complaints, or mostly no complaints.
Thx Ranger and the rest of the TI team.
 
C:\>tracert bbc.co.uk

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

1 1 ms <1 ms 1 ms 192.168.0.1
2 10 ms * 10 ms 224-116-1.dsl.subscriber.telkomsa.net [105.224.1
16.1]
3 152 ms 143 ms 142 ms 224-0-6.dsl.subscriber.telkomsa.net [105.224.0.6
]
4 136 ms 168 ms 135 ms 224-0-13.dsl.subscriber.telkomsa.net [105.224.0.
13]
5 142 ms 141 ms 142 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 332 ms 336 ms 321 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
7 322 ms 319 ms 320 ms 93-126-245-83.packetexchange.net [83.245.126.93]

8 * * * Request timed out.
9 * * * Request timed out.
10 330 ms 335 ms 335 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 338 ms 339 ms 332 ms 132.185.255.140
12 327 ms 329 ms 333 ms www-vip.telhc.bbc.co.uk [212.58.251.195]

Trace complete.
 
Hxx said:
C:\>tracert bbc.co.uk

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

1 1 ms <1 ms 1 ms 192.168.0.1
2 10 ms * 10 ms 224-116-1.dsl.subscriber.telkomsa.net [105.224.1
16.1]
3 152 ms 143 ms 142 ms 224-0-6.dsl.subscriber.telkomsa.net [105.224.0.6
]
4 136 ms 168 ms 135 ms 224-0-13.dsl.subscriber.telkomsa.net [105.224.0.
13]
5 142 ms 141 ms 142 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 332 ms 336 ms 321 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
7 322 ms 319 ms 320 ms 93-126-245-83.packetexchange.net [83.245.126.93]

8 * * * Request timed out.
9 * * * Request timed out.
10 330 ms 335 ms 335 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 338 ms 339 ms 332 ms 132.185.255.140
12 327 ms 329 ms 333 ms www-vip.telhc.bbc.co.uk [212.58.251.195]

Trace complete.
Click to expand...

Okay that is not so great. I will try in 30 minutes or so. I'm dl ubuntu 13.04 for the 9th time. The md5 hash is always wrong. :(
 
Hxx said:
C:\>tracert bbc.co.uk

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

1 1 ms <1 ms 1 ms 192.168.0.1
2 10 ms * 10 ms 224-116-1.dsl.subscriber.telkomsa.net [105.224.1
16.1]
3 152 ms 143 ms 142 ms 224-0-6.dsl.subscriber.telkomsa.net [105.224.0.6
]
4 136 ms 168 ms 135 ms 224-0-13.dsl.subscriber.telkomsa.net [105.224.0.
13]
5 142 ms 141 ms 142 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 332 ms 336 ms 321 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
7 322 ms 319 ms 320 ms 93-126-245-83.packetexchange.net [83.245.126.93]

8 * * * Request timed out.
9 * * * Request timed out.
10 330 ms 335 ms 335 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 338 ms 339 ms 332 ms 132.185.255.140
12 327 ms 329 ms 333 ms www-vip.telhc.bbc.co.uk [212.58.251.195]

Trace complete.
Click to expand...

We completed the transmission for the new IPC links this morning. Planning of the actual configuration of the links is being completed now, with the intention of doing the configuration tonight.
 
iceman23 said:
hi there, i am in pmb.

here is a traceroute to m$.

C:\Windows\system32>tracert www.microsoft.com

Tracing route to lb1.www.ms.akadns.net [64.4.11.42]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [10.13.0.1]
2 75 ms 18 ms 7 ms 224-164-1.dsl.subscriber.telkomsa.net [105.224.1
64.1]
3 60 ms 22 ms 40 ms 105.228.0.6
4 36 ms 63 ms 64 ms 105.228.0.13
5 317 ms 213 ms 184 ms rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.41]
6 380 ms 417 ms 496 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
7 * * * Request timed out.

timeouts from here on in...
Click to expand...

We found a problem on this IPC link (bandwidth was configured on the wholesale side with 10% less bandwidth than ordered). Our traffic management system was cpnfigured for more than 90% of the capacity of this link, resulting on congestion on the IPC.

Thay should have been fixed this morning.

Then, new links are planned to go live tonight, which should fix any remaining issues.
 
ranger said:
We found a problem on this IPC link (bandwidth was configured on the wholesale side with 10% less bandwidth than ordered). Our traffic management system was cpnfigured for more than 90% of the capacity of this link, resulting on congestion on the IPC.

Thay should have been fixed this morning.

Then, new links are planned to go live tonight, which should fix any remaining issues.
Click to expand...

Hopefully the high latency in online games too right?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X