INternational down / slow

Still nothing on the noticeboard:

Updates :

16 Jan 2007, 17:30:37 zumanm1
Our Technicians are busy investigating.

16 Jan 2007, 17:48:31 zumanm1
Our Technicians are busy investigating.

16 Jan 2007, 18:44:16 zumanm1
Our Technicians are busy investigating.

16 Jan 2007, 19:04:58 vdwalta1
Our Technicians are still busy investigating.
 
Say What?

What do you guys mean your connection is up :( my pings keep returning as :

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

SNIFF
 
Since this afternoon I have the problem that mail is not working, VoIP not working but web browsing and skype are fine - find that a bit curious. Any explanation for that?
 
IS - ADSL: Pretty much useless :)

PING google.com (72.14.207.99) icmp./ : 56(84) bytes of data.
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=1 ttl=230 time=722 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=2 ttl=230 time=724 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=3 ttl=230 time=729 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=4 ttl=230 time=735 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=5 ttl=230 time=718 ms

--- google.com ping statistics ---
6 packets transmitted, 5 received, 16% loss, time 5039ms
rtt min/avg/max/mdev = 718.026/725.961/735.560/6.087 ms

For SAIX info see - http://noc.sadomain.com/
 
someone told me a undersea earthquake fusked up the cables. lol
 
Retarded

What I find retarded is my friend who lives 2-3 km's away and falls under a different exchange and uses web africa vs my telkom connection has perfect international, is this only affecting telkom isp or the majority of saix customers? how is he still online, is it affecting certain exchanges only - J
 
Probably find that somewhere in Rondebosch is some 9600 modem that hasn't been switched over to 10-digit dialling :)
 
That SAIX notice boards?

yup

UPDATE:

16 Jan 2007, 19:04:58 vdwalta1
Our Technicians are still busy investigating.

16 Jan 2007, 20:18:36 vdwalta1
Our Technicians are still busy investigating.

16 Jan 2007, 21:44:59 vdwalta1
International Technicians are attending to cable break

Cause of Failure : Cable break in Malaysia
Status : New

 
JHB -Benoni

As of 22h01 still no International (Google/Yahoo) - CNN is fine (perhaps SAIX cache?)
Local is fine
 
Still it amazes me our traffic is going via safe to US instead of via sat-3? [unless hong kong moved].. or can someone explain how the sat-3 + safe cable works..
 
Still it amazes me our traffic is going via safe to US instead of via sat-3? [unless hong kong moved].. or can someone explain how the sat-3 + safe cable works..

My thoughts exactly.

We should be going via SAT3 and not SAFE.
 
thous ppl with IS , Verizon Adsl accounts should have there INT working fine
only looks like 2 b saix effected by this..


ace check doing trace from states box to ADSL IP here ...
GG LOOK WHERE IT GOES THRU??? JAPAN, HONG KONG WTF?

22:34:55 up 194 days, 12:06, 1 user, load average: 1.18, 0.86, 0.93
[ ~]# traceroute 41.242.85.60
traceroute to 41.242.85.60 (41.242.85.60), 30 hops max, 38 byte packets
1 gw.dedicated.abac.net (216.55.133.1) 0.717 ms 0.524 ms 0.454 ms
2 gi4-16.cr1.sandiego.abac.net (66.226.66.13) 0.485 ms 0.441 ms 0.487 ms
3 gi5-0.cr1.sandiego.abac.net (66.226.66.18) 0.352 ms 0.373 ms 0.361 ms
4 ge-1-0-0-142.gar2.SanDiego1.Level3.net (64.158.218.1) 2.984 ms 2.648 ms 2.487 ms
5 ge-4-0-0.mp1.SanDiego1.Level3.net (4.68.97.209) 2.860 ms 3.416 ms 3.487 ms
6 ae-0-0.bbr2.LosAngeles1.Level3.net (64.159.1.126) 6.108 ms as-2-0.bbr1.LosAngeles1.Level3.net (64.159.1.30) 5.412 ms 5.364 ms
7 ae-22-52.car2.LosAngeles1.Level3.net (4.68.102.45) 4.983 ms ae-12-53.car2.LosAngeles1.Level3.net (4.68.102.77) 4.653 ms ae-22-54.car2.LosAngeles1.Level3.net (4.68.102.109) 4.885 ms
8 xe-7-2.r00.lsanca03.us.bb.gin.ntt.net (129.250.8.181) 4.759 ms 5.353 ms 5.211 ms
9 xe-1-0-0.r20.lsanca03.us.bb.gin.ntt.net (129.250.5.32) 5.358 ms 5.047 ms 4.986 ms
MPLS Label=524945 CoS=5 TTL=1 S=0
10 p64-0-1-0.r20.tokyjp01.jp.bb.gin.ntt.net (129.250.2.218) 117.134 ms 118.850 ms 122.659 ms
MPLS Label=565669 CoS=5 TTL=1 S=0
11 p4-1-3-0.r01.newthk01.hk.bb.gin.ntt.net (129.250.3.174) 208.993 ms 208.000 ms 207.888 ms
MPLS Label=715328 CoS=5 TTL=1 S=0
12 as-0.r00.newthk01.hk.bb.gin.ntt.net (129.250.4.18) 212.231 ms 180.803 ms 209.883 ms
13 203.131.240.198 (203.131.240.198) 207.663 ms 209.968 ms 207.503 ms
14 203.131.243.18 (203.131.243.18) 269.324 ms 269.792 ms 269.341 ms
15 hkg-ip-dir-hongkong-pos-2-3-1.telkom-ipnet.co.za (196.43.9.222) 322.917 ms 321.773 ms 322.697 ms
16 196.43.18.41 (196.43.18.41) 269.610 ms 269.368 ms 269.850 ms
17 rrba-ip-lir-1-pos-6-3.telkom-ipnet.co.za (196.43.9.5) 325.171 ms 324.396 ms 324.297 ms
18 196.43.23.181 (196.43.23.181) 318.560 ms 317.156 ms 317.930 ms
19 nngy-ip-esr-2-gig-6-1-0-606.telkom-ipnet.co.za (196.43.10.89) 317.950 ms 317.667 ms 317.954 ms
20 nngy-ip-esr-2-gig-6-1-0-606.telkom-ipnet.co.za (196.43.10.89) 318.947 ms 319.441 ms 319.310 ms
21 * * *
22 * * *
23 * * *

