Google server testing in South Africa?

Google doesn't pay for bandwidth. They will not pay for a peering agreement.

It would actually benefit the providers, since this would save a huge amount of bandwidth on their international links.

So if anything is holding them up, its the local providers that are trying to get money out of it.
 
This would be fantastic news, the enhanced user experience would be great; here's hoping!
 
afair google has an open peering policy, and will peer with anyone. I also suspect the proplem lies more with local ISPs not wishing to peer.
 
Its probably more in line with:

Google wouldn't want to pay anything for peering, so its up to the ISP to pay for the physical link to wherever Google is located. So the cost is on to the ISP and they might not want to pay for that alone and would prefer to go 50/50 with google.

Still, I don;t see how that is a bad thing, it will lessen quite a bit of load on the main links as well as giving better latency to google...
 
A traceroute to google.co.za from UCT reveals a server cpt01s01-in-f100.google.com with a ping of 7ms :D
 
A traceroute to google.co.za from UCT reveals a server cpt01s01-in-f100.google.com with a ping of 7ms :D

http://protea.tenet.ac.za/cgi/cgi_trace.exe to www.google.co.za
1 <10 <10 <10 196.21.79.49 e1b.ten-mr0-tenet.uni.net.za
2 <10 <10 <10 155.232.253.254 unknown.uni.net.za
3 <10 <10 <10 64.233.174.105 Unavailable
4 <10 <10 <10 64.233.179.104 cpt01s01-in-f104.google.com

From IS it still an overseas hop with ping times of 430ms
 
Last edited:
Anyone that is capped, try access Google.co.za and see if u r able to access it, or am I wrong.
 
This is currently only on the TENET network...
Can anyone from a Neotel connection do a traceroute into local Google server (64.233.179.104) ?

No local routing into 64.233.179.104 yet ?
traceroute to 64.233.179.104 (64.233.179.104), 30 hops max, 38 byte packets
1 cisrb1-net109-64.truteq.com (160.124.109.126) 0.275 ms 0.249 ms 0.106 ms
2 cisldn1-cisrbc1.posix.co.za (160.124.1.2) 169.254 ms 170.468 ms 167.632 ms
3 de-cix10.net.google.com (80.81.192.108) 179.874 ms 180.121 ms 179.003 ms
4 209.85.255.172 (209.85.255.172) 179.729 ms 209.85.255.170 (209.85.255.170) 183.611 ms 193.377 ms
5 72.14.233.104 (72.14.233.104) 190.470 ms 72.14.232.105 (72.14.232.105) 190.090 ms 190.523 ms
6 64.233.174.41 (64.233.174.41) 181.579 ms 185.140 ms 181.876 ms
7 * * *
8 cpt01s01-in-f104.google.com (64.233.179.104) 179.818 ms 180.791 ms 180.368 ms
 
Last edited:
FABULOUS NEWS! International/local bandwidth cost differentiation is soon to be a thing of the past....
From what I can see, it's entirely based on what DNS server you use. If the guys currently getting 10ms to google.com can provide us with the DNS server, or even resolved IP addresses that we could use in our hosts file, then (assuming TENET doesn't mind) there's no reason why we can't experience the benefits of this too...
From my knowledge of the google network, chances are there are MANY of these customized host/IP addresses pairs, so just assigning *.google.com to a specific IP won't work - an authentic, properly configured DNS server would be the answer. Now it's only a matter of time before SAIX/IS/Mweb/etc configure their DNS servers to reflect this change, and BANG the whole country will be using local Google, YouTube :)
 
Last edited:
Chances are there are many of these customized host/IP addresses pairs, so a properly configured DNS server would be the best bet. Now it's only a matter of time before SAIX/IS/Mweb/etc configure their DNS servers to reflect this change, and BANG the whole country will be using local Google, YouTube :)

I would not agree with your statement, if you look at the traceroute above from the Posix.co.za network, the routing is still international and as RPM said,its only available on the TENET network - pity. Do a tracert from your PC,still international routing ?
 
Top
Sign up to the MyBroadband newsletter
X