Wikipedia:Blocking IP addresses

IP addresses can be blocked by administrators in the same way as registered users. IP blocks can be more powerful and effective, but also have additional ramifications.

Policies

Sensitive IP addresses

Sensitive due to public relations implications

If you block an IP address in any of the following ranges, you are required to immediately notify the Wikimedia Foundation Communications Committee. These ranges are allocated to major governmental organizations and blocks of these organizations have political and public relations implications that must 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 may be seen and commented on by the press. Also make sure to check the IP address codes to make sure it matches the one you intend to block.

Note that the IPv6 list is not complete. Therefore, always be sure to look up an IPv6 address in WHOIS to make sure it isn't that of a sensitive organization, and if so add the range to this list.

If the IP address belongs to anything that might be closely related to the above, or a major corporation, for example Microsoft, Apple, or others, it may be a good idea to notify the committee.

Sensitive for other reasons

Blocking an IP address listed in this section can cause undesired effects on Wikipedia, which varies depending on the IP address in question. Please issue soft blocks on any bot coming from this address. If you are unsure as to how to do this correctly, please do not issue the block, but contact another admin.

Category	Description
Category:Cleanfeed servers	These IPs are sometimes used by ISPs for legal reasons. When active, most of the traffic from the United Kingdom will be forced through this small number of IP addresses.

Addresses of organizations with a responsive IRT

Some organizations have an Incident Response Team that has demonstrated willingness and ability to be responsive to reports of abuse at the source (the user). In those cases, it is preferable to contact their response team through the provided contact information rather than blocking all or part of their IP ranges – although it remains appropriate to place short blocks to interrupt ongoing vandalism or disruption.

IP address or range	Description
193.113.57.160/27	British Telecommunications plc (response team)
129.127.0.0/16	University of Adelaide (response team)
(TBD)	University of Cambridge (response team)
71.0.0.0/14, 65.40.0.0/15, 76.0.0.0/13	CenturyLink (abuse AT centurylinkservices DOT net)

Organizations should be encouraged to be involved in managing disruption caused by their users to avoid the inconvenience to their other users. When placing a long block on an IP or IP range, a politely worded email to the organization's IT suggesting that they participate this way would be a good idea, and it is important to be liberal in unblocking ranges of organizations that collaborate.

Guidelines

Block lengths

Blocks should be based on the protection of Wikipedia rather than the punishment of offenders. Most IP addresses should not be blocked more than a few hours, since the malicious user will probably move on by the time the block expires. If there is persistent disruption or vandalism from an IP address, the block should be extended (with the 'anon-only' option selected) as long as is necessary to prevent further disruption.

However, IP addresses should almost never be indefinitely blocked. Many IP addresses are dynamically assigned and change frequently from one person to the next, and even static IP addresses are periodically reassigned or have different users. In cases of long-term vandalism from an IP address, consider blocks over a period of months or years instead. Long-term blocks should never be used for isolated incidents, regardless of the nature of their policy violation. IP addresses used by blatant vandals, sockpuppets and people issuing legal threats should never be blocked for long periods unless there is evidence that the IP address has been used by the same user for a long time.

Open proxies should generally be reported to the WikiProject on open proxies and blocked for the length of time they are likely to remain open on the same IP address, which in most cases is likely to be only a few months. Many open proxies have been blocked indefinitely, but this is no longer considered good practice. A large proportion of indefinitely blocked proxies are no longer open proxies.

If you do indefinitely block an IP address, place {{indefblockedip}} or {{blocked proxy}} (do not substitute) on its user or user talk page for tracking purposes.

Shared IP addresses

Before implementing a long-term block on an IP address with a long history of vandalism, please check if it is shared by performing a WHOIS and Reverse DNS lookup query on the IP address to determine if it belongs to a school or an ISP. If a Shared IP address' talk page is not already identified or tagged as such, use either the {{SharedIP}}, {{Shared IP edu}}, or any one of the templates at Category:Shared IP header templates to do so. For anonymous-only blocks of shared IP addresses, please consider using {{anonblock}} or {{schoolblock}} as your blocking reason as it causes less offence to innocent users.

Note that IPv6 addresses are almost never shared, even for large organizations, because network address translation is typically not used with IPv6.

Range blocks

Administrators can block ranges of IP addresses (commonly called rangeblocking). Use careful judgement and make them as brief as possible; they can affect up to 65,536 IPv4 addresses or 649,037,107,316,853,453,566,312,041,152,512 (~6.49×10³²) IPv6 addresses each, potentially affecting millions of users. These should be reserved as an absolute last resort, especially very large rangeblocks.

For more information, see mw:Help:Range blocks (mw:Help:Range blocks/IPv6 for IPv6). You need some knowledge of how networks and IP address numbering work, and of binary arithmetic. If you don't, many other administrators do— ask on the Administrators' noticeboard or on IRC.

If you propose to block a significant range, or for a significant time, consider asking a user with checkuser access to check for collateral damage – that is, for the presence of other users who may be unintentionally affected by the range block. Alternately, if you are unsure whether or not disruptive edits from a specific range can be matched to a single user, you can post a request at sock puppet investigations where an administrator or a checkuser will attempt to match users with IP addresses.

A list of all rangeblocks can be found at Wikipedia:Database reports/Range blocks, which is updated once per week.

You can calculate a rangeblock using toollabs:ip-range-calc.

Problems and solutions

Shared and dynamic IP addresses

Many users operate from shared IP addresses, often those belonging to proxies used by large networks or home users with their 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 targeted at a malicious user may shift to a legitimate user while the target shifts to an unblocked IP address.

Note that IPv6 addresses are almost never shared, even for large organizations, because network address translation is typically not used with IPv6. Although IPv6 addresses can be highly dynamic, possibly changing even more often than IPv4 addresses, a single user will generally use the same /64 range, and his or her IPv6 address is unlikely to be shared with other devices (although multiple people can use a single device, e.g. a shared computer). See Wikipedia:WikiProject on XFFs

Open proxies

Main page: Wikipedia:Open proxies

Open proxies may be blocked on sight according to the policy on open proxies. The IP should be unblocked once the proxy has been closed. Because the IPs may eventually be reassigned or the proxies closed, blocks should not be indefinite, but in some particular cases can be very long term. Block lengths should typically range from several weeks for dynamic IPs and short term Tor nodes, up to several years for long term proxies hosted on static IP addresses.

Administrators who block open proxies should attempt to record in the block log or on the user talk page how to verify whether the IP address is still an open proxy at a future date. Administrators who deal with unblock requests from blocked open proxies should typically seek advice from either the blocking admin or the WikiProject on open proxies before unblocking.

Indefinite blocks

Some behaviour by users, for example egregious threats and harassment, is so extreme that an indefinite block of the user is warranted. There are also some Wikipedia policies, for example Wikipedia:No legal threats and Wikipedia:Sock puppetry where an indefinite block of the user is suggested. These indefinite periods apply to users and not their IP addresses. While the user may be considered indefinitely blocked and subsequently blocked on sight, the IP addresses they use should only be blocked for as long as they are likely to remain assigned to the same user.

Notes

• WMF reply that management of the list of sensitive IP's for the English Wikipedia is the responsibility of the community, under WMF guidance

See also

• Wikipedia:Autoblock
• Wikipedia:Blocking Policy
• Guide to checking open proxies
• MediaWiki:Blockiptext, which provides the introductory text at Special:Block.
• Mediawiki:Help:Range blocks