High Latency - Congestion?

[AviD]

High latency during evening period the last week.
Not sure if it is congestion or another issue.Line stats seems fine and tested multiple ISPs.

Usually anywhere from 5pm to 10pm, strange thing is that the download speeds were fine the first few nights but seems to have dropped to half the previous two nights.

Line stats
Downstream
Data Rate(Kbps): 4096
Noise Margin: 12.0
Output power: 14.8
Attenuation: 30.0

Upstream
Data Rate(Kbps): 512
Noise Margin: 14.0
Output power: 5.4
Attenuation: 14.0

10:19 PM 8/5/2015

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

1 <1 ms <1 ms <1 ms 192.168.2.1
2 303 ms 304 ms 326 ms 41-133-76-1.dsl.mweb.co.za [41.133.76.1]
3 388 ms 380 ms 368 ms 197-80-96-210.jhb.mweb.co.za [197.80.96.210]
4 292 ms 322 ms 338 ms vl92.vic-hscore-1.optinet.net [197.80.2.1]
5 425 ms 391 ms 361 ms 11.te0-0-0-2.vic-p-1.optinet.net [197.80.5.225]
6 466 ms 462 ms 445 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
7 472 ms 498 ms 475 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
8 473 ms 447 ms 427 ms 196.28.178.66
9 435 ms 436 ms 435 ms cte-core-sw2.vwol.net [196.41.144.35]
10 424 ms 424 ms 593 ms www.mweb.co.za [196.2.63.110]

Trace complete.

10:20 PM 8/5/2015

Tracing route to www.bbc.net.uk [212.58.246.92]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 373 ms 384 ms 410 ms 41-133-76-1.dsl.mweb.co.za [41.133.76.1]
3 341 ms 366 ms 377 ms 197-80-96-162.jhb.mweb.co.za [197.80.96.162]
4 403 ms 408 ms 399 ms vl92.vic-hscore-1.optinet.net [197.80.2.1]
5 627 ms 592 ms 583 ms 11.te0-0-0-2.vic-p-1.optinet.net [197.80.5.225]
6 591 ms 605 ms 565 ms s2-po0-3-2-0.thd-p-2.optinet.net [197.80.5.7]
7 552 ms 569 ms 610 ms be-2-778-thd-up-2.optinet.net [176.67.177.148]
8 624 ms 628 ms 628 ms xe-10-1-3.edge4.London1.Level3.net [212.113.14.121]
9 621 ms 636 ms 570 ms BBC-TECHNOL.edge4.London1.Level3.net [212.113.14.222]
10 * * * Request timed out.
11 * * * Request timed out.
12 524 ms 586 ms 571 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
13 580 ms 579 ms 524 ms 132.185.255.165
14 579 ms 510 ms 591 ms bbc-vip013.cwwtf.bbc.co.uk [212.58.246.92]

Trace complete.

10:28 PM 8/5/2015

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

1 <1 ms <1 ms <1 ms 192.168.2.1
2 352 ms 321 ms 332 ms 41-133-76-1.dsl.mweb.co.za [41.133.76.1]
3 391 ms 354 ms 342 ms 197-80-96-210.jhb.mweb.co.za [197.80.96.210]
4 395 ms 377 ms 363 ms vl92.vic-hscore-1.optinet.net [197.80.2.1]
5 355 ms 382 ms 378 ms 11.te0-0-0-2.vic-p-2.optinet.net [197.80.5.226]
6 427 ms 403 ms 410 ms 102.te0-0-0.vic-pr-1.optinet.net [197.80.7.37]
7 316 ms 330 ms 322 ms 197-80-97-21.jhb.mweb.co.za [197.80.97.21]
8 357 ms 325 ms 339 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [196.43.25.137]
9 334 ms 385 ms 403 ms 196.43.51.74
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
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 * * * Request timed out.
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.

