Note: Firewall features are only available on some paid plans
You can enter an IPv4 Address, an IPv6 Address, or a CIDR range into the Address field. See this guide (external website) for more information about IP addresses and CIDR ranges.
The note is just a text field for you to keep track of what the IP address is and why it's on your list.
Note: Sessions are counted for live connected IPs. If you set an IP to block, or pass, this count will no longer update.
CrowdHandler will show you the most prolific IP addresses currently connected to waiting rooms on this domain. The Sessions field shows you how many sessions are connected. Lots of sessions eminating from a single IP can be an indication of fraudulent or scraper-bot behaviour. There are however legitimate reasons why you might see more than one connection from a single IP address. The most common are:
1. Mobile Networks
Multiple devices often connect through a single IP.
2. Corporate Networks
It is common to see multiple sessions connecting through a single IP when those users are on a corporate network, as many devices will be connecting through a single router.
That said, seeing large numbers of sessions emanating from a small number of IP address generally indicates a problem. For that reason you can specify a maximum number of sessions to allow from a single IP.
Note: Agents are counted for live connected IPs. If you set an IP to block, or pass, this count will no longer update.
User agent strings identify the browser and device that is being used to access a CrowdHandler session. A very low number of agents correlated to a high number of sessions can be indicative of fraudulent behaviour.
Note: Connected since is tracked for live connected IPs. If you set an IP to block, or pass, this count will no longer update.
Connected since shows you when the IP first connected as long as the IP has one or more continuous sessions. A very long connection time can be indicative of a user or bot acting fraudulently.
You can set the following status on an IP that you add, or set this status on a live-connected IP to move it onto a list:
1. Ignore - users connecting from IPs on the ignore list will be treated as normal users. Users on this list will not get auto-blocked when exceeding 20 sessions.
2. Block - this status prevents any further waiting room requests from being made by this IP. End users with this IP will see a suspension notice when visiting the waiting room, or when trying to access a protected URL. Use this status to get rid of undesirables.
3. Bypass - this status allows sessions connecting from this IP to bypass CrowdHandler.
4. Prioritize - this status gives sessions connecting from this IP top priority in the queue. In most cases this means that users from these IPs will not see waiting rooms even under heavy traffic.