Externally, we saw the BGP and DNS problems outlined in this post but the problem actually began with a configuration change that affected the entire internal backbone. How's that even possible? Update from Facebookįacebook has now published a blog post giving some details of what happened internally. This wasn't a DNS issue itself, but failing DNS was the first symptom we'd seen of a larger Facebook outage. It was as if someone had "pulled the cables" from their data centers all at once and disconnected them from the Internet. Their DNS names stopped resolving, and their infrastructure IPs were unreachable. Facebook and its affiliated services WhatsApp and Instagram were, in fact, all down. Social media quickly burst into flames, reporting what our engineers rapidly confirmed too. But as we were about to post on our public status page we realized something else more serious was going on. Today at 15:51 UTC, we opened an internal incident entitled "Facebook DNS lookup returning SERVFAIL" because we were worried that something was wrong with our DNS resolver 1.1.1.1. “Facebook can't be down, can it?”, we thought, for a second.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |