When Facebook Says Your Account Is Suspended, the 180-Day Clock Has Already Started

Two Facebook accounts can present the same symptom — the login goes nowhere — and still need completely different actions. The wording on the screen is what separates them. Facebook's help pages treat locked, suspended, disabled and limited as four separate states with four separate procedures, and only one of them carries a published deadline. That deadline is 180 days, it starts when the suspension is applied, and letting it lapse converts a reversible state into a permanent one.

Every menu path, number and quoted phrase below comes from Facebook's Help Center, Meta's Transparency Center or the Oversight Board's own publications, checked in August 2026. Where Meta publishes nothing, that gap is stated rather than filled with a plausible-sounding figure.

Read the Login Screen Before Doing Anything Else

Facebook's account recovery pages describe the states in language that is close enough to be confused and specific enough to be used as a test. A locked account produces an email saying the account was locked, and a message at login saying the same thing. A suspended or disabled account produces something different: the help page states that at login you will see either We suspended your account or We disabled your account, and that notice also arrives by email.

Those two sentences are not synonyms. One of them is the start of an appeal window. The other, in the most common path, is the end of one.

A fourth state does not block login at all. Facebook describes accounts with limited access as ones that can still browse but cannot comment on posts or send friend requests, and the cause it names first is not a Community Standards violation but a suspicion that a computer used to access the account carries a virus or malicious software. That page also notes access may behave normally on another computer, phone or tablet.

A Locked Account Is a Security Checkpoint, Not an Enforcement Decision

Facebook's page on unlocking an account frames the lock as a response to unusual activity on the account, applied for security. The procedure is short and it does not involve an appeal form: open Facebook, select Get started, and follow the on-screen steps. The page adds that identity confirmation may be requested as part of those steps.

The failure most often reported at this stage is not the lock itself but the confirmation code that never arrives. Facebook's published troubleshooting for that is worth following in order, because two of the items are counter-intuitive:

• If several codes have already been requested, wait a day before requesting again. Repeated requests are named specifically as the case where waiting is the correct action.
• Check the blocked messages list on the phone. Facebook's page notes that a handset may be screening or blocking confirmation code texts without any visible sign.
• Confirm the code is being sent to the number or address currently on the account, and check the spam folder.
• Check that the handset has enough free space to receive an SMS, and restart it.
• Contact the carrier: Facebook states a mobile plan can affect which message types a line is able to receive.

If login itself is impossible, that is a recovery problem rather than a lock problem, and it moves to facebook.com/login/identify. If someone else took over the account, Facebook routes that case to facebook.com/hacked and specifies it should be opened on a device previously used to log into Facebook. That device condition is easy to miss and it changes the outcome.

The Suspension Window Is 180 Days, and It Runs Whether or Not It Is Used

This is the part of the process with a hard number attached, and it is the part most often misread as a formality. Facebook's page on suspended and disabled personal accounts states that a suspension can be appealed within 180 days, and that if it is not appealed within that period, or if the appeal is not successful, the account will be permanently disabled.

Two details follow, and both matter operationally.

First, the appeal is not filed through a separate contact form. The page says to log into Facebook, at which point the appeal prompt is presented. The login attempt that appears to fail is the entry point to the appeal, not an obstacle in front of it.

Second, the page states that the time period available to appeal varies by region. The 180-day figure is the one Facebook publishes on that page, but it is not presented as universal, and the prompt shown at login is the authoritative version for a specific account.

After that window closes, the same page is explicit that another review of the decision cannot be requested. Meta's Transparency Center describes a narrower situation for accounts disabled without a suspension first — for example severe or time-sensitive violations — where users are told whether a further review is available. So "disabled" is not uniformly the end of the road, but a disable that arrived at the end of an unused 180-day suspension is.

The Strike Ladder Explains the Length of a Restriction

When the account still works but a feature does not, the strike system usually accounts for it, and Meta publishes the ladder rather than leaving it to inference. A first strike produces a warning. Strikes two through six produce restrictions on specific features, such as posting in groups, for a limited period. From the seventh strike the restriction is on creating content generally, and the duration is fixed by the count: one day at seven strikes, three days at eight, seven days at nine, and 30 days at ten or more.

The counting rules are as load-bearing as the ladder. Meta states that all strikes on Facebook or Instagram expire after one year. For standard violations, content posted more than 90 days ago is not counted as a strike; for severe violations that window extends to four years. Meta also notes that several removals announced at the same time may count as a single strike, and that some removals do not carry a strike at all.

Against that ladder there is a separate, blunter path: a single violation can be severe enough for the account to be disabled after one occurrence, with child sexual exploitation content given as the example. Meta also lists categories that lead to disabling on discovery rather than by accumulation, including accounts created to evade a previous removal and accounts misrepresenting identity in order to deceive.

Two Different Status Screens, Two Different Paths

Facebook documents two screens that answer two different questions, and they are reached by different routes on the desktop site. Confusing them wastes time because only one of them contains the button that starts a review.

Account Status shows the state of the main profile, the state of Pages and groups being managed, and any restrictions attached to them, including Community Standards strikes, limited monetisation and recommendations status. Facebook's path for it, as published in August 2026: click the profile picture in the top right, select Help & support, then Account Status.

The route to disagree with a specific removal is documented separately and uses different labels. Facebook's page on content it should not have taken down gives this path: click the profile picture in the top right, click the profile name, click Options, then Profile Status, open the message about the removal, and if the option appears, click Request review. Two published paths with two different names for the same area is an inconsistency in Meta's own documentation, and either route is worth trying if one does not show the expected screen.

