Platform ban symptoms: 15 situations and what each one usually is

A platform ban example is usually described from the platform's side, by the name of the action. You experience it from the other side, as a symptom: something stopped working and nobody explained why. These fifteen situations start from the symptom. Not every platform ban example is enforcement, and several are something else entirely.

What to take away

Nothing was removed, but something changed

1. Reach collapsed overnight and nothing came down. Most likely a distribution reduction, which is the commonest action on most large services and the least visible. Nothing is removed and usually nothing is announced. Your own analytics history is the only evidence there is.

2. Your posts appear to you but not to anyone else. Same family as above, sometimes limited to a surface or a country. Caching and personalisation can produce the same appearance.

3. Comments you leave vanish within seconds. Usually an automated filter on the commenting surface, which is governed separately from posting. Check whether it happens everywhere or only under certain accounts; the difference tells you whether it is you or the destination.

4. Search no longer returns your account by name. Could be a discovery restriction, could be an indexing delay, could be a name that now collides with something else.

5. Everything works, but you have stopped appearing in recommendations. Rarely notified and rarely appealable. Treat it as a business signal rather than an incident: it is the clearest possible argument for holding a route to your audience that does not depend on the service.

Something was removed, blocked or restricted

6. One item came down with a notice naming a policy. A notice from YouTube, Facebook, or TikTok that names a policy is the most tractable case. Screenshot the notice in full, read the policy it names on the service's own site, and appeal on the narrow point that your item falls outside that category.

7. An item came down with no policy named. Assume automation. Write the appeal to the most likely category rather than asking which rule was applied, since asking usually spends the attempt without producing an answer. Some removals run through a statutory notice scheme rather than a policy one, with its own steps and its own counter-route: one country's copyright office describes such a framework at its overview of that scheme, which applies in that system alone. Where a service's obligations about notice come from a market regime, the European Union describes one at its page on rules for online services.

8. Content is visible in some countries and not others. Often a legal route rather than a policy one. The remedy sits with the authority in that country rather than with the service, and appealing to the platform is the wrong forum.

9. Posting is disabled for a period, everything else works. A feature restriction. These usually expire on their own. Use the time to complete the settings and export work in the settings pass, because a restriction is often a warning shot before something larger.

10. An old post was actioned years after publication. Re-scanning happens, and so does a reclassification following a policy change. The version of the rule in force when you published is the substance of any appeal, and you can only make that point with a dated copy you took at the time.

It looks like a ban, and it is something else

11. Login works but the dashboard says restricted. Check whether the restriction is on the account, on a linked business or advertising entity, or on a payout profile. These are separate objects with separate appeal routes, and appealing the wrong one is common.

12. Monetization stopped, the account is fine. A separate policy set with its own eligibility rules and its own appeal. Nothing about your posting status tells you anything about this, and the reverse is also true.

13. An API key or integration stopped working. X's developer terms are one example, and Developer terms are their own document with their own enforcement. A change there can be a deprecation rather than an action against you. Check the developer changelog before assuming anything.

14. The app store listing disappeared, the service still works. Apple's App Store or Google Play is a different company from the service, with a different rule set. The store's decision is appealed to the store, and it may turn on a rating or a declaration rather than on conduct.

15. A new account was blocked within minutes of creation. Usually a device, network or payment level block, or an evasion signal from an existing restricted account. Creating a replacement account while restricted is treated as its own violation on essentially every service and converts a temporary problem into a permanent one.

What every one of these needs first

The same three things, in the first hour, whatever the symptom.

Do those before drafting anything. The variables that determine how severe an outcome will be are covered in what moves the grade, which maps factors like recency, severity, and prior strikes. The full set of outcomes and their reversibility is in the eight outcomes, a list that ranges from a warning to permanent removal.

Using examples without over-reading them

An example helps you recognize a shape, nothing more. It does not prove anything similar happened to anyone, or say what a service will do. No two accounts share the same history, surface mix, or program obligations.

For money, employment, or a legal order, take the case to someone qualified where you are, not a pattern on a page.

Why the notices read the way they do is explained in how a moderation policy is built, a process that turns a rule into a template notice. Why the relationship is shaped this way at all is in the four asymmetries, which covers the imbalance in information and appeal rights.

Common questions

How do I tell a restriction from a bug?

Use the first-hour steps above to compare accounts, devices, and networks, then repeat over several days. One test proves very little, and services do ship broken releases.

Should I post publicly about it?

Occasionally it produces a response, and it also creates a permanent record you cannot edit and may complicate a resolution. Write down what you have captured, then decide afterwards.

Nothing on this list matches. Now what?

Describe the symptom precisely, in writing: the exact time, the surface, the account name, the error text, and what you expected to happen. Take that to the service's published contact route once. A vague report gets a template answer.