Like Facebook’s Antigone Davis was live on CNBC When he was defending the company against a whistleblower’s allegation and handling of research data suggesting Instagram is harmful to teenagers, the company’s entire service network suddenly went offline. The outage started just before noon ET, and nearly four hours later, there is no sign or recovery, and no one from the company has given an explanation of the problems or estimates of when they will be fixed.
On Twitter, Facebook communications director Andy Stone says, “We understand that some users are having problems accessing our apps and products. We are working to get things back to normal as soon as possible and we apologize for any inconvenience. “
A look at Down Detector (or your Twitter feed) shows that the problems are widespread. While it’s unclear why the platforms are inaccessible to so many people, their DNS records indicate that, as with last week’s Slack outage, the problem appears to be DNS (it’s always DNS).
Cloudflare Senior Vice President Dane Knecht Remarks that Facebook’s border gateway protocol routes – BGP helps networks choose the best route to deliver internet traffic – were “pulled from the internet”. While some have speculated about hackers or an internal protest against last night’s whistleblower report, there is still no information to suggest anything malicious is responsible.
We know that some users are having problems accessing the Facebook app. We are working to get everything back to normal as soon as possible and we apologize for any inconvenience.
– Facebook app (@facebookapp) October 4, 2021
Instagram.com flashes a 5xx Server Error message while the Facebook site just tells us that something went wrong. The problem also seems to affect his virtual reality arm, Oculus. Users can load games that are already installed and the browser works, but social features or installing new games cannot. The outage is so severe that it affects Facebook customers’ workplaces and after Jane Manchun Wong, the internal pages of Facebook.
Update October 4, 3:37 p.m. ET: Added additional information about the ongoing outage.