Printer Friendly Version Print this thread
Email this thread to a friend eMail this thread to a friend
  • Google PR (In: Google)
  • Youtube Results on Google (In: Google)
  • Google (In: Pay Per Click - Google/Yahoo & Others)
  • SEO Top 10 Check List (In: General Search Engine Optimization)
  • Featured Web Site Template

    Hundreds More at Free Site Templates.com!

    Web Site Partners
    Sponsored Links
    Jet City Software
     
    Whos Here ?
    There are 0 guests and 2 members in the forums right now.
    Reflects user activity within the last 5 minutes
    Moderator(s): g1smd, Logan
    Forum Index · Search Engine Forums · Optimizing Your Website for the Search Engines · Google · Updated Google DataCentres GFE and IP Address List : 2008-June
    Member Message

    g1smd
    Staff
    Joined: Jul 28, 2002
    # Posts: 10438

    View the profile for g1smd Send g1smd a private message

    Posted: 2008-Jun-01 03:19
    Edit Message Delete Message Reply to this message


    Following on from the information posted a couple of years ago in an older Google Datacentres thread, here is a new version of the list:




    Older Google Datacentres (closed years ago):

    216.239.33.xxx - www-ex - Gone a very long time ago.
    216.239.35.xxx - www-sj - Gone a very long time ago.
    216.239.41.xxx - www-fi - Gone a very long time ago.
    216.239.55.xxx - www-zu - Gone a very long time ago.

    66.249.87.xxx - gfe-lo/lo2 - Not Responding for a Long Time.






    Original Google Datacentre Naming Convention from 2000 Onwards:

    216.239.33.xxx - www-ex/ex2 - Santa Clara, California.
    216.239.35.xxx - www-sj/sj2 - San Jose, California (Hosted at Global Crossing)
    216.239.37.xxx - www-va/va2 - Herndon, Virginia.
    216.239.39.xxx - www-dc/dc2 - Washington, DC.
    216.239.41.xxx - www-fi/fi2 - Unknown, Virginia.
    216.239.51.xxx - www-ab/ab2 - Sterling, Virginia (Hosted at Exodus)
    216.239.53.xxx - www-in/in2 - Santa Clara, California (Hosted at Exodus)
    216.239.55.xxx - www-zu/zu2 - Zurich, Switzerland.
    216.239.57.xxx - www-cw/cw2 - Palo Alto, California (Hosted at Cable and Wireless)
    216.239.59.xxx - www-gv/gv2 - Dublin, Ireland.

    66.102.7.xxx - www-mc/mc2 - Santa Clara, California.
    66.102.9.xxx - www-lm/lm2 - Dublin, Ireland.
    66.102.11.xxx - www-kr/kr2 - Dublin, Ireland.


    www-xx was always at xxx.xxx.xxx.100 and www-xx2 was always at xxx.xxx.xxx.101 although there were other IPs such as .98 .99 .100 .101 .102 .103 .104 .105 that also brought up a Google Search box.

    IPs addresses at .106 .107 .147 brought up the Google Directory on many Class C blocks too.



    The Big Datacentre Closure and Move Event:

    In late 2003 and early 2004, all of the old www-xx names disappeared over a short space of time.

    Most of the datacentres soon re-appeared with a new gfe-xx name but on slightly different base IPs. The last octet of the IP address changed, but each two letter GFE name remained on the same Class C block as the older equivalent www-xx name.

    There was one exception. The datacentre at www-ab was renamed as gfe-kc and remained on the same Class C block. Some reports show it briefly online as gfe-ab before closing down, and then a gap of many months, perhaps more than a year, before it re-appeared as gfe-kc again.



    The Base IP Addresses Changed as Follows:

    www-xx base IP addresses: (-xx).100 - (-xx2).101

    gfe-xx base IP addresses: (-xx).104 - (-xx2).99 - (-xx3).147 - (-xx4).103



    The 2004 Datacentre Closures and Upgrades in Detail:

    216.239.33.xxx - www-ex/ex2 - closed down
    216.239.35.xxx - www-sj/sj2 - closed down
    216.239.37.xxx - www-va/va2 - converted to gfe-va/2/3
    216.239.39.xxx - www-dc/dc2 - converted to gfe-dc/2
    216.239.41.xxx - www-fi/fi2 - converted to gfe-fi
    216.239.51.xxx - www-ab/ab2 - converted to gfe-kc - (possibly very briefly online as gfe-ab first)
    216.239.53.xxx - www-in/in2 - converted to gfe-in/2
    216.239.55.xxx - www-zu/zu2 - closed down
    216.239.57.xxx - www-cw/cw2 - converted to gfe-cw/2/3
    216.239.59.xxx - www-gv/gv2 - converted to gfe-gv/2/3/4

    66.102.7.xxx - www-mc/mc2 - converted to gfe-mc
    66.102.9.xxx - www-lm/lm2 - converted to gfe-lm/2/3
    66.102.11.xxx - www-kr/kr2 - converted to gfe-kr/2



    These are the major IP ranges that Google have allocated:

    8.6.48.0 - 8.6.55.255
    64.68.80.0 - 64.68.87.255
    64.233.160.0 - 64.233.191.255
    - In Use
    66.102.0.0 - 66.102.15.255 - In Use
    66.249.64.0 - 66.249.95.255 - In Use
    72.14.192.0 - 72.14.255.255 - In Use
    209.85.128.0 - 209.85.255.255 - In Use
    216.239.32.0 - 216.239.63.255 - In Use



    These IP ranges are also newly registered to Google:

    64.68.88.0 - 64.68.95.255
    74.125.0.0 - 74.125.255.255




    Current Google Datacentres (as of 2006-July, and still active 2008-May):

    64.233.161.xxx - gfe-od/od2/od3
    64.233.167.xxx - gfe-py/py2/py3
    64.233.169.xxx - gfe-yo/yo2
    64.233.171.xxx - gfe-rn/rn2/rn3
    64.233.179.xxx - gfe-ui/gfe-hs/hs2
    - [Note: 64.233.179.104 responds as both gfe-ui and gfe-hs]
    64.233.183.xxx - gfe-nf/nf2/nf3/nf4
    64.233.185.xxx - gfe-wr/wr2
    64.233.187.xxx - gfe-jc/jc2
    64.233.189.xxx - gfe-hk


    66.102.1.xxx - gfe-he
    66.102.9.xxx - gfe-lm/lm2/lm3


    66.249.81.xxx - gfe-bx/bx2/bx3
    66.249.83.xxx - gfe-wx/wx2
    66.249.89.xxx - gfe-jp/jp2
    66.249.91.xxx - gfe-ik/ik2/ik3
    66.249.93.xxx - gfe-ug/ug2


    72.14.205.xxx - gfe-qb/qb2
    72.14.211.xxx - gfe-au/au2
    72.14.207.xxx - gfe-eh/eh2
    72.14.209.xxx - gfe-bf/bf2
    72.14.215.xxx - gfe-hu/hu2
    72.14.217.xxx - gfe-bu/bu2
    72.14.219.xxx - gfe-ed/ed2/ed3
    72.14.221.xxx - gfe-fg/fg2/fg3
    72.14.223.xxx - gfe-ar/ar2/ar3
    72.14.235.xxx - gfe-tw/tw2/tw3
    72.14.247.xxx - gfe-ag/ag2/ag3
    72.14.253.xxx - gfe-po/po2/po3
    72.14.255.xxx - gfe-td/td2/td3/td4


    209.85.129.xxx - gfe-fk/fk2/fk3
    209.85.133.xxx - gfe-an/an2/an3
    209.85.135.xxx - gfe-mu/mu2/mu3/mu4
    209.85.139.xxx - gfe-pr/pr2/pr3
    209.85.143.xxx - gfe-ti/ti2/ti3


    216.239.51.xxx - gfe-kc/kc2
    216.239.59.xxx - gfe-gv/gv2/gv3/gv4




    Notes:

    On each Class-C block, there are several dozen IP addresses that are active. These usually end in 17, 18, 19, 44, 80, 81, 83, 84, 91, 93, 95, 98*, 99, 100, 101, 102, 103, 104, 105*, 106*, 107, 115, 133, 147, 184, 189, 210* and 214 (* Note: .98, .105, .106, & .210 seem to be no longer accessible). These show results from the "Google English" search screen.

    Each Class-C block also has a two-letter GFE alias. These are always mapped in a specific way. For these, gfe-xx always corresponds to xx.xx.xx.104, most blocks also have gfe-xx2 which is xx.xx.xx.99 and a few also have gfe-xx3 which is xx.xx.xx.147. Finally, and for a very few, there is gfe-xx4 which is always xx.xx.xx.103. The search screen is simply announced as "Google" without the "English" logo.

    For each gfe-xx.google.com search box, the same data can also be reached at gfe-xx1.google.com as it resolves to the same IP address.

    Matt Cutts confirms that all the data at all of the IP addresses within one Class-C block should usually be the same, as typically they are all the same datacentre.



    Searching:

    Google search can be accessed in several different ways:

    There is of course, google.com and all the various Google-owned country TLDs.

    Next there is the direct IP address. There are several thousand of those, as listed above and below.

    There used to be access at a URL like www-xx.google.com but those were replaced in 2004 with the newer gfe-xx.google.com system.

    Finally, there is the direct alias per-IP address, all like xx-in-fnn.google.com where xx is the same letters as from the GFE name, and nn is the last octet of the IP addesss (like 107 from 66.102.9.107 and so on).


    [ Message was edited by: g1smd 06/12/2008 11:22 am ]





    g1smd
    Staff
    Joined: Jul 28, 2002
    # Posts: 10438

    View the profile for g1smd Send g1smd a private message

    Posted: 2008-Jun-01 23:50
    Edit Message Delete Message Reply to this message

    Google Datacentres No Longer In Use (since some time in the last 18 months):

    64.233.163.xxx - gfe-nz/nz2

    66.102.7.xxx - gfe-mc/mc2/mc3
    66.102.11.xxx - gfe-kr/kr2


    66.249.85.xxx - gfe-ff/ff2

    72.14.203.xxx - gfe-ro/ro2

    209.85.155.xxx - gfe-ht/ht2/ht3/ht4
    209.85.199.xxx - gfe-rv/rv2/rv3 - (Found in other lists)

    216.239.37.xxx - gfe-va/va2
    216.239.39.xxx - gfe-dc/dc2
    216.239.53.xxx - gfe-in/in2/in3
    216.239.57.xxx - gfe-cw/cw2/cw3/cw4
    216.239.63.xxx - gfe-bp/bp2


    I must add that "no longer in use" means "no longer in use for search". While some Class C blocks have completely disappeared, some of the above now resolve to the Google Directory, or to Gmail, or to some other Google services instead.



    Datacentres Missing From Previous Lists in 2006/2007 (previously overlooked? or newly online?):

    64.233.165.xxx - gfe-jl/jl2/jl3

    209.85.199.xxx - gfe-rv/rv2/rv3 - (Found in other lists and since closed down)



    New Google Datacentres Newly Online in 2007/2008:

    209.85.137.xxx - gfe-mg/mg2/mg3
    209.85.141.xxx - gfe-pq/pq2/pq3
    209.85.147.xxx - gfe-wa/wa2/wa3
    209.85.149.xxx - gfe-hr
    209.85.153.xxx - gfe-im
    209.85.159.xxx - gfe-fh/fh2/fh3
    209.85.161.xxx - gfe-mk/mk2/mk3/mk4
    209.85.163.xxx - gfe-??/??2/??3/??4
    - (NO GFE name allocated - direct access by IP address only - where xxx is 107,104,99,147,103, etc).
    209.85.165.xxx - gfe-eo/eo2/eo3/eo4
    209.85.167.xxx - gfe-da/da2/da3/da4
    209.85.169.xxx - gfe-rc/rc2/rc3/rc4
    209.85.171.xxx - gfe-cg/cg2/cg3/cg4
    209.85.173.xxx - gfe-mh/mh2/mh3/mh4
    209.85.175.xxx - gfe-tc/tc2/tc3
    209.85.193.xxx - gfe-br/br2/br3/br4
    - (access by direct IP address and by br-in-fnnn.google.com URL format only - where nnn is 107,104,99,147,103, etc - NO ACCESS by GFE name).
    209.85.195.xxx - gfe-rg/rg2 - (access by direct IP address and by rg-in-fnnn.google.com URL format only - where nnn is 107,104,99 (but NOT 147,103), etc - NO ACCESS by GFE name).
    209.85.197.xxx - gfe-bd
    209.85.201.xxx - gfe-wf/wf2/wf3/wf4
    209.85.203.xxx - gfe-pn/pn2/pn3/pn4
    209.85.207.xxx - gfe-ya/ya2/ya3/ya4
    209.85.209.xxx - gfe-yb
    209.85.215.xxx - gfe-ye
    209.85.237.xxx - gfe-??
    - (NO GFE name allocated - direct access by IP address only - where xxx is 107,104 (but NOT 99,147,103), etc).



    Google was also allocated a new IP block, just over a year ago, at 74.125.0.0 - 74.125.255.255 and has already started to populate it:

    74.125.19.xxx - gfe-cf/cf2/cf3/cf4 - (access by direct IP address and by cf-in-fnnn.google.com URL format only - where nnn is 107,104,99,147,103, etc - NO ACCESS by GFE name).
    74.125.39.xxx - gfe-fx/fx2/fx3/fx4
    74.125.43.xxx - gfe-bw/bw2/bw3/bw4
    74.125.45.xxx - gfe-yx/yx2/yx3/yx4
    74.125.47.xxx - gfe-yw/yw2/yw3/yw4
    74.125.65.xxx - gfe-gx/gx2/gx3/gx4
    74.125.67.xxx - gfe-gw/gw2/gw3/gw4
    74.125.77.xxx - gfe-ew/ew2/ew3/ew4
    74.125.79.xxx - gfe-ey/ey2/ey3/ey4
    74.125.93.xxx - gfe-??/??2/??3/??4
    - (NO GFE name allocated - direct access by IP address only - where xxx is 107,104,99,147,103, etc).

    These ten new Class C blocks represent another significant expansion of usage. They could have been online for anything up to a year, but my feeling is that they are mostly only a few months old.


    Those without a GFE name or which resolve only by direct IP address are the most interesting. Could they be from a datacentre that is very newly online and therefore not yet fully commissioned?



    Historical:

    Back in 2006 I showed that Google used approx. 43 Class C blocks for their search operations and postulated that this corresponded with 43 datacentres (or at least 43 "server rooms" ) active.

    So, 43, then 41 (when some fell out of use), then 47 (when new ones were discovered) Class C blocks were in use in mid-late 2006.

    Since the 2006 lists were produced, 11 more have fallen out of use, and 34 new blocks have come online.

    Going back a little further; in the last two years they have closed about 11 of the older server farms (mostly in the older 66.102.xxx.xxx and 216.239.xxx.xxx Class C blocks) and they have opened 28 more in the 209.85.xxx.xxx range, and 10 more in the 74.125.xxx.xxx range, in the same time.

    There are currently 70 Class C blocks in use, and the current system of allocation allows for a maximum of 288 such blocks to be brought in to use at full capacity.

    When you take into account the individual GFE names like gfe-ro and gfe-pn3 there are approx. 204 of those active at present. Their current system allows for 1152 of those to be allocated, at a maximum of four per Class C block. Some blocks use less, but most new blocks seem to come online with four GFE names resolving these days. However, their naming convention has room for 2704 GFE entries, so there is plenty of room for expansion.

    Although not a directly useful measure, the number of individual directly accessible IP addresses in use is already in excess of 1400.



    In 2004, people were listing only 56, or so, IP addresses spread over about 18 Class C blocks.

    At that time, Google did have more online (not much more though), but people just hadn't yet discovered them.

    Even so, Google appears to have almost doubled in size in the last two-and-a-bit years alone.



    [ Message was edited by: g1smd 06/02/2008 12:57 pm ]





    g1smd
    Staff
    Joined: Jul 28, 2002
    # Posts: 10438

    View the profile for g1smd Send g1smd a private message

    Posted: 2008-Jun-27 14:40
    Edit Message Delete Message Reply to this message

    Google recently allocated GFE names to the new servers (listed above) which have been on test for a few months:

    209.85.163.xxx - becomes gfe-el/el2/el3/el4

    209.85.237.xxx - becomes gfe-yr

    74.125.93.xxx - becomes gfe-qw/qw2/qw3/qw4


    Forum Index · Search Engine Forums · Optimizing Your Website for the Search Engines · Google · Updated Google DataCentres GFE and IP Address List : 2008-June
    You are not permitted to post messages in this forum or topic, because of one or more of the following reasons:
    1. You have not yet logged in, or registered properly as a member
    2. You are a member, but no longer have posting rights.
    3. This is a private forum, for which you do not have permissions.

    If you are a recent member, it's possible that you simply have not yet confirmed your account. Please check your email for a message entitled 'JimWorld Forums: Confirm Your Account' and follow the instructions contained within.

    If you cannot find this message, click here to Re-Send it.

    If you are still experiencing problem, please read the Login Assistance Article for some advice on what may be causing your login not to work properly.

    Switch to Advanced Editor and ... Create a New Topic or Reply to this Thread

    New posts Forum is locked
    © 1995  ·  iWeb, Inc  ·  DBA JimWorld Productions