Telkom Internet Capped/Uncapped User Feedback (Pt2)

Latency ALL over the place this morning with TI. Where is it all going wrong, been like this for a while?!?!

anywhere between 800-2400ms latency
 
Looks normal here:
Code: 
[mick@house ~]$ mtr -rc 10 bbc.co.uk
Start: Mon Aug  3 08:39:43 2015
HOST: house                       Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- newcop                     0.0%    10    3.5   3.5   3.4   4.5   0.0
  2.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- wbs-ip-hsll-2-gi3-1-0-vl1  0.0%    10   26.7  28.7  26.7  35.3   3.1
  4.|-- ipc-4-up.south.dsl.telkom  0.0%    10   33.5  36.3  33.5  46.7   5.3
  5.|-- ipc-aggr-2.south.dsl.telk  0.0%    10   26.7  27.3  26.4  30.8   1.1
  6.|-- 165.165.214.213            0.0%    10   33.4  33.9  33.2  37.3   1.1
  7.|-- lon-ip-dir-telecity-pos-1  0.0%    10  171.0 181.0 170.9 204.2  13.0
  8.|-- ldn-b5-link.telia.net      0.0%    10  171.0 178.9 170.6 202.1  11.5
  9.|-- atos-ic-151907-ldn-b5.c.t  0.0%    10  201.1 188.5 177.5 206.7  11.4
 10.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- ae0.er01.telhc.bbc.co.uk   0.0%    10  170.9 174.2 170.9 185.4   5.8
 12.|-- 132.185.255.149            0.0%    10  172.0 172.4 171.4 176.7   1.4
 13.|-- fmt-vip71.telhc.bbc.co.uk  0.0%    10  170.9 171.3 170.9 172.0   0.0
[mick@house ~]$
 
Based in CPT, Northern Suburbs

Pinging bbc.co.uk [212.58.244.18] with 32 bytes of data:
Reply from 212.58.244.18: bytes=32 time=2938ms TTL=50
Reply from 212.58.244.18: bytes=32 time=2811ms TTL=50
Reply from 212.58.244.18: bytes=32 time=2874ms TTL=50
Reply from 212.58.244.18: bytes=32 time=2685ms TTL=50

Ping statistics for 212.58.244.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2685ms, Maximum = 2938ms, Average = 2827ms

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

1 <1 ms 2 ms <1 ms 192.168.1.1
2 2539 ms 2613 ms 2336 ms wblv-ip-bb-1.south.dsl.telkomsa.net [105.224.144.1]
3 2636 ms 2381 ms 2497 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 3372 ms 3078 ms 3018 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 2946 ms 3321 ms * wbs-ip-ll-1-wan.telkom-ipnet.co.za [165.165.221.153]
6 * * 3557 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.43.9.46]
7 * 3612 ms 3747 ms ldn-b5-link.telia.net [62.115.35.89]
8 * 3884 ms 3509 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.142]
9 * * * Request timed out.
10 2845 ms 2894 ms 3135 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 * 3584 ms 3570 ms 132.185.255.149
12 3791 ms * 3754 ms fmt-vip72.telhc.bbc.co.uk [212.58.244.18]

Trace complete.

Switching over to different ISP's, Afrihost or FNB, it all systems go!
 
Tjoker said:
Switching over to different ISP's, Afrihost or FNB, it all systems go!
Click to expand...
Still fine here in PE, obviously a localized problem looking at your first hop. Maybe a PM to TelkomZA might get things sorted.

Could also be DNS settings - are you using TI's default DNS or custom?
 
Last edited:
Tjoker said:
1 <1 ms 2 ms <1 ms 192.168.1.1
2 2539 ms 2613 ms 2336 ms wblv-ip-bb-1.south.dsl.telkomsa.net [105.224.144.1]
3 2636 ms 2381 ms 2497 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 3372 ms 3078 ms 3018 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
Click to expand...

This link is currently running at 75%. There is no shaping occurring on our side at present. So assuming there isn't an issue on your side (e.g. something congesting your upstream), the problem thus cannot be on our side, but on the wholesale side between the high-speed leased line (105.226.0.5) and the broadband router (wblv-ip-bb-1). I don't know if any other ISPs are on the same high speed leased line, but I know most are on a different one in the same site (we were moved from it when we needed more capacity).
 
ranger said:
This link is currently running at 75%. There is no shaping occurring on our side at present. So assuming there isn't an issue on your side (e.g. something congesting your upstream), the problem thus cannot be on our side, but on the wholesale side between the high-speed leased line (105.226.0.5) and the broadband router (wblv-ip-bb-1). I don't know if any other ISPs are on the same high speed leased line, but I know most are on a different one in the same site (we were moved from it when we needed more capacity).
Click to expand...

You may want Wholesale to check that link as plenty of TI folks in the Western Cape are complaining.
 
Stickfigure said:
Dial up is faster than this ****

