The ins and outs of the blogger.com unblocking incident from yesterday

The reason why xxx.blogspot.com was briefly accessible yesterday is, in fact, the same as what everyone (including reader XiaoBi's email) later guessed: Google temporarily redirected blogspot.com’s IP to 72.14.207.191, while our GFW was targeting the original old IP, which is 66.102.15.101. Therefore, it wasn't because Google made an effort, nor was it because the GFW went on vacation; it was simply an accident. The details of what happened? They're below.

First, let's take a look at an official announcement posted on blogger.com (translated):

**Tuesday, August 1, 2006**

Due to a configuration change that occurred earlier this evening, approximately 10% of requests to blogspot may not be successfully returned. Users accessing blogspot might experience slow speeds or see a server error message.

If you encounter this issue, refreshing the page you’re trying to access should work as a good solution. Meanwhile, we are actively working to resolve the problem.

**23:24 Update:** The issue has been resolved.

**23:56 Update:** To be more precise, the issue has been resolved but it may still take some time for the fix to fully propagate.

Please note that the times mentioned here refer to U.S. Pacific Time, which is roughly 16 hours behind ours. In other words, the configuration change on blogger.com happened just as...