Add /32 whitelists

Enter one per line, separated by spaces or commas. Up to 500 per batch. Each address must be inside a prefix you can edit.

Saved rules stop future mitigation after the monitor reloads. Use Current attacks → Unban to clear an active ban.

Authentication

Tokens only disables PeeringDB web login. Create and copy an administrator token before switching; your PeeringDB session will end.

One HTTPS origin per line. Server-to-server integrations do not need an origin entry.

Create token

Leave blank to generate a random token when creating it. Rotation replaces an existing token string.

Simulation

Traffic and mitigation state are isolated from live measurements. The monitor sends no attack packets. Simulations use the current saved policies.

Running the mitigation script can install real mitigation for this destination. Use a destination intended for testing. Stopping synthetic traffic does not remove installed mitigation; clear the test mitigation separately.

Prefix policy settings

Only settings checked as “Apply this setting” are saved. Red rows show explicit values to apply. Blank monitor values remove the override and inherit applicable settings. Other settings and more-specific policies are preserved.

Manual mitigation has no automatic expiry. Automatic mitigation for this host stays suspended until you clear it with Unban under Current attacks. Blackhole requests can discard all traffic to this host.