To everyone jumping to conclusions, remember that the words "server" and "configuration" can mean a whole host of things. It doesn't necessarily mean they mistyped their nginx config.
Largely impacted by this outage was how it affected those who use Facebook Login as a convenient OAuth option. Good thing for developers to remember if someone asks them to avoid a native login option.
.. but, but, didn't they wring the DevOps folks through coding challenges, sorting algos and whiteboard coding before hiring them? I heard that's the number 1 way to ensure uptime at FAANG.<p>(Configuration changes, that's the source of my sarcasm)
Also, 'many people had trouble accessing our apps and services' is some ninja-level gaslighting: <a href="https://twitter.com/facebook/status/1106229690069442560" rel="nofollow">https://twitter.com/facebook/status/1106229690069442560</a>
WAT. A server configuration change? What kind of server configuration can affect presumably thousands of machines replicated across the globe? I'm trying to understand this.
This is fucking bananas. For nearly a decade, Facebook has been at the forefront of innovating how code is deployed at global scale. They presumably have gradual rollouts, automated rollbacks, anomaly detection, not to mention (I assume) loads of organizational safeguards in place to ensure this sort of thing never happens.<p>Something else happened. This was not a configuration issue. Edit: If it was, I'd expect a post-mortem post-haste.