Forever Couch Gang

Blocking high-confidence bots

The wall has stopped 15 bots at the gate during this server window. People who pass the visitor check are counted separately.

High-confidence bots are stopped at the gate. Real visitors who see a check can always get through.

ACTIVE · BLOCKING

HOLDGATE

  • Checks issued

    3

    Real visitors, this server window

  • People who passed

    0

    Completed the visitor check

  • Not verified

    3

    Issued and not completed

  • Stopped at the gate

    15

    This server window

Ambient audio stays off.

A local animation only. Live blocking continues separately. This control does not send traffic, hit an endpoint, or test the live guard.

Last 24 hours

Last 24 hours: 15 stopped, 0 passed the visitor check, 3 not verified.

Checks issued3
People who passed0
Not verified3
Stopped15

Timeline sparkline uses the sealed daily record, not a guessed lifetime total.

Live activity

Anonymized events only. No addresses, tokens, rules, or paths.

  • Form-safety rejection (not a bot stop)
  • Form-safety rejection (not a bot stop)
  • Form-safety rejection (not a bot stop)
  • Visitor checked
  • Visitor checked
  • Visitor checked
  • Visitor checked
  • Visitor checked
  • Visitor checked
  • Visitor checked
  • Visitor checked
  • Visitor checked
  • Visitor checked
  • Visitor checked

Practice attacks we run on ourselves

Practice attacks we run on ourselves. These are never mixed into real visitor totals.

Practice sent326,338
Practice stopped326,338
Practice passed2,430
Practice stop rate100%

Tamper-proof daily record

Finished days are sealed. Today stays unsealed until the day closes.

  • 2026-10-12 · today (unsealed)

    Today’s running total (not sealed yet).

    15
  • 2026-10-11 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    0
  • 2026-10-10 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    0
  • 2026-10-09 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    0
  • 2026-10-08 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    0
  • 2026-10-07 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    0
  • 2026-10-06 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    2
  • 2026-10-05 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    1
  • 2026-10-04 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    10
  • 2026-10-03 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    135
  • 2026-10-02 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    114
  • 2026-10-01 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    0
  • 2026-09-30 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    69
  • 2026-09-29 · sealed

    Sealed daily total chained to the previous day. Older days may still include mixed legacy events.

    13

Legacy figure — not a verified total

Earlier mixed “bots blocked” count

22,608

22,608 is a mixed count from an earlier period. That period included events that were not confirmed bots, and stops were not counted the same way each time. It is not a permanent total and cannot be combined with the verified checks, passes, or stops on this page.

This 22,608 figure is a legacy mixed count from an earlier period. That period counted things that were not confirmed bots, and it counted stops inconsistently. It is not a permanent total. It is never added to today’s verified checks, passes, or stops.

What these numbers are not

Pass and fail refer only to the visitor check (a short accessible question). Sign-in errors, CSRF, and other HTTP failures are counted separately and are not shown as challenge fails.

Loading visitor check…

How the wall works

plain language
01
A visitor arrives
The wall looks at how the request behaves — not at a purchased puzzle, and not at a public list of secret rules.
02
A check is recorded
When the wall is unsure, it asks a short accessible question. Passing that check is “Humans who passed.” Not passing it is “Not verified.” Sign-in errors are something else.
03
Blocking is on
The live mode is enforce: high-confidence bot traffic can be stopped. Visitor checks still never use a silent 429. This page reads that mode from the live numbers payload, so a flip cannot leave watching-only wording behind.
04
Practice stays in its own bucket
We send fake attacks at ourselves so we can see the wall work. Those runs are labeled practice and are never mixed into real visitor counts.