platform_acknowledged: false). See methodology.
@degudluck01 publicly reports that Meta suspended their Facebook page on May 24, 2026, reportedly for content or activity that did not follow Meta's rules. No specific policy was cited. The suspension reportedly triggered a concurrent Instagram account suspension for the linked account (thegudluck01), which Meta's in-app notice explicitly states was caused by the Facebook page violation. An appeal was submitted on May 24, 2026 with no response as of the date of reporting.
Sources
Research patterns
All findings →Experienced something similar? See Resources for escalation paths by jurisdiction—EU/DSA, India, Turkey, and more. For US-based cases, Signal Flare covers the full stack: state Attorneys General, the FTC, and congressional offices.
This record is published under GDPR Art 89 public interest exemption. Data policy
Are you the subject of this record? Request erasure
The primary enforcement target appears to be the reporter's Facebook Page (creator/business page) rather than a personal Facebook account — the reporter's post explicitly states 'My Facebook page was suspended.' Meta's Instagram suspension notice uses the language 'a Facebook account that doesn't follow our rules,' which may reflect Meta's internal terminology treating Pages and accounts interchangeably for cross-product enforcement purposes. This is a reverse cascade from the pattern documented in PA-2026-0003, where Instagram was the primary enforcement target and Facebook cascaded. Here Facebook Page enforcement cascades to Instagram. The reporter was a monetized creator — the first monetized creator account in the dataset — who describes months of organic growth prior to the suspension. No policy or content was cited beyond 'Doesn't follow the rules,' the least specific enforcement reason in the dataset so far. The abrupt suspension of an active monetized creator page with no prior warning and no specific policy citation is consistent with automated detection. The Facebook Page vs. personal account distinction may indicate a schema gap in enforcement_action_type, which does not currently distinguish between Page-level and account-level suspensions.