Claude tombstones Ban log

rip.monk.party

How this yard is kept

Claude tombstones is a log. When someone says, in public, that their Claude account was banned, suspended, or disabled, we keep one sentence and a link. We do not speak for Anthropic, and we do not decide why an account went away. The reason on a row is the poster's guess.

Where the posts come from

  • V2EX, through the public sov2ex search.
  • Linux.do, a Discourse search. If Cloudflare challenges the worker, that run is recorded as a miss and the other sources still run.
  • Hacker News, through the Algolia API.
  • Reddit, search.json on r/ClaudeAI, r/Anthropic, and r/ClaudeCode. A 403 or 429 is recorded, not retried in a loop.
  • GitHub issues in anthropics/claude-code and anthropics/claude-desktop.
  • X. This worker cannot call the X API. An outside routine pushes posts to POST /api/ingest with the INGEST_TOKEN secret. The same endpoint accepts any source.

How often

A cron run starts every 3 hours, at minute 17. The first successful run of a source looks back 30 days. Later runs look back 3 days. You can also ask for a run with POST /api/admin/run?source=v2ex and the same bearer token. ?backfill=1 forces the 30-day window.

How a post gets onto the yard

We ask a fixed set of questions: is this a real ban report, is it an ad, what reason did they guess, what happened with an appeal or a refund, which plan, how old was the account. If MONK_API_KEY is set, a small model at api.monk.party answers those questions as JSON, and deterministic rules make the final labels. Without the key, the same rules run on keywords in Chinese and English. Ads (selling accounts, top-ups, group buys, promotions) stay out. So does a second copy of the same story. We store the short line, never the full post.

What we leave out

Questions about how to avoid a ban, worries that a ban might happen later, and anything that is selling a seat. If we kept something you wrote and you want it gone, write to support@monk.party with the link. We will hide the row.