Network
See every blocked connection — created by an agent's ban or flagged by the automatic flood detector — with why it was blocked, how long is left, and a one-click release.
What a "connection" means
A connection is the visitor's internet address — the IP address their browser connects from. For IPv6 addresses, which change constantly by design, it is the household-sized block of addresses instead of a single one. Blocking a connection stops the trick every banned troublemaker tries first: opening a private window, or clearing their site data, to come back as a brand-new visitor.
A connection block is deliberately narrow:
- It only stops new visitor sessions and new conversations from that connection on your widget. Anyone already mid-conversation on the same connection — a colleague on the office Wi-Fi, another customer behind the same mobile network — is never affected.
- It lasts at most 24 hours, however long the ban that created it. Internet addresses get reassigned, so a block that outlived a day could land on a stranger.
- A visitor turned away by it sees the usual quietly disabled chat input — no message about blocks or durations.
Where blocks come from
| Source | How it gets here |
|---|---|
| Agent ban | Someone banned a visitor from a conversation with Also block their connection ticked — the default on a full ban. See Inbox Sidebar Actions. The block lasts as long as the ban, capped at 24 hours, and lifting the ban releases it. |
| Automatic | Yaplet's flood detector noticed one connection creating an unusual number of new visitors or new conversations within 24 hours — the signature of a script, not a person. |
The list
The tab shows every open block plus the last 30 days of history. Opening it needs the Security permission, like the rest of the Security page.
| Column | What it shows |
|---|---|
| Connection | The address that was blocked. IPv6 entries add a note with the block of addresses covered. |
| Source | Agent ban or Automatic. |
| Status | Blocked (in force now), Would have blocked (automatic, watch-only), Expired (ran out on its own), or Released (lifted by a person). |
| Why | The ban reason for an agent ban; for the detector, the count that tripped it — for example 23 new chats from this connection in 24 hours. |
| Created | When, and who created it. |
| Expires | When it ends, with the hours left — or who released it. |
Releasing a block
Release on a Blocked or Would have blocked row lifts the block immediately. Only the connection part is lifted: the ban on the visitor it came from stays in force — unban that from the conversation or from the Banned visitors tab. Anyone the connection block had turned away is let back in the next time their widget loads. Visitor opens the security profile of the visitor the block came from, where the block also appears in the "This visitor is blocked" banner.