Users reported that their Facebook accounts were suddenly logged out and could not be accessed again, both on the app and web version.
On March 5, 2024, all Facebook, Messenger and Instagram accounts were suddenly logged out when used on a laptop. Even though I tried to log back in, the browser kept saying "website is unavailable, link is broken or deleted".
Facebook reported an inaccessible error at 10:30 p.m. on March 5
One girl shared, "I thought my computer was hacked, so I switched to texting using the app on my phone, but my account was also thrown out and I couldn't log in." She turned to the Instagram app to update the situation, but the app also announced "Cannot download newsletter".
On Downdetector, a tool specializing in monitoring the performance of Internet services, in just 10 minutes from about 10:30 p.m., the number of error reports from users of Meta's platforms jumped to nearly 400,000, including Facebook, Messenger, Instagram, Threads, but WhatsApp are not affected.
The number of Facebook error reports reached more than 300,000 on March 5.
Hundreds of thousands of users said they could not access it again and had to go to other social networks and messaging services such as X, Telegram... to notify. Some even have to use traditional calling and SMS texting methods to maintain contact.
Meta representatives have not yet commented on the incident.
A similar Meta error occurred in 2021, causing a series of the company's services to become inaccessible on all platforms and in many regions around the world, lasting for 6 hours. At that time, Meta said the problem was caused by a "configuration error" on the system. In 2019, the web version of Facebook also lost connection for 24 hours.
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.
