Not to bash on SAINET, they are obviously still testing and working on their new network but here are a few traceroutes I did out of interest sake. Looking at them I see now how they can do the split accounting for local/international, by making use of a product from Neology or whatever but I do remember reading about neology planning to do split account a few months ago on their website.
From Europe to Sainet's website:
Code:
be ~ # traceroute www.sainet.co.za
traceroute to www.sainet.co.za (41.216.192.115), 30 hops max, 40 byte packets
1 rt-gs01-v53.xl-is.net (79.170.90.2) 0.509 ms 0.450 ms 0.424 ms
2 xl-internetservices.nl.jointtransit.nl (217.170.10.139) 1.023 ms 1.262 ms 1.273 ms
3 k705.pni-openpeering.ams1.nl.above.net (82.98.253.169) 0.927 ms 0.915 ms 0.893 ms
4 ge-0-2-0.mpr1.ams1.nl.above.net (64.125.28.93) 1.580 ms 1.558 ms 1.539 ms
5 so-3-0-0.mpr2.ams5.nl.above.net (64.125.28.90) 1.498 ms 1.481 ms 1.457 ms
6 so-2-0-0.mpr1.lhr2.uk.above.net (64.125.27.177) 11.371 ms 11.486 ms 11.531 ms
7 213-152-252-92.elite.net.uk (213.152.252.92) 12.788 ms 12.492 ms 12.730 ms
8 217.68.240.26 (217.68.240.26) 13.446 ms 13.646 ms 14.009 ms
9 217.68.254.108 (217.68.254.108) 13.673 ms 13.583 ms 13.941 ms
10 41-216-193-198.neoinx.net (41.216.193.198) 1037.748 ms 1037.726 ms 1037.670 ms
11 grz-sainetcr02-eth1-vlan210.neology.co.za (41.216.193.166) 1038.226 ms 1038.256 ms 1038.188 ms
12 ns1.sainet.co.za (41.216.192.115) 1038.207 ms 1029.232 ms 1021.939 ms
Seems their international link gets a bit saturated during the day reaching latencies of a 1000ms.
Now from local:
Code:
tpr-route-server>traceroute www.sainet.co.za
Translating "www.sainet.co.za"...domain server (196.25.1.11) [OK]
Type escape sequence to abort.
Tracing the route to ns1.sainet.co.za (41.216.192.115)
1 tpr-ip-esr-1-fe-1-0-3.telkom-ipnet.co.za (196.25.9.45) 0 msec 0 msec 0 msec
2 196.43.51.6 0 msec 0 msec 4 msec
3 ipinx-internet-gw.telkom-ipnet.co.za (196.25.110.46) 0 msec 4 msec 0 msec
4 41-216-193-170.neoinx.net (41.216.193.170) [AS 37105] 4 msec 0 msec 4 msec
5 ns1.sainet.co.za (41.216.192.115) [AS 37105] 4 msec 0 msec 4 msec
Code:
local-route-server>traceroute www.sainet.co.za
Translating "www.sainet.co.za"...domain server (168.210.2.2) [OK]
Type escape sequence to abort.
Tracing the route to www.sainet.co.za (41.216.192.115)
1 ar2-rba-tnr-gi0-3-11.ip.isnet.net (196.34.7.195) [AS 3741] 0 msec 0 msec 0 msec
2 168.209.1.170 [AS 3741] 4 msec 0 msec 4 msec
3 rrba-ip-spe-2-wan.telkom-ipnet.co.za (196.25.127.181) [AS 5713] 4 msec 4 msec 0 msec
4 196.43.25.137 [AS 5713] 4 msec 4 msec 4 msec
5 rrba-ip-hsll-1-gig-1-0-8.telkom-ipnet.co.za (196.43.51.70) [AS 5713] 128 msec 0 msec 0 msec
6 ipinx-internet-gw.telkom-ipnet.co.za (196.25.110.46) [AS 5713] 0 msec 4 msec 4 msec
7 41-216-193-170.neoinx.net (41.216.193.170) [AS 37105] 0 msec 4 msec 4 msec
8 www.sainet.co.za (41.216.192.115) [AS 37105] 4 msec 4 msec 4 msec
Local latencies on their network looks excellent and seems they are based somewhere in JHB/PTA probably JHB and making use of SAIX for local transit and they have their own layer2 transit over SEACOM I assume because later after hours the latencies to their website from Europe is around 233ms which looks like its SEACOM as opposed to SAT3 which should be around 170-190ms.