tracert www.google.co.za

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 1443 ms 1062 ms * ipc-2-up.south.dsl.telkomsa.net [105.226.0.22]
5 1044 ms * * ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 * 1304 ms 1694 ms blv-pr-01-be200-vl1.net.telkomsa.net [105.226.0.53]
7 * * * Request timed out.
8 458 ms 545 ms 601 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
9 539 ms 542 ms 1078 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]
10 1062 ms 1026 ms 1582 ms 72.14.237.239
11 269 ms 291 ms 325 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

tracert www.mybroadband.co.za

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 965 ms 682 ms 338 ms wbs-ip-hsll-2-gi4-0-0-vl102.telkom-ipnet.co.za [105.226.0.21]
4 169 ms 677 ms 115 ms ipc-2-up.south.dsl.telkomsa.net [105.226.0.22]
5 551 ms 193 ms 359 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 683 ms 1106 ms 361 ms blv-pr-01-be200-vl1.net.telkomsa.net [105.226.0.53]
7 * * * Request timed out.
8 496 ms 875 ms 684 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
9 304 ms 339 ms 456 ms cloudflare.jb1.napafrica.net [196.46.25.198]
10 657 ms 147 ms 176 ms 141.101.112.56

Trace complete.
Click to expand...

@ranger
We checked his line and did every test available. His line is near perfect. His exchange uplink was at 19% so it is not congested. You may want to get Wholesale to check your leased links.
 
Traceroute has started…

traceroute: Warning: mybroadband.co.za has multiple addresses; using 190.93.240.55
traceroute to mybroadband.co.za (190.93.240.55), 64 hops max, 72 byte packets
1 router.asus.com (192.168.1.1) 5.048 ms 0.833 ms 0.737 ms
2 rrba-ip-bng-1.north.dsl.telkomsa.net (105.224.208.1) 445.384 ms 409.279 ms 409.754 ms
3 ipc-1-up.north.dsl.telkomsa.net (105.224.0.6) 511.645 ms 409.393 ms 307.065 ms
4 ipc-aggr-1.north.telkomsa.net (105.224.0.13) 409.606 ms 408.906 ms 309.032 ms
5 jb1-pr-01-te8-3.net.telkomsa.net (105.187.249.2) 141.189 ms 160.290 ms 310.758 ms
6 cloudflare.jb1.napafrica.net (196.46.25.198) 312.066 ms 259.691 ms 349.408 ms
7 190.93.240.55 (190.93.240.55) 307.339 ms 226.447 ms 284.572 ms

:( Had this yesterday too, which passed after about 30min... but is back again
 
Don't run trace routes to mybroadband... There is mitigation in place to ward off DDoS attacks and it messes up your target address.
 
MickeyD said:
Don't run trace routes to mybroadband... There is mitigation in place to ward off DDoS attacks and it messes up your target address.
Click to expand...

Ah... well, fine again... next time will go somewhere else:)

Traceroute has started…

traceroute: Warning: mybroadband.co.za has multiple addresses; using 190.93.241.55
traceroute to mybroadband.co.za (190.93.241.55), 64 hops max, 72 byte packets
1 router.asus.com (192.168.1.1) 1.311 ms 0.819 ms 0.658 ms
2 rrba-ip-bng-1.north.dsl.telkomsa.net (105.224.208.1) 6.645 ms 7.174 ms 6.614 ms
3 ipc-1-up.north.dsl.telkomsa.net (105.224.0.6) 9.880 ms 9.699 ms 11.756 ms
4 ipc-aggr-1.north.telkomsa.net (105.224.0.13) 10.457 ms 9.519 ms 9.489 ms
5 jb1-pr-01-te8-3.net.telkomsa.net (105.187.249.2) 10.083 ms 10.025 ms 9.735 ms
6 cloudflare.jb1.napafrica.net (196.46.25.198) 9.920 ms 12.763 ms 33.883 ms
7 190.93.241.55 (190.93.241.55) 12.472 ms 10.053 ms 10.987 ms



Bah... spoke too soon:(

Traceroute has started…

traceroute: Warning: mybroadband.co.za has multiple addresses; using 190.93.243.55
traceroute to mybroadband.co.za (190.93.243.55), 64 hops max, 72 byte packets
1 router.asus.com (192.168.1.1) 4.966 ms 0.860 ms 0.855 ms
2 rrba-ip-bng-1.north.dsl.telkomsa.net (105.224.208.1) 444.924 ms 408.659 ms 307.719 ms
3 ipc-1-up.north.dsl.telkomsa.net (105.224.0.6) 306.538 ms 409.582 ms 409.307 ms
4 ipc-aggr-1.north.telkomsa.net (105.224.0.13) 409.656 ms 511.768 ms 307.230 ms
5 jb1-pr-01-te8-3.net.telkomsa.net (105.187.249.2) 307.031 ms 409.724 ms 409.129 ms
6 cloudflare.jb1.napafrica.net (196.46.25.198) 409.533 ms 511.551 ms 409.602 ms
7 190.93.243.55 (190.93.243.55) 409.538 ms 408.886 ms 409.467 ms
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X