PHILADELPHIA (KYW Newsradio) — Facebook and its associated platforms are coming back online.
The social media congolmerate tweeted at 3:33 p.m. PT it was "happy to report" its "apps and services" were "coming back online now."
In the wake of Frances Haugen's revelations that Facebook deliberately downplayed how harmful Instagram is to young people, the company experienced widespread, hourslong outages Monday across all its applications. Some of its platforms were accessible just before 3 p.m. PT, although users still experienced issues with Facebook, Instagram and WhatsApp.
Facebook Chief Technology Officer Mike Schroepfer tweeted at 3:46 p.m. that it "may take some time to get back to 100%." He also apologized for the outages for the second time in three hours.
The company's network of services suddenly went offline Monday morning, with Instagram flashing a server error message and Facebook saying that something went wrong.
A quick snapshot from Down Detector, an outage tracking site, indicated the problems were widespread.
Just before 9 a.m. PT on Monday, there were over 86,000 reports of outages on the Facebook site, over 76,000 reports for Instagram and over 29,000 for WhatsApp.
Related
According to reporting by The Verge, the problem was likely DNS-related, which is the system in which domain names are cataloged on the internet. The problem seemingly affected Facebook's virtual reality platform, Oculus. And it’s affecting Workplace from Facebook customers and Facebook's internal sites.
The New York Times reported the outage extended to Facebook-owned buildings, with some employees unable to access conference rooms or even the buildings themselves due to issues with their digital badges. Facebook employees were also unable to send or receive emails from external addresses.
The outlet reported the company sent engineers to a Santa Clara data center for a "manual reset" of its servers.
In a twist, Facebook's domain appeared to be for sale, but GoDaddy told ABC News the sale listing has subsequently been removed.
Facebook first acknowledged the problem in a tweet Monday morning.
