Are you using Wifi? If not something just does not look right on your side. Can't say that is the cause but its certainly not right for the router hop.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Do you bet on sports?
Telkom Internet Capped/Uncapped User Feedback (Pt2)
- Thread starter bwana
- Start date
Are you using Wifi? If not something just does not look right on your side. Can't say that is the cause but its certainly not right for the router hop.
YouTube earlier was noticeably slower, but not a problem really. It was just, just keeping up.
NorthPole
Senior Member
Yep, ooops, *noob*.
Restarted the router seems better.
However now I suspect something is up as the new telkom jumps (ti not ti-224...).
C:\Users\Adrian>tracert www.facebook.com
Tracing route to www.facebook.com [31.13.90.81]
over a maximum of 30 hops:
1 3 ms 2 ms 2 ms login.router [10.0.0.2]
2 9 ms 10 ms 15 ms ti-224-148-01.telkomadsl.co.za [105.224.148.1]
3 71 ms 29 ms 14 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 14 ms 13 ms 13 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 15 ms 85 ms 26 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 190 ms 181 ms 193 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
7 218 ms 206 ms 202 ms ldn-b5-link.telia.net [62.115.35.89]
8 271 ms 199 ms 203 ms facebook-ic-307985-ldn-b5.c.telia.net [213.248.7
3.182]
9 * * * Request timed out.
10 198 ms 197 ms 228 ms msw01.06.lhr3.tfbnw.net [173.252.66.152]
11 199 ms 194 ms 229 ms www.facebook.com [31.13.90.81]
Trace complete.
C:\Users\***>tracert www.facebook.com
Tracing route to www.facebook.com [31.13.90.81]
over a maximum of 30 hops:
1 2 ms 2 ms 3 ms login.router [10.0.0.2]
2 10 ms 10 ms 11 ms ti-224-148-01.telkomadsl.co.za [105.224.148.1]
3 14 ms 13 ms 14 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 14 ms 13 ms 15 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 13 ms 15 ms 14 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 181 ms 182 ms 182 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
7 259 ms 203 ms 326 ms ldn-b5-link.telia.net [62.115.35.89]
8 199 ms 207 ms 199 ms facebook-ic-307985-ldn-b5.c.telia.net [213.248.7
3.182]
9 * * * Request timed out.
10 355 ms 321 ms 291 ms msw01.06.lhr3.tfbnw.net [173.252.66.152]
11 196 ms 195 ms 195 ms www.facebook.com [31.13.90.81]
Trace complete.
USING LAN CABLE
C:\Users\****>tracert speedtest.mybroadband.co.za
Tracing route to speedtest.mybroadband.co.za [196.10.98.18]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 9 ms 8 ms 8 ms ti-224-148-01.telkomadsl.co.za [105.224.148.1]
3 13 ms 12 ms 11 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 13 ms 12 ms 11 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 12 ms 12 ms 12 ms 105-187-249-98.dsl.telkomsa.net [105.187.249.98]
6 13 ms 12 ms 12 ms 105-187-249-2.dsl.telkomsa.net [105.187.249.2]
7 13 ms 14 ms 12 ms teraco.jb1.napafrica.net [196.46.25.200]
8 14 ms 14 ms 14 ms speedtest.mybroadband.co.za [196.10.98.18]
Trace complete.
USING WIFI
C:\Users\****>tracert speedtest.mybroadband.co.za
Tracing route to speedtest.mybroadband.co.za [196.10.98.18]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms login.router [10.0.0.2]
2 10 ms 9 ms 9 ms ti [105.224.148.1]
3 15 ms 14 ms 13 ms ti [105.224.0.6]
4 14 ms 13 ms 12 ms ti [105.224.0.13]
5 13 ms 13 ms 14 ms 105 [105.187.249.98]
6 41 ms 15 ms 13 ms 105 [105.187.249.2]
7 15 ms 15 ms 14 ms teraco.jb1.napafrica.net [196.46.25.200]
8 15 ms 14 ms 14 ms speedtest.mybroadband.co.za [196.10.98.18]
Trace complete.
C:\Users\****>tracert www.facebook.co.za
Tracing route to star.c10r.facebook.com [31.13.90.97]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms login.router [10.0.0.2]
2 11 ms 10 ms 10 ms ti [105.224.148.1]
3 14 ms 14 ms 13 ms ti [105.224.0.6]
4 14 ms 16 ms 13 ms ti [105.224.0.13]
5 13 ms 13 ms 14 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 181 ms 181 ms 181 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
7 203 ms 205 ms 206 ms ldn-b5-link.telia.net [62.115.35.89]
8 240 ms 198 ms 195 ms facebook-ic-307985-ldn-b5.c.telia.net [213.248.7
3.182]
9 * * * Request timed out.
10 194 ms 195 ms 196 ms msw01.07.lhr3.tfbnw.net [173.252.66.151]
11 201 ms 201 ms 201 ms www.facebook.com [31.13.90.97]
Trace complete.
C:\Users\****>tracert www.cnn.com
Tracing route to cnn-56m.gslb.vgtf.net [157.166.249.11]
over a maximum of 30 hops:
1 2 ms 1 ms 2 ms login.router [10.0.0.2]
2 9 ms 9 ms 9 ms ti [105.224.148.1]
3 14 ms 12 ms 14 ms ti [105.224.0.6]
4 14 ms 13 ms 13 ms ti [105.224.0.13]
5 14 ms 13 ms 13 ms 165.165.216.221
6 182 ms 181 ms 181 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
7 285 ms 203 ms 204 ms te3-7.ccr01.lon09.atlas.cogentco.com [149.6.98.7
3]
8 196 ms 197 ms 197 ms te0-7-0-1.ccr21.lon01.atlas.cogentco.com [130.11
7.0.153]
9 196 ms 197 ms 196 ms be2314.ccr21.lon13.atlas.cogentco.com [154.54.72
.253]
10 270 ms 270 ms 271 ms be2347.ccr21.jfk02.atlas.cogentco.com [154.54.27
.141]
11 285 ms 285 ms 285 ms be2148.ccr21.dca01.atlas.cogentco.com [154.54.31
.117]
12 291 ms 291 ms 291 ms be2168.ccr41.atl01.atlas.cogentco.com [154.54.31
.93]
13 293 ms 293 ms 293 ms be2034.ccr21.atl04.atlas.cogentco.com [154.54.6.
114]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
NorthPole
Senior Member
Hahaha, sorry just felt compelled to block something out
clearly failed.
clearly failed.Hahaha, sorry just felt compelled to block something out
Your names still there Adrian...
Check first tracert to facebook
NorthPole
Senior Member
I know, doesn't matter, lets call it a easter egg from me
MickeyD
RIP
All other scheduled DLs completed. Single torrent now (not even well seeded):
ranger
Expert Member
P2P is unshaped at 01h00. I had one large-ish torrent running last night, my bandwidth scheduling is currently configured as 8kB/s at normal times, and 400kB/s from 00h00 to 06h00.
As you can see, the bandwidth scheduling limit was hit immediately at 01h00.
I see that too, and often it only becomes unshaped much later, so why are you asking us to schedule downloads from 12AM?
It was also stated here that the overnight hours were extended to 7AM, but if you've taken off 1 hour (12- 1) what are we gaining?
ranger
Expert Member
Uh, no, it is always 01h00. It may be that on some days there is more demand.
Why must the zero-rating time match the p2p unshaping time? Note that we consider this (the need to have a specific time-based policy on p2p) a bug anyway, and will continue investigating (in conjunction with vendors) ways to remove it entirely, the way it was until January.
When NightSurfer was 00h00 to 06h00, p2p was unshaped from 01h00 to 07h00. With the NightSurfer change to 00h00 to 07h00, we couldn't extend p2p unshaping to 08h00, and didn't want to reduce it, so p2p unshaping is still 01h00 to 07h00.
There is no reason they have to be aligned, but there are a few good reasons not to align them. One reason is to see what the effect is of customer behavior because of NightSurfer, and what the effect of unshaping p2p is, seperately.
Yuu
Executive Member
Not sure anyone else, getting mega packet loss / intermittent access to all sites. Was trying to get into a game of GTAV and it was rather bad even though was logged into PSN. Changed to a backup account and it is great.
Let us know if anything abnormal this side ranger-san
?
@shanezn @ponder - any performance hits this morning guys?
/makes mental note to catchup on above discussion
Let us know if anything abnormal this side ranger-san
?@shanezn @ponder - any performance hits this morning guys?
/makes mental note to catchup on above discussion
MickeyD
RIP
Valid question, AntiGanda!
Thanks for the reply, ranger.
We learn something every day...
Thanks for the reply, ranger.
We learn something every day...
Does the shaping have to be so extreme? 0 kb/s for 2Meg mostly
Not sure anyone else, getting mega packet loss / intermittent access to all sites. Was trying to get into a game of GTAV and it was rather bad even though was logged into PSN. Changed to a backup account and it is great.
Let us know if anything abnormal this side ranger-san
@shanezn @ponder - any performance hits this morning guys?
/makes mental note to catchup on above discussion
Nope. All fine here. My kid was watching YouTube from about 7am till about 8.30am, and then I downloaded the 10.9.5 OS X update and all was running fine. Downloaded a bit more later, around 12pm (about 2GB) and all is still ok.
I find this rather weird as I get 50-100% line speed with torrents (generally 75-100%) in the shaping period but I also dont have a standard torrrent client/router setup when it comes to torrents. I've assisted others here before getting better torrent speeds as well.
eremos
Senior Member
We had a little incident with a tree branch falling on the line in our backyard on Thursday. Technicians came and fixed it on Friday, and everything was hunky dory until late this afternoon. Now I have terrible throughput and some packet loss but I'm not sure if it's related to the branch.
Reasons I think it might NOT be:
1. Things were working fine after they fixed it (I know, I know)
2. My SNR and attenuation are excellent
3. Only downstream traffic seems to be affected
Reasons it might be:
1. Nothing else has changed in the last few days
2. My Afrihost connection behaves the same way
Traceroute to saix.net:
I'll see how things look in the morning, but in the meantime, anyone else in Natal having issues?
Edit: Actually, based on the fact that my Afrihost account does pretty much the same thing, I'll just log a fault now.
Edit 2: Also, I picked up the phone and it's noisy. So just disregard this entire post.
Reasons I think it might NOT be:
1. Things were working fine after they fixed it (I know, I know)
2. My SNR and attenuation are excellent
3. Only downstream traffic seems to be affected
Reasons it might be:
1. Nothing else has changed in the last few days
2. My Afrihost connection behaves the same way
Traceroute to saix.net:
Code:
My traceroute [v0.85]
hex (0.0.0.0) Sun Oct 5 22:04:56 2014
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. my.router 0.0% 176 0.5 0.5 0.5 1.9 0.1
2. ti-224-124-01.telkomadsl.co.za 1.1% 176 13.7 22.4 10.5 347.7 36.9
3. 105.229.0.22 2.3% 176 13.6 23.3 12.7 297.3 35.6
4. 105.229.0.13 1.1% 176 17.8 25.0 12.2 275.6 35.7
5. ndn-ip-hsll-1.telkom-ipnet.co.za 1.1% 176 14.9 23.4 12.1 221.5 31.7
6. wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.z 1.7% 176 39.7 52.3 37.9 324.1 40.6
7. ???I'll see how things look in the morning, but in the meantime, anyone else in Natal having issues?
Edit: Actually, based on the fact that my Afrihost account does pretty much the same thing, I'll just log a fault now.
Edit 2: Also, I picked up the phone and it's noisy. So just disregard this entire post.
Last edited:
Just happened now, started at around 8.30am until around 8.40am. Here are both during and post browsing failure for mybb and youtube, again, only happens on certain site like mybb, google and youtube (probably many more that I don't visit so am unaware of them), others are fine
8.35am during
Traceroute has started…
traceroute to mybroadband.co.za (197.242.89.170), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 0.657 ms 0.366 ms 0.300 ms
2 ti-224-208-01.telkomadsl.co.za (105.224.208.1) 10.031 ms 9.346 ms 10.262 ms
3 ti-224-0-06.telkomadsl.co.za (105.224.0.6) 13.193 ms 12.066 ms 11.789 ms
4 ti-224-0-13.telkomadsl.co.za (105.224.0.13) 33.093 ms 12.589 ms 12.320 ms
5 165.165.216.221 (165.165.216.221) 11.927 ms 12.976 ms 12.561 ms
6 rrba-ip-lir-1-gig-5-0-0.telkom-ipnet.co.za (196.43.52.38) 12.757 ms 12.623 ms 12.573 ms
7 rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za (196.43.25.138) 12.557 ms 13.775 ms 13.703 ms
8 internet-solutions-gw.telkom-ipnet.co.za (196.25.46.90) 13.660 ms 12.542 ms 12.873 ms
9 ar2-rba-gi0-0.ip.isnet.net (196.26.0.33) 14.072 ms 12.357 ms 12.952 ms
10 mi-za-rba-gsrpe2-gi1-1-0.ip.isnet.net (168.209.86.250) 13.372 ms 12.601 ms 13.167 ms
11 * * *
12 core.gp-cn-het-mee-1.to.gp-mr-vod-mee-1.dfa.p2p.10g.za.africainx.net (41.84.12.151) 32.714 ms 31.976 ms 32.024 ms
13 41-66-132-246-f6.het001-cpe-1-to-gp-cn-het-mee-1.africainx.net (41.66.132.246) 32.281 ms 36.782 ms 32.516 ms
14 core-access-switch1.jnb1.host-h.net (197.189.193.1) 34.788 ms 33.027 ms 33.206 ms
15 row-access-switch1-row3-4.jnb1.host-h.net (197.189.193.36) 38.942 ms 38.176 ms 34.787 ms
16 197.242.89.170 (197.242.89.170) 34.429 ms 34.101 ms 33.824 ms
Traceroute has started…
traceroute: Warning: youtube.com has multiple addresses; using 74.125.233.2
traceroute to youtube.com (74.125.233.2), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 0.747 ms 0.419 ms 0.313 ms
2 ti-224-208-01.telkomadsl.co.za (105.224.208.1) 10.675 ms 10.888 ms 10.213 ms
3 ti-224-0-06.telkomadsl.co.za (105.224.0.6) 15.031 ms 12.702 ms 12.471 ms
4 ti-224-0-13.telkomadsl.co.za (105.224.0.13) 12.895 ms 12.553 ms 11.840 ms
5 105-187-249-98.dsl.telkomsa.net (105.187.249.98) 13.040 ms 12.584 ms 12.444 ms
6 105-187-249-2.dsl.telkomsa.net (105.187.249.2) 12.841 ms 13.244 ms 13.482 ms
7 105-187-249-22.dsl.telkomsa.net (105.187.249.22) 13.756 ms 13.841 ms 13.016 ms
8 72.14.237.239 (72.14.237.239) 13.442 ms 13.274 ms 14.132 ms
9 jnb01s07-in-f2.1e100.net (74.125.233.2) 13.718 ms 13.429 ms 13.124 ms
8.44am post
Traceroute has started…
traceroute to mybroadband.co.za (197.242.89.170), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 0.799 ms 0.422 ms 0.382 ms
2 ti-224-208-01.telkomadsl.co.za (105.224.208.1) 9.116 ms 10.294 ms 9.719 ms
3 ti-224-0-06.telkomadsl.co.za (105.224.0.6) 12.629 ms 12.441 ms 12.291 ms
4 ti-224-0-13.telkomadsl.co.za (105.224.0.13) 13.999 ms 12.860 ms 11.433 ms
5 165.165.216.221 (165.165.216.221) 13.172 ms 12.149 ms 12.224 ms
6 rrba-ip-lir-1-gig-5-0-0.telkom-ipnet.co.za (196.43.52.38) 12.144 ms 13.109 ms 13.254 ms
7 rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za (196.43.25.138) 13.235 ms 12.650 ms 13.210 ms
8 internet-solutions-gw.telkom-ipnet.co.za (196.25.46.90) 13.165 ms 12.949 ms 12.751 ms
9 ar2-rba-gi0-0.ip.isnet.net (196.26.0.33) 12.709 ms 13.114 ms 13.062 ms
10 mi-za-rba-gsrpe2-gi1-1-0.ip.isnet.net (168.209.86.250) 15.735 ms 13.521 ms 13.424 ms
11 * * *
12 core.gp-cn-het-mee-1.to.gp-mr-vod-mee-1.dfa.p2p.10g.za.africainx.net (41.84.12.151) 32.199 ms 31.957 ms 32.514 ms
13 41-66-132-246-f6.het001-cpe-1-to-gp-cn-het-mee-1.africainx.net (41.66.132.246) 32.431 ms 32.286 ms 32.367 ms
14 core-access-switch1.jnb1.host-h.net (197.189.193.1) 33.097 ms 33.381 ms 32.973 ms
15 row-access-switch1-row3-4.jnb1.host-h.net (197.189.193.36) 37.925 ms 35.089 ms 37.052 ms
16 197.242.89.170 (197.242.89.170) 34.834 ms 34.001 ms 34.869 ms
Traceroute has started…
traceroute: Warning: youtube.com has multiple addresses; using 74.125.233.8
traceroute to youtube.com (74.125.233.8), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 0.854 ms 0.446 ms 0.330 ms
2 ti-224-208-01.telkomadsl.co.za (105.224.208.1) 10.198 ms 9.855 ms 9.246 ms
3 ti-224-0-06.telkomadsl.co.za (105.224.0.6) 12.672 ms 11.808 ms 11.864 ms
4 ti-224-0-13.telkomadsl.co.za (105.224.0.13) 13.247 ms 11.649 ms 11.914 ms
5 105-187-249-98.dsl.telkomsa.net (105.187.249.98) 12.441 ms 13.559 ms 11.872 ms
6 105-187-249-2.dsl.telkomsa.net (105.187.249.2) 13.344 ms 12.629 ms 14.121 ms
7 105-187-249-22.dsl.telkomsa.net (105.187.249.22) 13.401 ms 12.927 ms 13.046 ms
8 72.14.237.239 (72.14.237.239) 13.530 ms 13.839 ms 12.631 ms
9 jnb01s07-in-f8.1e100.net (74.125.233.8) 13.198 ms 13.281 ms 12.302 ms