Sign up with Googlerudirautenbach
Senior Member
- Joined
- Mar 17, 2007
- Messages
- 619
Tried something different tonight. Using the tracert command, I traced the routes to two web addresses, one local (www.mybroadband.co.za) and one international (www.speedtest.net). There is a significant difference in the number of hops before reaching final destination between iBurst and MTN. A quick summary follows, although I have two text files with the data copied from the command prompt screens.
MTN to www.mybroadband.co.za
Hops : 16
Total Time (ms) : 4401
MTN to www.speedtest.net
Hops : 19
Total Time (ms) : 7747
iBurst to www.mybroadband.co.za
Hops : 9
Total Time (ms) : 674 ms
iBurst to www.speedtest.net
Hops : 17
Total Time (ms) : 3393 ms
Now I am not a TCPIP expert, but my common sense tells me that MTN SP's routing to both international and local addresses is not optimised at all, which could contribute to our common experiences of slow connections.
Perhaps someone more knowledgable could comment and assist with the interpretation of the results.
Rudi
PS read the post in the ADSL section on routing, I wonder if we could give it a try too?
MTN to www.mybroadband.co.za
Hops : 16
Total Time (ms) : 4401
MTN to www.speedtest.net
Hops : 19
Total Time (ms) : 7747
iBurst to www.mybroadband.co.za
Hops : 9
Total Time (ms) : 674 ms
iBurst to www.speedtest.net
Hops : 17
Total Time (ms) : 3393 ms
Now I am not a TCPIP expert, but my common sense tells me that MTN SP's routing to both international and local addresses is not optimised at all, which could contribute to our common experiences of slow connections.
Perhaps someone more knowledgable could comment and assist with the interpretation of the results.
Rudi
PS read the post in the ADSL section on routing, I wonder if we could give it a try too?