Yesterday, OpenDNS resolved its 200,000,000,000th request. That’s 200 billion with a b.

Thank you to our many customers for making OpenDNS the world’s largest and fastest-growing DNS service. It’s been less than 3 months since we responded to the 100 billionth request. We’ve averaged more than 1 billion requests/day for that period. On Thursday, OpenDNS responded to 1.4 billion DNS requests (stats).

All that, with zero downtime (system status), thanks to multiple servers spread across five geographically distributed locations connected by multiple Tier 1 telco providers to deliver an amazingly fast, reliable Internet experience no matter the size of your network.

Come on in! Get started.

The magic numbers:

• 208.67.222.222
• 208.67.220.220

Yesterday marked another milestone in OpenDNS’s history; we served our 100 billionth DNS request. I remember how excited we were to serve 1 billion DNS requests in our first month. Compare that to yesterday where we served 1,071,072,782 queries in a single day.

This milestone is also a good time to point out that our DNS service has had zero downtime since the day it launched. We put up a system status website a couple weeks after we launched to show you just how reliable we are.

Or put simply…

And growing…

P.S. Some of you have asked what the 100 billionth DNS request was. Since we have five locations and we process stats in large aggregates every few minutes it is hard to tell. If we had to guess, we’re pretty sure it was either for TechCrunch or Digg.

I’ve just posted about this on the OpenDNS System Status site, but the OpenDNS.com website (and blog.opendns.com, etc.) were unavailable due to authoritative DNS failure for about 90 minutes earlier today, starting around 1pm PT (21:00 UTC). Here are the details.

I will repeat myself on a few key points.

First, OpenDNS’s speedy, reliable DNS was not affected. Our website is treated separately from our DNS, for this reason among others.

Second, the cause of the failure was a Denial of Service (DOS) attack on EveryDNS. David Ulevitch, CEO of OpenDNS, also owns and operates EveryDNS, but the two companies are separate. OpenDNS has used EveryDNS services, although we’ve now spread the authoritative DNS for OpenDNS more broadly as a result of this incident.

Third, the DOS attack on EveryDNS continues. It’s being actively worked on, as you can imagine. As we learn more, we’ll share it in this post, since I know other EveryDNS customers are interested, too.

Update: As of 9:30pm PT, December 1 (05:30 UTC December 2), EveryDNS is recovering. Still under attack, but mitigated. Status report on the EveryDNS home page. I’ll leave it to EveryDNS for updates from here on.

Note: you can bookmark or save our OpenDNS System Status site at http://208.67.219.60/ just for rare events like this, whether there is an authoritative or recursive DNS issue.

Yesterday we crossed the 4,000,000,000 (That’s four billion!) overall DNS query mark.

More importantly, we also crossed the 100,000,000 (That’s one hundred million!) DNS queries per day mark.

Check it out:

Woo Hoo!

As of Dec 31, 2006, London is online.

On our network map, we show our four current network nodes in the United States, and provide insight into our future locations. The map, dated July 7, is still accurate as I type this.

The first location online from our “Coming soon” contingent will be London, England. Our hardware is racked and powered in the London facility. But we’ve been held up by bandwidth discussions, as we have some specific network requirements that complicate the matter beyond just the cost of connectivity.

The delay is frustrating to us, too. My apologies to the several folks who have inquired and been told (by me personally, or by my colleagues) that London would be online by this time. I’m not going to promise a new date right now, but we’re working on this, and will announce more details on our blog as we have them. Once the London location is online, we’ll focus more attention on our next locations.

Fortunately, many customers are finding that OpenDNS is faster for them in the UK already, despite any network latency. That’s proof positive that DNS speed is the combination of two factors: network latency and software speed/cache size. Even when we’re “farther” away on the network, OpenDNS often delivers results back to the end user faster. We want to accelerate the experience again, by removing the network latency concern — which is the whole point of London.

Is it only me, or does this post beg for The Clash’s London Calling? Or is that just too much of a cliché?