Showing posts with label ip. Show all posts
Showing posts with label ip. Show all posts

Thursday, August 06, 2009

Google preparing for full roll-out?

Google shuffles around some more DNS records et voilá:
  • mail.google.com now resolves to a Google-owned IP (one of the cpt01s01 series)
  • mt.google.com now resolves to a Google-owned IP (as above, so below)
Was the hosting of the Google Maps tiles on the [presumed] GGC caching box just a fig-leaf, a ploy for respectability? Since only YouTube access still seems to be directed towards those caching boxen, perhaps that traffic was a quite-substantial chunk of the original Google traffic to TENET's network, the rest of which is now easily handled by the local peering arrangement.

It might allow easier filtering or shaping for the IT/ICTS departments so inclined, but why else keep the YouTube traffic on those boxes? Google's purported 'boxenertia'?


However, seeing that GMail is now locally hosted, that means the major services are being served from local machines. Perhaps this means Google is getting ready for a full-bore load test, in preparation for a proper roll-out?

Wednesday, March 11, 2009

Google resolving locally

When resolving www.google.co.za from within TENET IP space, one now receives A records indicating TENET IP addresses.

There are still some holdouts - kh.google.com / mwx.google.com and mail.google.com still resolve to normal Google IP addresses. Perhaps they'll transition soon.

Wednesday, February 25, 2009

UCT's extra bandwidth redux

[from a comment on the last post:]
Of course, SANREN is what's supposed to provide the drastically improved last-mile.
SANReN will eventually provide the core of the new network, and maybe the access leg too. Some Gauteng institutions have access via the fibre ring there and are happy. Many large institutions elsewhere don't have that yet (and are waiting, waiting, waiting) and are unhappy.

However, if the UCT link was increased from ~32 to ~44 Mbps (coincidentally this is like going from an E3 to a DS-3), what's to prevent it from being increased further? Why not a DS-4 (~274 Mbps) :)
BTW, the Google caches are already live. [We don't know for sure that these are GGCs, but see below ] Their effectiveness seems to be improving (presumably their caches are still filling), but they do still use quite a lot of incoming (international) bandwidth.
If these are Google caches (GGCs), I doubt they will have reduced international bandwidth usage much. The local usage would spike because access is so much quicker and easier.
Traceroute (ICMP, rather than UDP) to v1.cache.googlevideo.com
mt.google.com is also mapping to a TENET IP block, so Google Maps tiles should be served from somewhere local [TENET or GGC or who-knows-what].

kh.google.com [Google Earth] is still mapping to the Google IP addresses overseas.

mail.google.com and docs.google.com still map to the Google IP blocks overseas.

So either TENET has some sort of fancy caching and line-rate traffic redirection going on, or Google is doing something interesting.

Hopefully the local build-out will be finished soon.