Wikipedia:Blocking IP addresses
From Wikipedia, the free encyclopedia
| ←Information pages | Blocking IP addresses |
| This page outlines issues and problems related to blocking IP addresses. |
IP addresses can be blocked by administrators in the same way as registered users are. IP blocks can be more powerful and effective, but also have additional ramifications.
Contents |
[edit] Problems and solutions
[edit] Autoblocks
An autoblock occurs when the software blocks usernames operating from a given IP address. This can occur indirectly when a registered user is blocked, autoblocking the IP. A single block can lead to hundreds of autoblocked legitimate users, so administrators should always be careful to watch for autoblocks in their name. For more information, see Wikipedia:Autoblock.
The simplest way to prevent autoblock problems is to check "Block anonymous users only" for IP addresses, or uncheck "Automatically block IP addresses used by this user" for registered users. Administrators should watch for autoblocks using the block log or pgk's autoblock toolserver script.
[edit] Shared and dynamic IP addresses
Many users operate from shared IP addresses, often those belonging to proxies used by large networks or Internet service providers. Since it is impossible to distinguish between individual users operating from shared IP addresses, blocking one may affect a very large number of legitimate users (ranging up to millions). Users operating from dynamic IP addresses change IP addresses periodically. This can compound the autoblock problem, particularly when they are also shared, because a block targetted at a malicious user may shift to a legitimate user while the target shifts to an unblocked IP address.
[edit] Open proxies
Open proxies are indefinitely blocked on sight according to the Foundation policy against open proxies. This may affect millions of users in rare cases; however, the IP should not be unblocked until it has been closed.
[edit] Particular cases
[edit] AOL IPs
AOL users change IP addresses very rapidly, often within a single minute. Blocks applied against the AOL proxy server IP addresses (see list) should never exceed fifteen minutes, except with rangeblocks intended to stop a vandalbot; see Dealing with AOL vandals and Wikipedia:Advice to AOL users. Please be sure to check "Block anonymous users only" when blocking in these ranges; administrators will generally clear blocks generating a large number of autoblocks.
| AOL proxies (shift within minutes) | ||
|---|---|---|
| CIDR range | Range | |
| 64.12.0.0/16 | 64.12.*.* | |
| 149.174.0.0/16 | 149.174.*.* | |
| 152.163.0.0/16 | 152.163.*.* | |
| 195.93.0.0/17 | 195.93.0.0–195.93.127.255 | |
| 198.81.0.0/19 | 198.81.0.0–198.81.31.255 | |
| 202.67.64.0/18 | 202.67.64.0–202.67.127.255 | |
| 205.188.0.0/16 | 205.188.*.* | |
| 207.200.64.0/18 | 207.200.64.0–207.200.127.255 | |
[edit] Public relations implications
Blocking certain IP addresses can have important public relations and political ramifications for the Wikimedia Foundation. If you must block any of the IP addresses below, you must notify the Wikimedia Foundation Communications Committee immediately so that they may be managed by the Foundation's press relations team. Avoid long blocks of these addresses and be especially careful in formulating your block messages because your block message will be seen and commented on by the press.
| Government IPs (political/public relations issues) | ||
|---|---|---|
| CIDR range | Range | Owner |
| — | 143.231.249.141 | United States House of Representatives |
| 156.33.0.0/16 | 156.33.*.* | United States Senate |
| 194.60.0.0/20 | 194.60.0.0 - 194.60.63.255 | UK Parliament |
[edit] Miscellaneous information
[edit] Blocking ranges
Administrators can block ranges of IP addresses (commonly called rangeblocking); this can affect over sixty-five thousand IP addresses, potentially affecting millions of users. These should be reserved as an absolute last resorts. For information, see m:Range blocks.
