{"id":482,"date":"2021-10-05T02:07:22","date_gmt":"2021-10-05T02:07:22","guid":{"rendered":"https:\/\/fde.cat\/index.php\/2021\/10\/05\/update-about-the-october-4th-outage\/"},"modified":"2021-10-05T02:07:22","modified_gmt":"2021-10-05T02:07:22","slug":"update-about-the-october-4th-outage","status":"publish","type":"post","link":"https:\/\/fde.cat\/index.php\/2021\/10\/05\/update-about-the-october-4th-outage\/","title":{"rendered":"Update about the October 4th outage"},"content":{"rendered":"

To all the people and businesses around the world who depend on us, we are sorry for the inconvenience caused by today\u2019s outage across our platforms. We\u2019ve been working as hard as we can to restore access, and our systems are now back up and running. The underlying cause of this outage also impacted many of the internal tools and systems we use in our day-to-day operations, complicating our attempts to quickly diagnose and resolve the problem.<\/span><\/p>\n

Our engineering teams have learned that configuration changes on the backbone routers that coordinate network traffic between our data centers caused issues that interrupted this communication. This disruption to network traffic had a cascading effect on the way our data centers communicate, bringing our services to a halt. <\/span><\/p>\n

Our services are now back online and we\u2019re actively working to fully return them to regular operations. We want to make clear at this time we believe the root cause of this outage was a faulty configuration change. We also have no evidence that user data was compromised as a result of this downtime. <\/span><\/p>\n

People and businesses around the world rely on us everyday to stay connected. We understand the impact outages like these have on people\u2019s lives, and our responsibility to keep people informed about disruptions to our services. We apologize to all those affected, and we\u2019re working to understand more about what happened today so we can continue to make our infrastructure more resilient.\u00a0 <\/span><\/p>\n

The post Update about the October 4th outage<\/a> appeared first on Facebook Engineering<\/a>.<\/p>\n

Facebook Engineering<\/p>","protected":false},"excerpt":{"rendered":"

To all the people and businesses around the world who depend on us, we are sorry for the inconvenience caused by today\u2019s outage across our platforms. We\u2019ve been working as hard as we can to restore access, and our systems are now back up and running. The underlying cause of this outage also impacted many… Continue reading Update about the October 4th outage<\/span><\/a><\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","footnotes":""},"categories":[7],"tags":[],"class_list":["post-482","post","type-post","status-publish","format-standard","hentry","category-technology","entry"],"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":484,"url":"https:\/\/fde.cat\/index.php\/2021\/10\/05\/more-details-about-the-october-4-outage\/","url_meta":{"origin":482,"position":0},"title":"More details about the October 4 outage","date":"October 5, 2021","format":false,"excerpt":"Now that our platforms are up and running as usual after yesterday\u2019s outage, I thought it would be worth sharing a little more detail on what happened and why \u2014 and most importantly, how we\u2019re learning from it.\u00a0 This outage was triggered by the system that manages our global backbone\u2026","rel":"","context":"In "Technology"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":257,"url":"https:\/\/fde.cat\/index.php\/2021\/08\/31\/analytical-model-for-capacity-and-degradation-in-distributed-systems\/","url_meta":{"origin":482,"position":1},"title":"Analytical Model for Capacity and Degradation in Distributed Systems","date":"August 31, 2021","format":false,"excerpt":"Activity Platform (AP) is part of our Einstein Activity Capture (EAC) and Engagement Activity Platform (EAP) eco-system. AP captures, on behalf of users, their activities and engagement data generated from the interaction between users and their leads and contacts. Upon capturing those records, they are scoped, augmented with artificial intelligence\u2026","rel":"","context":"In "Technology"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":794,"url":"https:\/\/fde.cat\/index.php\/2023\/11\/20\/sre-weekly-issue-399\/","url_meta":{"origin":482,"position":2},"title":"SRE Weekly Issue #399","date":"November 20, 2023","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, FireHydrant: Severity levels help responders and stakeholders understand the incident impact and set expectations for the level of response. This can mean jumping into action faster. But first, you have to ensure severity is actually being set. Here\u2019s one way. https:\/\/firehydrant.com\/blog\/incident-severity-why-you-need-it-and-how-to-ensure-its-set\/ Paper:\u2026","rel":"","context":"In "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":725,"url":"https:\/\/fde.cat\/index.php\/2023\/06\/19\/sre-weekly-issue-377\/","url_meta":{"origin":482,"position":3},"title":"SRE Weekly Issue #377","date":"June 19, 2023","format":false,"excerpt":"View on sreweekly.com A message from our sponsor, Rootly: Curious how companies like Figma, Tripadvisor, and 100s of others leverage Rootly to manage incidents in Slack and unlock instant best practices? Check out this lightning demo: https:\/\/www.loom.com\/share\/051c4be0425a436e888dc0c3690855ad Articles Why did AWS Support fail with US-EAST-1 again? AWS had a major\u2026","rel":"","context":"In "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":466,"url":"https:\/\/fde.cat\/index.php\/2021\/09\/16\/autonomous-monitoring-and-healing-networks\/","url_meta":{"origin":482,"position":4},"title":"Autonomous Monitoring and Healing Networks","date":"September 16, 2021","format":false,"excerpt":"Autonomous Monitoring and Self-Healing Networks Occasional failure is inevitable in any network system. The need of the hour is a robust, self-reliant automated monitoring tool that provides great insight and a lesser degree of manual intervention. We need autonomous interventions that save us time and enhance system availability. What Salesforce\u2026","rel":"","context":"In "Technology"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":645,"url":"https:\/\/fde.cat\/index.php\/2022\/10\/31\/sre-weekly-issue-345\/","url_meta":{"origin":482,"position":5},"title":"SRE Weekly Issue #345","date":"October 31, 2022","format":false,"excerpt":"View on sreweekly.com SRE Weekly is now on Mastodon at @SREWeekly@social.linux.pizza! Follow to get notified of each new issue as it comes out. This replaces the Twitter account @SREWeekly, which I am now retiring in favor of Mastodon. For those of you following @SREWeekly on Twitter, you\u2019ll need to choose\u2026","rel":"","context":"In "SRE"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/posts\/482","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/comments?post=482"}],"version-history":[{"count":0,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/posts\/482\/revisions"}],"wp:attachment":[{"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/media?parent=482"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/categories?post=482"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fde.cat\/index.php\/wp-json\/wp\/v2\/tags?post=482"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}