Raid early warning signs hiding in your verification logs

Most raids announce themselves at the verification step before anyone posts a single message. Here is how to read those signals in RestoreCord and what to do in the first hour.

Short answer

Watch your log channel and the Firewall tab for sudden spikes in blocked verifications that share one reason, bursts of brand-new accounts and rising rate limits. Confirm against a normal day in Analytics, filter the firewall Activity Logs to find the pattern, then tighten the matching rule.

Why the front door shows it first

Raiders need roles to cause damage, and with RestoreCord in front of your server those roles only come through verification. That means a raid has to pass your checks first, and every failed attempt is recorded. If you know what normal looks like, the abnormal is easy to see.

Signals and where to see them

SignalIn the log channelIn Analytics
Same block reason over and overBlocked embeds repeating Alt or VPNBlocked count climbing on the Firewall tab
Burst of attemptsMany messages within a couple of minutesRate Limited events appearing
Very new accountsAccount age showing days, not years (Premium detail)Member Integrity shifting toward alt or fake
One source dominatingRepeated provider or location (IP Logging on)ISP or city spike (Business and above)
Password guessingFirewall embeds for password attemptsPassword Used rising faster than invites

What each block reason suggests

The reason on a blocked attempt usually tells you what kind of wave you are facing and which setting answers it.

  • Alt: the same person or group cycling through accounts; alt detection is on Premium and above.
  • VPN: attackers hiding their connection; anti-VPN and proxy blocking starts on Premium.
  • Wireless: mobile carrier connections, which Enterprise can block outright.
  • Account age: freshly made accounts, filtered by the Enterprise minimum account age setting.
  • Blacklist: known bad actors returning, often after a ban when auto blacklist is on.
  • Server: members of a server you blocked through firewall rules based on guild membership (Business and above).

Not every spike is hostile. A big partnership post or a giveaway can push verifications up just as sharply. The difference is the ratio: in a healthy rush Allowed rises with everything else, while in a raid Blocked climbs and Allowed barely moves.

Set a baseline before you need it

Open Analytics on the 7 or 14 day range during a calm week and write down roughly how many verifications and blocks a normal day brings. The analytics guide explains each figure. Without that number, every spike looks either terrifying or harmless.

The first hour of an incident

  1. Switch Analytics to the last 24 hours and compare blocked events with your baseline.
  2. Open the firewall Activity Logs, filter by event and see which outcome dominates: Blocked (Alt), Blocked (VPN), Blocked (Server) or invalid passwords.
  3. Tighten the protection that matches: alt blocking, anti-VPN, or a firewall rule for the source you found.
  4. If a genuine member gets caught, search their User ID and use Grant Temporary Access for 15 minutes up to 7 days.
  5. Keep the log channel open until blocks fall back to normal levels.

Clear Logs permanently deletes all firewall activity history. Finish your review and note the accounts and times first.

Make the alert reach someone

A log nobody reads is not an alert. Set the log channel's notifications to all messages for whoever handles raids, and consider a dedicated role for raid duty. Teams running their own on-call tools can forward firewall.block and member.denied events from an Enterprise custom webhook instead.

After it's over

Check Member Activity for the following days. Leaves (Business) and mass ping markers (Enterprise) show whether anything got through and how members reacted. If damage was done, a recent RestoreCord snapshot puts channels and roles back. Set up the log channel if you haven't yet, or return to RestoreCord Monitor.

Respond to a spike in four steps

  1. Confirm the spike

    Switch Analytics to the last 24 hours and compare blocked events on the Firewall tab with a normal day.

  2. Read the block reasons

    Filter the firewall Activity Logs by event to see whether alts, VPNs or one source dominate.

  3. Tighten the matching rule

    Adjust the firewall rule or protection that fits the pattern, such as anti-VPN or alt blocking.

  4. Watch the next hour

    Keep the log channel open and check that blocks fall back to your usual level.

Raid readiness checklist

Tick these off on a quiet day so the loud day is easier.

Baseline written down

You know roughly how many verifications and blocks a normal day brings.

Log channel pings the right people

Moderators on raid duty get notified for every new message in the log channel.

Rules ready to switch on

You've decided in advance which protections to tighten for alt, VPN or brand-new account waves.

Temporary access process agreed

Staff know who may grant a bypass and for how long while rules are strict.

Evidence kept before clearing

Nobody clears activity logs until the incident has been reviewed.

Backup is recent

A current snapshot exists, so even a raid that slips through can be rolled back.

Raid warning questions

See the raid before your members do

Put RestoreCord verification in front of your server and every suspicious attempt shows up in your logs first.