The Support Inbox is where responses land. Its path is the profile picture in the top right, then Help & support, then Support inbox. Facebook's page on limited access points there explicitly as the place to check for status updates, and the Oversight Board route depends on a message that arrives there.

What the Identity Check Will and Will Not Accept

Identity confirmation appears in the locked-account flow and in several recovery flows, and the requirements are published in enough detail to prepare for in advance. Facebook accepts one government ID, which must show either a name and date of birth, or a name and a photo. If no government ID is available, it accepts two different non-government IDs instead: all of them must show the name, and at least one of the two must show a date of birth, a photo, or both. The name on the documents must match the name on the profile.

Facebook lists five reasons an ID photo is rejected: blurry, not well-lit, missing the required information, a picture of a screenshot or a photo-copied ID, and not fully in frame. It also draws a line that is easy to cross by accident — images digitally modified to hide information are not accepted, while physically covering non-essential fields before photographing the document is explicitly permitted. Facebook adds that submitting more documents than required may delay the review.

On retention, Meta states the storage period depends on the purpose and is disclosed before the upload. The figures it publishes as examples: up to 180 days for an ID uploaded to get verified to run ads or for Meta Verified, extended to up to one year where fraud or abuse is detected or for ads about social issues, elections or politics. Meta also suggests deleting the captured photo from the device gallery afterwards.

The Oversight Board Handles Content Decisions, Not Account Decisions

The Oversight Board is frequently suggested as the escalation point for a disabled account. For the ordinary case it is not one, and the eligibility rules say so directly.

Meta's published route requires exhausting its own appeals process first and receiving a final content decision. That decision arrives as a message in the Support Inbox on Facebook containing a reference number, which is then entered on the Board's site to establish the link between the two systems. The Board's FAQ states the reference ID begins with FB or IG followed by eight numbers and letters.

The constraint that decides most cases is in the same FAQ: to submit an appeal, a person must have an active account on the service where the content was posted — the account cannot be disabled, and the person must be able to log into it. A disabled account therefore fails the entry condition for the route people are most often pointed toward. Meta also states plainly that not all decisions are eligible, and that the Board selects only a limited number of the eligible appeals it receives.

That gap is not a matter of interpretation. On 5 June 2026 the Oversight Board published the outcome of its first case focused on account disablement. It upheld Meta's permanent disabling of the Instagram account in question, and recommended that platforms provide a fair and effective appeals process for users whose accounts are disabled, including the opportunity to give written reasons, and that account status and appeal options stay reachable after disablement. Recommendations describe what the Board argues should exist, not what is available today.

What Meta Does Not Publish

Three numbers people reasonably expect to find are not published anywhere in Meta's documentation. Any figure offered for them elsewhere is an estimate.

• Review turnaround. No page in the Help Center or Transparency Center gives a target or maximum time for reviewing an appeal. What Meta does state is a capacity caveat: during busy periods it may not be able to review everything, and it may not be able to review all requests.
• Automation thresholds. Meta describes using technology and review teams to detect and act on content, but publishes no threshold, confidence score or volume trigger at which an account is actioned automatically. The Oversight Board's June 2026 recommendations include asking platforms to disclose whether and how AI was used in a penalty decision — a recommendation that only makes sense because the disclosure does not currently exist.
• Odds of reinstatement. Meta reports appealed and restored content in aggregate in its enforcement reporting, but publishes no success rate for account-level appeals.

When This Doesn't Apply

The four-state frame above is a reading of Facebook's published enforcement path. Several situations look identical from the login screen and are governed by something else entirely:

• A compromised account. If the loss of access followed a takeover, the enforcement path is the wrong one; Facebook routes that to facebook.com/hacked from a previously used device.
• A profile the account holder deactivated. Deactivation is reversible by logging back in, or through Accounts Center for an additional profile, and is unrelated to strikes. It requires access to the email address or mobile number used to log in.
• Limited access caused by malware detection. Facebook states this can resolve on its own once the underlying problem is fixed, and that it can take a few days. There is no appeal step in that path.
• Pages, groups and business assets. Account Status covers them, but Pages have their own removal and limitation rules, and Meta Pay has a separate disabled-account article. A personal profile appeal does not carry them.
• Region. Facebook states the appeal period varies by region. The 180-day figure is what its help page publishes; the prompt shown at login governs a specific account.
• Age-related holds. Where age needs confirming, Meta routes verification through a third-party provider, and the accepted document set narrows to IDs showing both a face photo and a date of birth.

The Order to Work In

1. Copy the exact wording on the login screen and the email subject line. That text selects the procedure, and it disappears once the flow moves on.
2. If the wording is a lock, run the checkpoint: open Facebook, select Get started, follow the steps. If codes are not arriving and several have been requested, wait a day rather than requesting more.
3. If the wording is a suspension, log in immediately and complete the appeal prompt. Treat the date on the notice as day zero of a window that is 180 days at the outside and may be shorter by region.
4. If the account still works, open Help & support → Account Status and read the strike count and restriction end date before assuming anything about cause.
5. To contest a specific removal, use the documented review path — profile name → Options → Profile Status → open the removal message → Request review — and keep the reference number that arrives in the Support Inbox.
6. Before uploading identity documents, check the photo against the five published rejection reasons, and send only what is asked for.
7. Check the Support Inbox for the response rather than waiting on email alone, and do not treat silence as a decision: Meta publishes no review turnaround at all.