- Joined
- Oct 9, 2014
- Messages
- 7,265
- Reaction score
- 6
Here is the trace. The trace shows that there is congestion at the exchange. Afrihost, did send technicians to my premises that is 400m away from the Meyerspark exchange, but they cant find problems on my line at home. I don't know what is happening with my line inside the exchange building. I have trailed a Telkom bakkie to the exchange and asked the guy if he can check my port, he said that he will.He has written down my line number and cell, still my latency is pathetic.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Melvin>tracert google.co.za
Tracing route to google.co.za [74.125.230.119]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 339 ms 332 ms 332 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
3 316 ms 289 ms 293 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
4 348 ms 312 ms 309 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 282 ms 263 ms 280 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 342 ms 331 ms 367 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 512 ms 494 ms 500 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
8 547 ms 543 ms 561 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 468 ms 462 ms 460 ms ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.203]
10 542 ms 567 ms 584 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.13]
11 589 ms 572 ms 552 ms 209.85.255.76
12 574 ms * 530 ms 72.14.238.185
13 515 ms 513 ms 530 ms lhr14s24-in-f23.1e100.net [74.125.230.119]
Trace complete.
C:\Users\Melvin>
Telkom is very hesitant with actually taking active measures to improve Exchange Congestion, as they have very specific upgrade schedules and cycles which they follow.
I do hope though that we can make some positive steps to at least improve your latency from its current levels.