10:31 PM 8/5/2015

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.2.1
2 327 ms 315 ms 291 ms 41-133-76-1.dsl.mweb.co.za [41.133.76.1]
3 355 ms 357 ms 376 ms 197-80-96-162.jhb.mweb.co.za [197.80.96.162]
4 448 ms 399 ms 391 ms vl92.vic-hscore-1.optinet.net [197.80.2.1]
5 358 ms 354 ms 297 ms 11.te0-0-0-2.vic-p-2.optinet.net [197.80.5.226]
6 430 ms 505 ms 547 ms 202.bu-ether5.vic-pe-2.optinet.net [197.80.7.103]
7 533 ms 553 ms 517 ms bu-ether1.tis-pe-2.optinet.net [197.80.4.9]
8 475 ms 452 ms 381 ms bu-ether2.tis-pe-1.optinet.net [197.80.4.252]
9 348 ms 336 ms 368 ms 197-80-4-195.jhb.mweb.co.za [197.80.4.195]
10 444 ms 427 ms 527 ms africainx.jb1.napafrica.net [196.46.25.135]
11 483 ms 443 ms 414 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
12 435 ms 432 ms 430 ms 141.101.112.56

Trace complete.

 

[AviD]

Returns to normal later at night and normal during the day

12:20 AM 8/9/2015

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

1 <1 ms <1 ms <1 ms 192.168.2.1
2 8 ms 7 ms 7 ms dsl-197-245-6-1.voxdsl.co.za [197.245.6.1]
3 9 ms 10 ms 9 ms 41.193.3.101
4 9 ms 8 ms 9 ms 41.193.3.102
5 9 ms 9 ms 9 ms 196.41.12.0
6 10 ms 10 ms 10 ms 41.193.32.137
7 10 ms 10 ms 10 ms 41.193.32.198
8 11 ms 10 ms 10 ms 41.193.119.22
9 11 ms 11 ms 11 ms mweb.jb1.napafrica.net [196.46.25.145]
10 30 ms 30 ms 31 ms te0-7-0-3.vic-p-2.optinet.net [197.80.7.98]
11 32 ms 32 ms 33 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
12 29 ms 28 ms 34 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
13 31 ms 28 ms 28 ms 196.28.178.66
14 30 ms 29 ms 28 ms cte-core-sw2.vwol.net [196.41.144.35]
15 29 ms 29 ms 30 ms www.mweb.co.za [196.2.63.110]

Trace complete.


12:22 AM 8/9/2015
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 7 ms 7 ms 7 ms 41-133-76-1.dsl.mweb.co.za [41.133.76.1]
3 9 ms 9 ms 9 ms 197-80-96-210.jhb.mweb.co.za [197.80.96.210]
4 10 ms 9 ms 9 ms vl92.vic-hscore-1.optinet.net [197.80.2.1]
5 104 ms 103 ms 107 ms 11.te0-0-0-2.vic-p-1.optinet.net [197.80.5.225]
6 113 ms 119 ms 106 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
7 77 ms 71 ms 64 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
8 46 ms 41 ms 45 ms 196.28.178.66
9 28 ms 28 ms 28 ms cte-core-sw2.vwol.net [196.41.144.35]
10 79 ms 69 ms 67 ms www.mweb.co.za [196.2.63.110]

Trace complete.

 

[HavocXphere]

Yup. The exchange is fkd.

Very little you can do about it unfortunately.

From experience, its likely to get worse...a semi-congested exchange thats screwed at certain times turns into an exchange thats 24/7 screwed. That being said if its that fk'd then its likely on Telkom's upgrade plan already. They're slow but they aren't oblivious.

 

[ghostR]

Certainly looks like an exchange congestion issue.

 

[AviD]

Thanks for the replies.Ugghhh,had hope that it would be something else.

 

[MWEBHelp]

Hi AviD, following our conversation on Twitter, a fault was logged to Telkom for you so that they can investigate further.

Call Ref: 1878306
Fault Ref: 47BRK090815

 

[AviD]

Thanks again MWEB Guy