international/local

This is interesting lowest pings i have seen to google.com on adsl 270 - 310ms BUT still about 30% packet loss.
 
I think their routing shaped adsl over a portion of the unshaped network. While fixing the f472up ;p
 
Please post tracerts to www.yahoo.com in this thread. This is very funny and I want the findings to be on a public medium eg Myadsl :)

Well this looks like another Telkom screw around. The fault is local IP : 196.43.9.146 is where the packet loss starts.... which belongs (suprise suprise) to TELKOM .... ash-ip-dir-equinix-pos-6-1.telkom-ipnet.co.za

Its the silly Ash Linux box again causing problems.
 
Last edited:
It's so funny I could just throttle someone...

Tracing route to www.yahoo.akadns.net [68.142.197.89]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 *
 
Its very obvious that there is a network break locally, uunet is going over same pipe and not experiecing any international problems, while saix users is experiecing problems on the local loop.

Telkom is just really retarded, and maybe there is a problem overseas with landslide but there is definitely a link down locally aswell.
 
Would someone with an ADSL connection please post their traceroutes in this forum. I will, with some software be able to trace the origins of each and every IP on that list......
 
my results:

traceroute: Warning: www.yahoo.com has multiple addresses; using 68.142.226.38
traceroute to www.yahoo.akadns.net (68.142.226.38), 30 hops max, 38 byte packets
1 hostnet-net112.posix.co.za (160.124.112.1) 0.199 ms 0.152 ms 0.129 ms
2 cisrb1.posix.co.za (160.124.2.1) 0.471 ms 0.504 ms 0.526 ms
3 168.209.89.53 (168.209.89.53) 0.939 ms 0.799 ms 0.869 ms
4 core1b-rba-gi0-1.rtr.isnet.net (196.26.0.10) 1.302 ms 1.158 ms 1.889 ms
5 168.209.0.142 (168.209.0.142) 249.062 ms 248.304 ms 249.341 ms
6 cmsfc2a-ny.nmszone.is.co.za (168.209.244.7) 251.294 ms 247.770 ms 247.253 ms
7 nyiix.bas1-m.nyc.yahoo.com (198.32.160.121) 248.176 ms 250.641 ms 249.681 ms
8 ge-2-0-9.p558.pat1.dce.yahoo.com (216.115.97.17) 262.833 ms * 257.815 ms
9 vlan260-msr2.re1.yahoo.com (216.115.96.173) 256.022 ms ge-3-1-0.p440-msr1.re1.yahoo.com (216.115.96.189) 254.200 ms vlan260-msr2.re1.yahoo.com (216.115.96.173) 255.378 ms
10 t-2-1.bas2.re2.yahoo.com (206.190.33.93) 254.796 ms t-3-1.bas1.re2.yahoo.com (206.190.33.91) 259.541 ms t-2-1.bas1.re2.yahoo.com (206.190.33.89) 253.965 ms
11 p7.www.re2.yahoo.com (68.142.226.38) 256.916 ms 259.072 ms 264.834 ms

Completed in 14.07 seconds, 0% cpu
 
additional results to gmai.com:

traceroute: Warning: www.gmail.com has multiple addresses; using 64.233.161.107
traceroute to gmail.l.google.com (64.233.161.107), 30 hops max, 38 byte packets
1 hostnet-net112.posix.co.za (160.124.112.1) 0.218 ms 0.208 ms 0.156 ms
2 cisrb1.posix.co.za (160.124.2.1) 1.424 ms 0.512 ms 0.430 ms
3 168.209.89.53 (168.209.89.53) 1.039 ms 0.764 ms 0.684 ms
4 core2b-rba-gi8-0-0.rtr.isnet.net (196.26.0.9) 1.190 ms 1.495 ms 0.923 ms
5 168.209.0.86 (168.209.0.86) 249.478 ms 248.523 ms 249.764 ms
6 cmsfc2a-ny.nmszone.is.co.za (168.209.244.7) 249.874 ms 248.753 ms 248.995 ms
7 ny-iix.above.net (198.32.160.22) 251.149 ms 248.858 ms 249.390 ms
8 so-4-0-0.mpr1.lga1.us.above.net (64.125.30.17) 250.485 ms 261.928 ms 263.815 ms
MPLS Label=278464 CoS=5 TTL=1 S=0
9 so-3-0-0.cr2.lga1.us.above.net (64.125.27.149) 248.062 ms 248.552 ms 249.436 ms
MPLS Label=246480 CoS=5 TTL=1 S=0
10 so-1-0-0.mpr2.iad1.us.above.net (64.125.28.65) 253.534 ms 256.560 ms 260.379 ms
MPLS Label=103552 CoS=5 TTL=1 S=0
11 so-3-0-0.mpr2.iad5.us.above.net (64.125.28.14) 253.379 ms 253.027 ms 252.173 ms
12 216.200.151.110.available.above.net (216.200.151.110) 254.499 ms 255.891 ms 253.948 ms
13 216.239.46.250 (216.239.46.250) 259.975 ms 216.239.46.248 (216.239.46.248) 256.134 ms 254.060 ms
14 216.239.47.69 (216.239.47.69) 275.920 ms 256.656 ms 255.212 ms
15 216.239.49.214 (216.239.49.214) 260.726 ms 216.239.48.190 (216.239.48.190) 261.350 ms 216.239.48.198 (216.239.48.198) 258.805 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Completed in 233.39 seconds, 0% cpu
 
thats unshaped, the guy specificly asked for shaped adsl ie. general user results, this is pointless Oliver.
 
um... sorry guys, maybe I missed something... but last time I checked I have a 512k 3Gig shaped account ... although I know more about IT than the average guy on the street, I still dont consider myself a power user, certainly most of the people in these forums have more IT knowledge than myself, so I dont understand what you are implying... maybe I was just lucky?... Here is what I did, step by step:

I visited: http://www.traceroute.org/

I selected South Africa and then I selected http://services.truteq.com/ (the other site is in Afrikaans and I'm sorry to say I don't know the language since I just moved to SA from overseas)

From that site I selected Tracerout to a host (http://services.truteq.com/cgi-bin/nph-traceroute) and then entered www.yahoo.com

I copied the results and pasted them here, then I did the same for google.

Like I said, you guys probably know more about these things than I do, but how do you determine that those are not general "user" results or that I am "unshaped"?
 
lol thats pointless, we want traceroutes from your connection at home to international address.

Doing traceroutes from that site is unshaped and shows nothing with regards to your line

ie. traceroutes from there, would do a trace from the actual server to server, not from your client(pc?) to server.
 
ok, you see?... proves my point!... I dont know how to run a traceroute from here, that's why I used that site lol

Ok clipse, tell me what I must do from here, step by step as if I was a 5 year old :)
 
hehe np

goto run->cmd then type tracert google.com or whichever dns/ip you want to trace.

:)
 
SAIX:.....
"Overseas technicians have indicated that they will have access to the site after 15 hours after which they will investigate the damage and also the restoration of this link.Major impact was to our adsl service and we have rerouted the majority of our adsl traffic to minimise the impact to our adsl service"
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X