---
title: "Google upgrades to \"BigDaddy\""
url: "https://osherove.com/blog/2006/2/6/google-upgrades-to-quotbigdaddyquot.md"
canonical: "https://osherove.com/blog/2006/2/6/google-upgrades-to-quotbigdaddyquot.html"
published: "2006-02-06T12:34:00"
updated: "2006-02-06T12:34:00"
tags: []
author: "Roy Osherove"
description: "Weird headline, huh? Google is doing a major upgrade to their search data centers. during this upgrade, you can check out how the new data center acts and behaves (code named \"BigDaddy\") through several IP addresses.In…"
usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)."
license: "https://creativecommons.org/licenses/by/4.0/"
---

# Google upgrades to "BigDaddy"

By Roy Osherove February 6, 2006

**Historical article** · Originally published February 6, 2006; technical details may be outdated.

Weird headline, huh?

Google is doing a major upgrade to their search data centers. during this upgrade, you can check out how the new data center acts and behaves (code named "BigDaddy") through several IP addresses.In addition to 66.249.93.104 and 64.233.179.104, BigDaddy is now up at 216.239.51.104.

**How do I know if the version of Google is using "BigDaddy"?**

A: There’s not a definitive way outside of Google. But the \[sf giants\] example [Here](http://www.mattcutts.com/blog/seo-advice-discussing-302-redirects/) remains a pretty good test. If the query \[sf giants\] returns giants.mlb.com, the odds are pretty good that you’re hitting BigDaddy.

\[More info on this in [Matt Cutts](http://www.mattcutts.com/blog/bigdaddy-progress-update/)' blog.\]

_PS (unrelated funny tidbit)_

This "[soldiers taking drugs](http://video.google.com/videoplay?docid=517198059628627413)" experiment certainly looks like a Monty python sketch.  (via [Google scoped blog](http://blog.outer-court.com/archive/2006-02-03.html#n63))

Or, if you're in a \*really\* good mood, go see "[BrokeBack to the Future](https://www.youtube.com/watch?v=zfODSPIYwpQ)"(same source)


---

## About the author

**Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery.

### Sites

- [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership.
- [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts.
- [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin.
- [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model.
- [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps.
- [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes).

### Social

- X: https://x.com/royosherove
- LinkedIn: https://www.linkedin.com/in/osherove/

### Contact

- Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7

### License

Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/