A Discord raid is not random. Someone decided your server was worth hitting: a rival community, a drama thread that went the wrong way, a scam crew that scraped your invite link, or a bored group with a bot farm. The raid itself lasts minutes. Whether it costs you members depends almost entirely on what you set up before it started.

We work on raid detection at collony.ai, so this is a pattern we watch daily. Here is what actually works, split the way you experience it: before and during.

Know what kind of raid you are dealing with

• Join floods. Dozens to hundreds of fresh accounts joining in seconds, then spamming or just inflating numbers. The classic, and the easiest to stop.

• Slow raids. Aged, real-looking accounts trickling in over hours, then acting together. Rate-based protection never fires, which is the point.

• Content raids. Accounts already inside flooding channels with spam, slurs or NSFW content, often triggered by an event or announcement.

• Nukes. A compromised mod account or malicious bot deleting channels and mass-banning. Rare, catastrophic, and preventable with permission hygiene.

Before: set up the defenses that decide the outcome

Raise the entry cost

In Server Settings, set verification to at least Medium so accounts need a verified email and some account age. Turn on Discord AutoMod's mention spam and keyword rules. For servers over a few thousand members, add a join gate with risk scoring rather than a plain captcha, because modern raid tooling solves captchas fine. What it cannot fake cheaply is account history and behavior.

Lock down permissions before you need to

Nukes succeed through over-permissioned roles. Keep Administrator to as few people as possible, require 2FA for moderation, audit bot permissions quarterly, and never give a new bot more than it demonstrably needs. Anti-nuke tooling like Wick can rate-limit destructive actions so one hijacked account cannot delete forty channels in a minute.

Prepare a panic plan

Decide now what one person can do alone at 3am: pause invites, lock @everyone posting in key channels, enable slow mode everywhere. Write it as a pinned checklist in your mod channel. Some bots bundle this into a single panic command, which is worth configuring precisely because raids happen when the fewest mods are online.

Add detection that reads coordination

Everything above raises the cost of a raid. None of it recognizes one. Rate limits catch join floods, but slow raids of aged accounts pass every static check, which is where behavioral detection earns its place: synchronized join timing, identical or templated messages, accounts that never speak until they all speak at once. That coordination signal is what a dedicated protection layer is for, and it is the difference we built collony.ai around.

During: the response order that works

Order matters more than speed. The goal is to stop the inflow first, then the noise, then clean up.

• 1. Pause invites. Server Settings, Invites, Pause. This stops the inflow instantly and is the single highest-value action.

• 2. Lock the loud channels. Slow mode at 30 seconds or more, or remove posting for @everyone in the channels being hit.

• 3. Ban by pattern, not one by one. Sort recent joins by join date and remove the wave together. Bots with mass-action tools make this minutes instead of an hour.

• 4. Say one calm thing. A single mod message that the raid is handled stops the panic reposts that double the noise.

• 5. Afterwards, close the hole. Check which invite the wave used, rotate it, review what the raiders targeted, and tighten whichever defense they walked through.

The mistake that makes raids worse

Mass-banning everyone who joined in the last hour feels decisive and regularly catches real new members in the sweep, which converts a raid into a community trust problem. Quarantine-style responses, where suspect accounts lose posting rights but stay reviewable, cost nothing when the call is right and are reversible when it is wrong. Raids end. How you treated bystanders is what members remember.

Frequently asked questions

How do I stop a Discord raid in progress?

Pause invites first, that stops the inflow. Then slow mode or lock the channels being hit, mass-remove the join wave by join date, and post one calm mod message. Cleanup and invite rotation come after, not during.

Can Discord AutoMod stop raids?

Not really. AutoMod filters message content and mention spam, which blunts content raids, but it has no join logic at all. Join floods and slow raids need verification settings, a join gate and ideally coordination detection on top.

What is the best anti-raid bot for Discord?

Wick is the strongest dedicated anti-raid and anti-nuke tool, and Dyno's rate-based protection covers basic join floods free. For slow raids of aged accounts that pass captchas, you need behavioral detection like collony.ai that scores coordination rather than join rate. Our Dyno vs MEE6 comparison covers how the rule-based options differ.

How do raiders get into verified servers?

They buy or farm aged accounts with verified emails, solve captchas with paid services, and join slowly enough to stay under rate limits. That is why entry friction alone fails against a motivated raid and why behavior after joining is the more reliable signal.

Should I mass ban everyone who joined during a raid?

No. Sweeping bans catch real new members and damage trust. Remove accounts that match the wave's pattern, quarantine the uncertain ones so they stay reviewable, and reverse mistakes quickly.