Updated on Friday, June 12, at 1:26 p.m. ET — Andy Stone, Meta VP of Communications, posted an update on X that stated Meta services were being restored.
This Tweet is currently unavailable. It might be loading or has been removed.
The Meta status page for its business services listed most of the June 12 disruptions as resolved. “We have recovered from an earlier outage impacting Ads Creation and Editing, and services have now been restored. We apologize for any inconvenience that this may have caused.” However, the WhatsApp Business Platform still showed “High Disruptions” as of this writing.
Updated on Friday, June 12 at 1:15 p.m. ET — As of this writing, the outages for Meta’s services appear to be on their way out, at least according to DownDetector. Meta has not provided an official cause for the outage yet, however.
Some of Meta’s products had a hard time on Friday morning.
Services like Instagram, Facebook, and WhatsApp all experienced temporary service outages to start the weekend. The cause is unknown at this point in time, but Meta’s VP of Communications, Andy Stone, acknowledged the outage on X.
Mashable Light Speed
Stone said Meta’s engineers are working on it.
This Tweet is currently unavailable. It might be loading or has been removed.
That’s not good.
Credit: Screenshot: Downdetector
In addition, the platform DownDetector recorded spikes in user error reports for Meta products on Friday. A peak of 10,000 users reported problems accessing Instagram, with the majority reporting problems with the app.
According to DownDetector users (Disclosure: Mashable and Down Detector have the same parent company, Davis), Facebook, Facebook Messenger, Instagram, and WhatsApp all experienced problems starting in the late morning on Friday. On top of that, Meta’s status page for its business applications also noted “High Disruptions” on Friday morning, too.
Anecdotally, multiple Mashable staff members have had a hard time posting or sending messages on Instagram during this outage. It’s unclear exactly when the problem will be resolved, but at the very least, Meta is aware of it and is doing something about it.
This is a developing story…
