Facebook, Messenger Websites Experience Widespread Outage in Vietnam

On the afternoon of July 19, a widespread outage affected access to Facebook and Messenger websites in Vietnam. Mobile applications remained functional. Around 2:30 PM, Nguyen Hung in Hanoi attempted to access Facebook on his computer to check work messages but could not connect. He repeatedly received a notification stating, "Your account is currently unavailable due to a website issue," initially leading him to believe his account was locked or compromised. "I tried logging in multiple times but received errors for both Facebook and Messenger. It was only when I opened the app on my phone that I realized my account was still working normally," Hung stated. Not only Hung, but many users in Vietnam and globally have reported similar situations. According to the outage tracking site Downdetector, Facebook error reports surged around 2:39 PM Vietnam time, exceeding 3,000 within minutes. The platform's statistics indicate that 61% of reports relate to being unable to access the Facebook website, with the remainder experiencing login or app issues. On social media platforms like X and Threads, users worldwide have reported that when accessing the Facebook website, their accounts display a "temporarily unavailable" message, with reasons such as "The link you clicked may be broken or the page may have been removed." Meanwhile, the Facebook and Messenger applications on mobile phones operated normally, allowing users to view their news feeds and send/receive messages. Other Meta products, such as Instagram and Threads, did not report significant issues. Meta has not yet issued an official statement regarding the cause or the scope of the outage. This is not the first time Meta's platforms have experienced outages this year. In June, Facebook, Messenger, and Instagram were disrupted for about an hour, preventing many users from logging in, loading their news feeds, or sending messages. According to Downdetector, tens of thousands of error reports were recorded globally before services were gradually restored. Meta later confirmed the issue was resolved but did not disclose the specific cause.