Malaysian legislator details personal experience of Meta ban wave following Facebook and Instagram suspension

A Malaysian state legislator has reached out to share their firsthand experience of getting caught up in Meta’s ongoing mass account suspension crisis that I’ve been tracking for over a month now.

Lim Yi Wei, who represents Kampung Tunku in Selangor’s state assembly, contacted us after following my coverage of what users have dubbed the “Meta Ban Wave.” Her story adds another dimension to this crisis, showing how even government officials aren’t immune to Meta’s automated enforcement gone wrong.

On June 20, around 5pm, Lim found herself suddenly logged out of Facebook with her account suspended for allegedly violating Community Standards. Like thousands of others I’ve documented, she had to go through the facial verification process, submit government ID, and wait for an outcome. Her Instagram account got suspended too since it was linked to Facebook.

What makes Lim’s case particularly interesting is her role as an elected representative. She mentioned that 95% of her Facebook activity happens on her official page to communicate with constituents about policy and community matters. Her Instagram is similarly work-focused, being 90% professional content. Yet Meta’s systems flagged both accounts anyway.

The timeline of her suspension shows just how chaotic this whole situation has become. After contacting Malaysia’s deputy communications minister, who then alerted Meta Singapore, her accounts were restored on June 24. But the relief was short-lived. That same afternoon, both accounts got suspended again. She had to appeal once more and provide additional ID verification before getting restored on June 26.

This back-and-forth pattern matches what I’ve been seeing across social media platforms where users report getting their accounts back only to face another suspension days later. It suggests Meta’s automated systems are still misfiring even after manual reviews.

Lim’s experience also highlights the human cost of these mass suspensions. For elected officials like her, social media isn’t just personal networking but an essential tool for constituent communication. Business owners face similar pressures, with some losing thousands in daily revenue while their accounts remain suspended.

What struck me about her account is the lack of transparency in Meta’s process. Like others have detailed, she received no specific details about what content allegedly violated Community Standards. This makes it nearly impossible for users to understand what went wrong or avoid future suspensions.

Lim has even highlighted this on her X account with a dedicated thread that you can check out below:

The situation has gotten so bad that it’s drawing government attention internationally. Just this week, I reported on South Korea’s National Assembly scheduling an emergency meeting with Meta Korea executives after lawmakers got overwhelmed with complaints from affected users.

Lim’s story reinforces what I’ve been documenting for weeks now. This isn’t just a technical glitch affecting a few accounts. It’s a systematic failure that’s impacting real people’s lives, businesses, and in this case, democratic communication between elected officials and their constituents.

Meta has remained largely silent about the scope of these mass suspensions and is refusing to take any accountability. For someone like Lim, who relies on these platforms for official duties, that silence is particularly concerning.

Her experience shows that even when users have connections to government officials who can escalate cases directly to Meta’s regional offices, the underlying system problems remain unresolved. If a state legislator can get suspended twice in a week despite having official channels to resolve the issue, regular users face an even steeper uphill battle.

I’ve reached out to Meta for comment on the ongoing mass suspension issues and will update this story with their response, if any.

You can read Lim’s whole report on this (unedited) in the document embedded below, or head here if you’re on a mobile device.