[~]# uptime
22:35:19 up 194 days, 12:07, 1 user, load average: 1.27, 1.00, 0.98
 
Last edited:
Its just telkom covering its incompetence again.
someone remembered the earthquake braking cables in Malaysia 2 weeks ago and said cool we can blame it on that.
 
this is the funny check this speed of this traceroute..
and look where really slows down...
hop 1 to 9 is 5 ms
hop 10 to 15 is 82 ms
hopt 16 to 18 is 279 ms ??? What the F happen there?? IT LAND in SA OH

traceroute to 41.204.193.119 (41.204.193.119), 30 hops max, 38 byte packets
1 gw.dedicated.abac.net (216.55.133.1) 0.551 ms 0.449 ms 0.486 ms
2 gi4-16.cr1.sandiego.abac.net (66.226.66.13) 0.478 ms 0.469 ms 0.482 ms
3 gi2-0.er1.sandiego.abac.net (66.226.66.2) 0.362 ms 0.384 ms 0.364 ms
4 ge-1-0-0-142.gar2.SanDiego1.Level3.net (64.158.218.1) 1.354 ms 1.507 ms 1.486 ms
5 ge-4-0-0.mp1.SanDiego1.Level3.net (4.68.97.209) 1.605 ms 27.381 ms 1.854 ms
6 ae-0-0.bbr2.LosAngeles1.Level3.net (64.159.1.126) 4.604 ms as-2-0.bbr1.LosAngeles1.Level3.net (64.159.1.30) 4.890 ms 4.524 ms
7 ge-7-0-0-52.gar1.LosAngeles1.Level3.net (4.68.102.48) 5.226 ms ge-0-0-0-55.gar1.LosAngeles1.Level3.net (4.68.102.144) 4.774 ms ge-7-0-0-52.gar1.LosAngeles1.Level3.net (4.68.102.48) 4.649 ms
8 uunet-level3-oc48.LosAngeles1.Level3.net (209.0.227.38) 4.897 ms 4.893 ms 4.973 ms
9 0.so-7-0-0.XL1.LAX15.ALTER.NET (152.63.116.22) 5.102 ms 37.867 ms 4.852 ms
10 0.so-3-0-0.XL1.MIA4.ALTER.NET (152.63.85.62) 80.568 ms 80.846 ms 80.684 ms
11 0.so-3-0-0.CL1.MIA4.ALTER.NET (152.63.101.41) 80.932 ms 81.258 ms 80.811 ms
12 207.ATM4-0.IH3.MIA4.ALTER.NET (152.63.7.169) 80.447 ms 80.627 ms 80.690 ms
13 102.ATM5-0.IH4.MIA4.ALTER.NET (152.63.7.78) 80.770 ms 81.039 ms 80.796 ms
14 POS2-0-0.IR2.MIA16.ALTER.NET (152.63.86.146) 80.920 ms 80.921 ms 80.944 ms
15 atm5-0-0sub103.cr2.mia16.alter.net (196.30.229.222) 82.442 ms 81.530 ms atm6-0-0sub902.cr2.mia16.alter.net (196.30.229.210) 81.829 ms
16 srp1-0-0.gw1.cpt1.alter.net (196.31.249.66) 278.447 ms 279.404 ms 278.332 ms MPLS Label=425 CoS=5 TTL=254 S=0
17 vlan10.hr1.cpt1.alter.net (196.30.176.36) 278.832 ms 279.544 ms 279.059 ms
18 firewall1.cpt2.host-h.net (196.30.82.62) 278.968 ms 281.958 ms 279.103 ms
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X