SAIX / IS routing?

w1z4rd

Karmic Sangoma
Joined
Jan 17, 2005
Messages
52,146
Reaction score
8,340
Location
127.0.0.1
Pinging ftp.is.co.za [196.4.160.12] with 32 bytes of data:
Reply from 196.4.160.12: bytes=32 time=293ms TTL=58
Reply from 196.4.160.12: bytes=32 time=294ms TTL=58
Reply from 196.4.160.12: bytes=32 time=299ms TTL=58
Reply from 196.4.160.12: bytes=32 time=301ms TTL=58

Thats some international looking routing.
 
Maybe give us a traceroute instead of just a ping. According to the SAIX looking glass, routing looks fine, just high latency.

Code:
tpr-route-server>traceroute ftp.is.co.za
Translating "ftp.is.co.za"...domain server (196.25.1.11) (196.43.1.11)

Translating "ftp.is.co.za"...domain server (196.25.1.11) [OK]

Type escape sequence to abort.
Tracing the route to ftp.is.co.za (196.4.160.12)

  1 tpr-ip-esr-1-fe-1-0-3.telkom-ipnet.co.za (196.25.9.45) 0 msec 0 msec 0 msec
  2 rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za (196.43.8.198) 0 msec 4 msec 0 msec
  3 196.43.25.138 0 msec 4 msec 0 msec
  4 internet-solutions-gw.telkom-ipnet.co.za (196.25.127.182) 96 msec 92 msec 96 msec
  5 ar2-rba-tnr-gi0-2.ip.isnet.net (168.209.1.132) [AS 3741] 92 msec
    ar1-rba-tnr-gi0-1.ip.isnet.net (196.26.0.2) [AS 3741] 92 msec
    ar2-rba-tnr-gi0-1.ip.isnet.net (196.26.0.12) [AS 3741] 92 msec
  6  ?  ?  ? 
  7  ?  ?  ?
 
Looks like congestion on IS Telkom IPC from CT-Jhb:

Code:
Tracing route to ftp.is.co.za [196.4.160.12]
over a maximum of 30 hops:

   1   <10 ms   <10 ms     1 ms  home.gateway [192.168.1.254]
   2     8 ms     7 ms     8 ms  dsl-245-128-01.telkomadsl.co.za [41.245.128.1]
   3     9 ms     8 ms     8 ms  wblv-ip-lir-1-gig-4-0-0.telkom-ipnet.co.za [196.43.8.190]
   4     8 ms     8 ms     8 ms  196.43.25.206
   5    10 ms    10 ms     9 ms  196.25.247.26
   6    10 ms    10 ms    10 ms  core2a-ctn-gi0-1.ip.isnet.net [168.209.2.6]
   7   233 ms     *      222 ms  core2a-pkl-gi0-0-3-1-90.ip.isnet.net [168.209.100.153]
   8   230 ms   229 ms   233 ms  ar1-rba-tnr-gi0-1.ip.isnet.net [196.26.0.2]
   9   230 ms   229 ms   228 ms  ftp.is.co.za [196.4.160.12]

Trace complete.

This happens often on Mweb Telkom IPC, so don't feel left out...
 
tracert ftp.is.co.za

Tracing route to ftp.is.co.za [196.4.160.12]
over a maximum of 30 hops:

1 3 ms 2 ms 2 ms 192.168.1.151
2 36 ms 37 ms 43 ms dsl-241-0-01.telkomadsl.co.za [41.241.0.1]
3 39 ms 41 ms 37 ms wblv-ip-lir-1-gig-4-0-0.telkom-ipnet.co.za [196.
43.8.190]
4 37 ms 41 ms 40 ms 196.43.25.206
5 38 ms 40 ms 42 ms 196.25.247.26
6 41 ms 40 ms 39 ms core1a-ctn-gi0-2.ip.isnet.net [168.209.6.5]
7 110 ms 117 ms 114 ms core1a-pkl-gi0-0-3-1-305.ip.isnet.net [168.209.1
00.73]
8 118 ms 114 ms 112 ms ar2-rba-tnr-gi0-1.ip.isnet.net [196.26.0.12]
9 117 ms 114 ms 115 ms ftp.is.co.za [196.4.160.12]

Trace complete.

Thats my routing.
 
Routing looks good, mostly looks like the peering links are running congested, or actually no. Rather the IS network has congestion on their national network.
 
I've noticed the same problem on the IS network. It's only during the day though. I use a 30GB local-only, which should be unshaped 24/7, but during the day I get pings of around 300ms to and from the Webafrica network and IS sites. At night it's 50ms. If I switch to SAIX during the day, it's 40-50ms, so it's definitely IS related, and it's something that's happened fairly recent. (last few weeks)
 
Top
Sign up to the MyBroadband newsletter
X