Why “reports”: this record captures what the affected person publicly said happened and what the platform’s own enforcement notice showed. The source is archived below. The platform has not acknowledged this action ( platform_acknowledged: false). See methodology.
PA-2026-0041 Meta Account suspend Source confirmed Draft

@hekiwomattousu publicly reports that Meta suspended their Facebook account on April 24, 2026, reportedly without a cited policy basis. An appeal was filed but received no response in over one month, exceeding Meta's stated review SLA of approximately one day. Simultaneously, the Meta Verified 'Get Support' feature reportedly returned an error ('This page isn’t available right now'), preventing the reporter from opening a new support case despite active Verified subscription status. Three Meta case IDs are documented (1699688678125590 / 7380272726536577 / 9077880022853889), confirming internal acknowledgment with no resolution.

REPORTED_BY
@hekiwomattousu
PLATFORM
Meta
ENFORCEMENT_ACTION_TYPE
account-suspend
Account access restricted, not permanently removed
PLATFORM_POLICY_CITED
Bare citation; no specific policy domain named
AI_SYSTEM_INVOLVEMENT
APPEALS
AI system handled or influenced the appeal process
DATE_FROM / DATE_TO
Apr 24, 2026
VERIFICATION_LEVEL
SOURCE_CONFIRMED
Enforcement notification screenshot present in source
PLATFORM_ACKNOWLEDGED
false
CONFIDENCE_SCORE
4 / 5
Rubric: enforcement notification + archive confirmed
SCHEMA_VERSION
1
CREATED_AT
Jun 9, 2026

Sources

Curator commentary

This case documents two simultaneous appeal-access failure modes from a single incident — appeal-by-inaction (1+ month past stated SLA) and support-channel access blocking (Meta Verified Get Support page returning an outright error, preventing new case creation) — occurring concurrently rather than sequentially. The co-occurrence distinguishes this case from prior records where each mode appeared in isolation. Three Meta case IDs confirm internal tracking acknowledged the case multiple times without producing a visible response, extending the pattern from PA-2026-0006. As a Meta Verified subscriber, the reporter’s paid escalation channel was completely non-functional — not AI-chatbot-gated as in PA-2026-0033, but returning an outright error. No policy citation visible in either screenshot. Japan-based user (Japanese-language UI) — first non-English-UI record in the dataset, confirming the null-citation and appeal-inaction patterns are not specific to English-language enforcement notices.

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