Facebook, Instagram and Messenger inaccessible: what we know about the outage that affected Meta


Image: Chesnot/Getty Images.

Were you logged out of your Facebook, Messenger, Threads or Instagram account yesterday afternoon? You are far from the only one!

Yesterday, around 4:30 p.m., users around the world started complaining that their accounts had been disconnected from Meta services. We quickly realized that the problem was global, and that no one seemed to be able to use their Meta account.

The website DownDetector, which monitors internet outages in real time, says that as of 4:45 p.m. (Paris time), nearly 400,000 people had reported problems on Facebook.

” An unknown error has occurred “

During the outage, if you tried to connect, the service returned you an error message: “An unknown error has occurred.” Attempts to reset the password had the same result. Even two-factor authentication didn’t work: the code was sent, but the prompt to enter it never appeared.

Meta spokesperson Andy Stone spoke out after the outage ended, citing a “technical issue that resulted in difficulty accessing some of our services.” Before adding: “We resolved the issue as quickly as possible for everyone affected and we apologize for the inconvenience caused. »

All Meta services affected

Meta status, the Meta website which tracks the status of the company’s services, displayed “major disruptions” for several tools including Ads Manager, Facebook and Instagram stores, but also the Meta Business suite, the WhatsApp API Business and Messenger API. Surprisingly, the site showed “No known issues” for Messenger, even though many testimonials seemed to indicate otherwise. As of 6 p.m., all services reported that they were “recovering from an outage.”

With all top-down platforms using Meta to connect, early speculation indicates that the cause may be related to Meta identity and access management. No network outages or massive DDoS attacks have (yet) been reported.

In 2021, a similar outage occurred. It followed a problem during a faulty configuration change.

Source: ZDNet.com



Source link -97