Blogger Incident Report By Eddie Kessler, Tech Lead/Manager, Blogger (This is a follow-up to the original post we made on Blogger Buzz about this incident.) On Wednesday, May 11 at 10:00pm PDT, Blogger entered a one-hour scheduled maintenance period to make improvements to increase service reliability. Unfortunately, errors made during this period had the opposite effect. This report describes what we were doing, what went wrong, how we fixed it, and what we’re doing to help prevent these types of problems from happening again. We sincerely apologize for the impact of this incident on Blogger’s authors and readers. What we were doing Blogger maintains replicas (copies) of blogs in multiple locations so if one copy becomes unavailable — maybe due to a cut network cable or loss of power — blogs continue to remain accessible. During this maintenance period we attempted to add several more replicas to both increase redundancy (which helps make the service more robust) and capacity (so we