Redirect to:
This page is a redirect. The following categories are used to track and monitor this redirect:
|
WP:RANGEWP:RANGE Administrators can block ranges of IP addresses (commonly called rangeblocking). Use careful judgement and make them as brief as possible; they can...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Flagged as VPNGATE_VPN, via previous reports...
Click to read more »geo · rangeblocks · spur · shodan Reason: IP self-request unblock, claims no longer a proxy. See IP talk page. This must be part of a rangeblock, because...
Click to read more »listed are obvious, based on their contributions. I'm hoping to see if a rangeblock on 71.100.0.0/16 would be effective, and if there are any other sleeper...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan This address is not an open proxy. Reason: Requested...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: unblocked web proxy xx7.nl quacking...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Flagged as VPNGATE_VPN, via previous reports...
Click to read more »comment/discuss in this section below. See Defending yourself against claims. Rangeblock applied. Mike V • Talk 17:34, 29 June 2015 (UTC) Suspected sockpuppets...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Sameboat has made an unblock request. עוד מישהו...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: It's from Hong Kong according to this, and it...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 12.202.180.7 · talk · contribs · block · block log ·...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan The first IP may be User:Marknutley, who is blocked for...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: unblocked web proxy 1 Cheers! Feedintm (talk)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits As to the identity of the IP...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: An IP form the wayback machine. -322UbnBr2 (Talk...
Click to read more »see below) Code letter: C Supporting evidence: I am about to have set a rangeblock on 67.236.245.9/19 due to ongoing vandalism at Major League Baseball 2K9...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: unblocked web proxy [1] that came up while investigating...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: This IP blanked a page on the Czech Wikipedia...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan · WorldVPN · fr2.ocservvpn.com 152.228.215.225 · talk ·...
Click to read more »16.121.71 blocked 1 week. With only 2 IPs, a rangeblock is a litte hard to determine. So no rangeblock for now. Elockid (Talk) 17:01, 20 June 2010 (UTC)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Ip address is currently blocked for vandalism...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 88.110.0.39 · talk · contribs · block · block log · active...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan User talk:74.208.134.1 seems to be saying they are not...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: User:GameOn has told me on my talk page that...
Click to read more »Privacy policy, X!'s edit counter, old rangeblocks, and the Article Incubator: A list of current discussions on the English Wikipedia. ← Back to Contents...
Click to read more »read_default_file='~/.my.cnf') cursor = conn.cursor() cursor.execute(''' /* rangeblocks.py SLOW_OK */ SELECT ipb_address, ipb_by_text, ipb_timestamp, ipb_expiry...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan il.seed4.me 103.227.252.147 · talk · contribs · block ·...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Didn't give a reason for unblock; I presume this is what...
Click to read more »You can use templates with custom options to specify situations like {{rangeblock|create=yes}} or {{uw-ublock|contains profanity}}. Discuss this newsletter...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits from open corporate proxy. GabeMc...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 38.131.148.84 · talk · contribs · block · block log ·...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan open port 8080 2016-05-27 Reason: suspicious edits Confirmed...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits Sudden spate of vandalism -...
Click to read more »dynamic IPs, though a rangeblock could be considered. There is probably not enough volume of vandalism to justify a rangeblock. EdJohnston (talk) 00:52...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan User:Calvin 1998 uses this and says the IT people at...
Click to read more »blocked, but persists. I suspect that there are other accounts and that a rangeblock may be necessary, hence the request for CU. Alexandr Dmitri (talk) 11:51...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Appears to be an open proxy based on whois results. Vandalism...
Click to read more »sockpuppets See below - request for collateral damage check prior to rangeblock. Evidence submitted by Toon Wikipedia:Sockpuppet investigations/Albbbbeeeennnnoooo...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Says they're not an open proxy. Daniel Case (talk) 14:34...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits at AN/I, and Geolocate marks...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan IP was blocked back in 2006 with an expiry time of indefinite...
Click to read more »Requested by — Dædαlus Contribs 00:13, 29 May 2009 (UTC) CU is required for rangeblock potential. As said above, the first puppet listed was blocked indefinitely...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Restoring vandalism by IPs to Bob Jones University...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: This is an anonymizing proxy [1] EnPassant♟♙...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Blocked 4+ years ago, time to review following email...
Click to read more »alter the rangeblock) seems warranted. Endorsing. Steven Zhang Help resolve disputes! 03:19, 24 April 2013 (UTC) Bratyouth is Stale. Rangeblocks are going...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits. On The Fugitive: Plan B the...
Click to read more »December 2019 (UTC) @MJL: Visit the IP's userpage. You'll see it's under a rangeblock for Wikipedia:Disruptive editing. Cabayi (talk) 07:44, 9 December 2019...
Click to read more »for rangeblocking. Sock edits follow the master's edits. — Berean Hunter (talk) 16:04, 12 September 2012 (UTC) I have just imposed a small rangeblock; I...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Is a web proxy. I would assume it is to be blocked...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan and 166.137.156.32 · talk · contribs · block · block...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Block evasion on pl.wikinews. Suspicious Google results...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 221.130.23.88 · talk · contribs · block · block log ·...
Click to read more »--Drm310 (talk) 18:12, 17 September 2013 (UTC) Clerk endorsed - for a rangeblock/sleeper check. Rschen7754 20:00, 17 September 2013 (UTC) Clerk note: Already...
Click to read more »can now be shown in the block message (e.g. if a user is caught in a rangeblock, it's possible to distinguish this from their IP being blocked). (r22641...
Click to read more »clearly sockpuppets of Orijentolog and issued a Rangeblock. See brief discussion at Wikipedia:An#Rangeblock_check. Given the behavior, I'd support a CU to...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: IP traces back to a hosting company called worldstream...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan I made a null edit to the sandbox using http://www.deafdoor...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Requested unblock via UTRS #11262.--Jezebel'sPonyobons...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan open port 3128, blocked once before 2016-05-06 Reason:...
Click to read more »I'm not sure if I'm going about this the right way, but I believe a rangeblock is in order to stop this ongoing problem, and a combination of analysis...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: (This user violates wikipedia rules by using...
Click to read more »here, a sleeper check appears to be warranted, as well as potential for rangeblock. I've already DUCK blocked Ftsw. --Shirik (Questions or Comments?) 16:33...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 95.141.31.8 · talk · contribs · block · block log · active...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Requested unblock. Block ID #4575939. See User...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Open proxy. I know which site, but am unable...
Click to read more »but then the user shows up again on a new IP. I'd like to request a rangeblock to stop this user, if at all possible. NeoChaosX (talk, edits) 18:04,...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits {{opblocked}} Related to Hotspot...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Requested unblock via UTRS (#2349).--Jezebel'sPonyobons...
Click to read more »range block. Continues adding in unsourced content. Enforce a harder rangeblock. MarioProtIV (talk/contribs) 01:52, 4 March 2018 (UTC) Accused parties...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 145.15.244.25 · talk · contribs · block · block log ·...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Possible open proxy thats vandalising this talk...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 68.193.97.107 · talk · contribs · block · block log ·...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Requested unblock for AfroThundr3007730 (talk ·...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Registered to InternetNamesForBusiness.com, which...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits {{tl}} -- zzuuzz (talk) 11:52...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: {{unblock}} request by Philip200291. עוד מישהו...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Requesting unblock at User talk:M0z Ronhjones (Talk)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Known VPN. I've tested it, and this is one of...
Click to read more »2015 (UTC) A three-month rangeblock was applied by NeilN to 2602:306:BD7E:CAA0::/64 on 22 August 2015. A six-month rangeblock was applied by Bishonen to...
Click to read more »blocked on behavioural evidence alone. I've looked into a rangeblock, but unfortunately rangeblocking wouldn't work here. Chase me ladies, I'm the Cavalry...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan open port 8291 2016-05-03 Reason: Suspicious edits Comment:...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Corporate proxy server. Suspicious POV edits from this...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Nmap exposes Port 80 as open. -Jeremy (v^_^v Cardmaker)...
Click to read more »it makes rangeblocks ineffective. Some editors may only consider "true" IP hopping to be range hopping that would (or does) render rangeblocks entirely...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Edits made to denigrate person. Edits are offensive,...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: A pattern of attacks on User talk:Diannaa, all...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Mobile network, probably CGNAT. - RichT|C|E-Mail...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Unblock request by anon. עוד מישהו Od Mishehu...
Click to read more »Defending yourself against claims. I have imposed two fortnight-long rangeblocks. Salvio Let's talk about it! 11:06, 4 May 2012 (UTC) Suspected sockpuppets...
Click to read more »149.171.184.60 (talk · contribs · IP contribs · WHOIS), outside of the rangeblock. --TeaDrinker (talk) 00:47, 19 April 2012 (UTC) No contact history entered...
Click to read more »section below. See Defending yourself against claims. I'd recommend a rangeblock on the /64 (2602:30A:2E3E:DFF0::/64). All of that range is owned and controlled...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Requested unblock via UTRS.--Jezebel'sPonyobons...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: I’m not sure which LTA has used this IP but as...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Open proxy. [1] --Gordonrox24 | Talk 19:13, 3...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits by IP sock of indefinitely blocked...
Click to read more »— Dædαlus Contribs 04:17, 3 May 2009 (UTC) Checkuser is required for rangeblock potential, this user is obviously able to evade blocks.— Dædαlus Contribs...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 212.174.190.24 · talk · contribs · block · block log ·...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits to U.S. road articles from an...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: I know it to be an open proxy and I am being...
Click to read more »tilde characters "~~~~" WP:DUCK case, all disrupting Fufu. I placed two rangeblocks earlier today, but he seems to have avoided them. I'm requesting checkuser...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan {{notaproxy}} -- zzuuzz (talk) 17:40, 27 January 2010...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: IP recently used for vandalism, was blocked by...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Open proxy. - Dwayne was here! ♫ 20:05, 12 September...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Unblock request asks for us to check again. Clerk note:...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits. IP currently on talk-page disabled...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Blocked for vandalism, made this edit in which the user...
Click to read more »IP, is a sockpuppet of "Akshata Sen" and "Akshata Dev". Have to have rangeblock over here Avenue X at Cicero (talk) 10:19, 2 August 2011 (UTC) Accused...
Click to read more »obvious sockpuppets, but is a rangeblock possible? Reaper Eternal (talk) 18:38, 13 November 2012 (UTC) Completed Rangeblock is not possible. CU can barely...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits. In particular this edit, which...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Came up during a recent checkuser scan; port...
Click to read more »Auto-generated every hour. Editor interaction utility Any chance of a rangeblock? NeilN talk to me 20:45, 10 April 2017 (UTC) Accused parties may also...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits Not currently an open proxy...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: See here. I'm not requesting an unblock, the...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits; may have been used by User:45g...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Says we're just biased against any Linux server with...
Click to read more »little that can be done because a block will just make them move on, and a rangeblock could not be accurately targeted in this case. Kevin (talk) 08:22, 27...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 71.62.15.32 · talk · contribs · block · block log · active...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan the user's repeated violation on Lee Myung-bak reminds...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Project Honey Pot reports this as coming from a mail...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Edit on [1], unlikely a user in Indonesia would have...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Requesting unblock, claim it's a dynamic ip but not an...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits - MrX 🖋 23:00, 14 April 2019...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits. IP sock of User:ViperNerd,...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Vandalism to an article vandalized earlier by...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits, 3rd IP from Poland to edit...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Flagged by proxycheck.io and spur as an open...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Per this edit. I suspect the massive vandalism...
Click to read more »Wikipedia [3], which is a ROLE violation. RFCU to establish feasibility of a rangeblock with consideration of extent of collateral damage from so doing. MSJapan...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan The IP is listed on an open proxy list site, no edits...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan POINTy. QUESTION: Does ClueBot IV actually perform/cause...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Says it's not an open proxy; block was a while back....
Click to read more »Ericisafacinass just got blocked. This IP was blocked as part of the ensuing rangeblock. Ericisafacinass had edited the IPs talk page before. Each had been vandalizing...
Click to read more »vandalism-only accounts. NW (Talk) 18:46, 24 October 2009 (UTC) Unfortunately, a rangeblock does not seem to be possible, per discussion with Alison. NW (Talk)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Obvious troll editing from a confirmed proxy server....
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Wikipedia:Sockpuppet investigations/Andranikpasha...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: I am reporting myself before I go crazy. http://freethewww...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Requested unblock by N-soda. עוד מישהו Od Mishehu...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan See Project Honeypot's reportUser:LeadSongDog come howl...
Click to read more »the IP given, or all IPs in the given range, to be returned, including rangeblocks which contain the IP or range given. (r36452, bug 14405) It is now possible...
Click to read more »pattern of edits from previous revolving IP address. Evading existing rangeblock. HankScorpio1519 (talk) 08:47, 1 May 2022 (UTC) Accused parties may also...
Click to read more »same person, they are somewhat dynamic so I only issued short blocks. A rangeblock would be too disruptive. Tiptoety talk 04:48, 8 December 2009 (UTC)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: I was trying to verify an open web proxy claim...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Ltiler requesting unblock of this IP. Daniel Case (talk)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Unblock request I declined says this is a Tor node and...
Click to read more »log · CA · CheckUser(log) · investigate · cuwiki · SI) (see contribs). Rangeblock if possible. T. Canens (talk) 11:13, 22 July 2012 (UTC) Verr interresting...
Click to read more »getting a rangeblock? Sockmaster now taunting. Here also. ⋙–Berean–Hunter—► ((⊕)) 18:24, 24 January 2011 (UTC) I'd say maybe hold off on a rangeblock until...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan - see User talk:Dr Gwapo. Block is from July '08 so worth...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Per unblock request by anon. עוד מישהו Od Mishehu 13:06...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits. Geolocate says it is a proxy...
Click to read more »outside that range is the 66 one, which could be covered by another /24 rangeblock if needs be. See Classless Inter-Domain Routing - Alison ❤ 23:53, 26 February...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan User:DavidYork71 used IP address. Seems much of the 217...
Click to read more »The blacklist has already solved the problem. No additional accounts visible, and nothing suitable to rangeblock. ST47 (talk) 15:51, 11 April 2020 (UTC)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Possible Open Proxy R12056 (talk) 05:57, 21 March 2010...
Click to read more »here and more sovereignty disputes here and here. Request renewal of rangeblock detailed above and a checker for rooting out any sleeper accounts which...
Click to read more »229.232 (talk) 17:56, 15 November 2012 (UTC) Clerk note: I've applied a rangeblock to hopefully stop the sock edits and indefinitely blocked the account...
Click to read more »should the templatedata block be placed? Mass removal of old indefinite rangeblocks (This section will include active RfAs, RfBs, CU/OS appointment requests...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Requested unblock via unblock-en-l. I didn't...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Block was made three years ago. Can we see if things...
Click to read more »on the feasibility of a rangeblock. Nathan T 15:30, 28 October 2009 (UTC) Sorry, but we've already determined that a rangeblock here is technically impossible...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits and seems like open proxy given...
Click to read more »account of this person, so I am opening this investigation to see if any rangeblocks are warranted. TornadoLGS (talk) 06:24, 22 September 2021 (UTC) Accused...
Click to read more »fact that the known previous IP alt of the master is within the same IP rangeblock (103.6.156.1 - 103.6.159.255) as the current incarnation. Hasteur (talk)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Please check 216.56.7.98 - all of the edits are vandalism...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Banned user User:Tennis_expert is using a new ip which...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: This IP seems to do nothing but vandalism, and...
Click to read more »comment/discuss in this section below. See Defending yourself against claims. Rangeblock applied: that's all we can do. Drmies (talk) 02:11, 14 February 2020 (UTC)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: ISP is Locaweb Serviços de Internet S/A which...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 46.109.33.214 · talk · contribs · block · block log ·...
Click to read more »a tobacco product."). Pretty clear socking and probably in need of a rangeblock if possible. Jasper Deng (talk) 06:31, 12 October 2023 (UTC) Accused parties...
Click to read more »specify exactly which scripts require updating. Edit counting scripts Rangeblock-calculating scripts User comparison scripts Helpmebot Other IRC bots Huggle...
Click to read more »[2]. Request block for block evasion. Request Checkuser for check, and rangeblock, of related IPs, in similar range. Sagecandor (talk) 01:06, 17 June 2017...
Click to read more »block · block log · CA · CheckUser(log) · investigate · cuwiki · SI) Rangeblock_abuse_victim (talk+ · tag · contribs · deleted contribs · logs · filter...
Click to read more »address behavior. It looks like protections are already done. I can do a rangeblock later if disruptive behavior spreads. Elockid(Boo!) 17:29, 6 October 2013...
Click to read more »Defending yourself against claims. Clerk note: All IPs already blocked. No rangeblock possible. For quicker response, consider reporting any future IPs and/or...
Click to read more »so a CU check doesn't seem necessary. If they continue on this path a rangeblock might be explored at a later point. ☺ · Salvidrim! · ✉ 16:16, 16 June...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 213.151.218.137 · talk · contribs · block · block log ·...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan - Proxy 8080 Online proxy list - Cheers! Feedintm (talk)...
Click to read more »consensus-deleted info. Same ISP. Comments This is way too sporadic for a rangeblock, isn't it? If it's not...please consider it. (I apologize for the belated...
Click to read more »reason, my original isn't showing in the edit history. In any event, a rangeblock is long overdue. I suggested a course of action regarding a possible filter...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Polish LTA reported at WP:AIV. Currently blocked...
Click to read more »case will be soon declined if there is no any serious disruption for rangeblock. SA 13 Bro (talk) 13:59, 10 July 2017 (UTC) When given an account and...
Click to read more »scripts Vietnamese naming conventions Mass removal of old indefinite rangeblocks (This section will include active RfAs, RfBs, CU/OS appointment requests...
Click to read more »this section below. See Defending yourself against claims. Clerk note: A rangeblock is simply impossible. I will semiprotect his talk page, though. Reaper...
Click to read more »these are mobile IP addresses, there's not much we can do here because a rangeblock would cause collateral damage. I doubt that they'll come back to it, but...
Click to read more »2602:306:CE9A:860::/64, they are almost certainly the same and I'd recommend a rangeblock (almost zero collateral damage because one /64 is typically one AT&T connection...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan This edit suggests a previously-blocked disruptive user...
Click to read more »investigate · cuwiki · SI) The semi-protection is also a jolly good call, as a rangeblock doesn't look realistic. WilliamH (talk) 13:41, 1 February 2012 (UTC) Administrator...
Click to read more »Anyway, just inquiring as to the possibility of sleepers and/or a partial rangeblock if necessary. Comments by accused parties See Defending yourself against...
Click to read more »2009 (UTC) Clerk, patrolling admin and checkuser comments Looks like a rangeblock is not really feasible; the autoblock should take care of whatever IP...
Click to read more »rangeblocks. If IPBE is going to be restricted then rangeblocks also need to be restricted for the simple fact there are hundreds of bad rangeblocks....
Click to read more »persists, a checkuser request may become necessary to determine if a rangeblock might be possible, but it's too early for that at present. PeterSymonds (talk)...
Click to read more »no edits). Too old now to block. If it continues/starts again, a short rangeblock or semi-protection might be in order. Mr.Z-man 01:13, 20 February 2008...
Click to read more »a Checkuser request in case there are other sleeper socks, and put a rangeblock in. Daniel Case (talk) 15:26, 6 November 2008 (UTC) Good idea...and done[1]--...
Click to read more »protect his last target. At this point, I am trying to perhaps look at a rangeblock to stop this at the source. However, these are both rather large ranges...
Click to read more »or_intervention_against_vandalism#Rajput_troll in order to mete out a rangeblock. dab (ᛏ) 13:01, 11 July 2006 (UTC) Clerk note: Please give a list of (at...
Click to read more »the interest of determining an underlying schoolblock or constructing a rangeblock that wouldn't be awful, but since they wouldn't post about it here I'm...
Click to read more »Wikinews from the "In the News" section? Mass removal of old indefinite rangeblocks Bot flags (This section will include active RfAs, RfBs, CU/OS appointment...
Click to read more »creation may be blocked, but cycling through IPs is trivial. Only a CU can rangeblock since I don't know the IPs involved. If it continues, open a new case...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 2405:204:9493:913F:DCE3:AB6A:D101:B93C · talk · contribs ·...
Click to read more »bit in the meantime. I want to confirm that a /25 would be effective rangeblock and that's kind of hard with just two IPs. Elockid (Talk) 11:18, 4 May...
Click to read more »rangeblock in place. However, the first sock IP listed is not blocked yet (and a rangeblock would be useful for that sock IP as well). The rangeblock...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Requested unblock by Shreesmani. עוד מישהו Od Mishehu...
Click to read more »nothing about rangeblocks. I have raised the sockmasters block to indef. Spartaz Humbug! 15:32, 31 March 2014 (UTC) Closing. No rangeblock necessary at...
Click to read more »However, I would like to request a sleeper check, as well as finding if a rangeblock is possible. — Dædαlus Contribs 03:24, 4 September 2010 (UTC) See Defending...
Click to read more »Same pages being edited as previous sock. Requesting CU to see if a rangeblock is possible. Elockid (Talk) 12:44, 3 September 2011 (UTC) Accused parties...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Request made by Atin Bhattacharya. עוד מישהו...
Click to read more »supposed to place any tags or messages? I don't know how to do that with a rangeblock. Bishonen | talk 18:37, 23 October 2017 (UTC). @Bishonen: You can tag...
Click to read more »damage. Bishonen's rangeblock is relatively safe, but it is way too narrow to be effective. In other words, I don't think that rangeblocks are going to be...
Click to read more »GABgab 02:28, 6 September 2017 (UTC) GAB, if someone were looking for a rangeblock between, say, 2606:6000:FD0A:FB00:6849:6E35:BEF3:20E and...
Click to read more »Timeline · SPI Tools Reinstating troll edits by blocked IP. Can we get a rangeblock? I don't like to request page protection for a Talk page in case any grown...
Click to read more »checkuser comments Administrator note You're probably right, but the rangeblock to catch those two IPs would encompass 536870912 possible users. :) I...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits consistent with banned user...
Click to read more »harassment SPAs from some previously blocked user. CU is to find if a rangeblock is possible, and if any sleepers exist. — Dædαlus Contribs 20:59, 1 April...
Click to read more »they had been blocked by a rangeblock put in at my request. (This is a response to the initial close.) Update: rangeblock (expired) It says anyone can...
Click to read more »User:Correcttherecord13. I'll block, you tag. I threw in a week-long rangeblock for free. Drmies (talk) 03:08, 22 August 2018 (UTC) Tagged. Ian.thomson...
Click to read more »User:WJH1992 and is constantly being caught in this rangeblock. I recommend extending this rangeblock as it's just due to expire. This guy has been at this...
Click to read more »that I produce as subpages of my userpage. See for example User:ST47/rangeblocks expiring soon. In order to produce those reports in a timely manner,...
Click to read more »type of vandalism to the Lena Raine page. Requesting CU to check for a rangeblock as well as to triple check and make sure I got all the accounts. Ks0stm...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 65.151.155.243 · talk · contribs · block · block log ·...
Click to read more »03:13, 29 April 2009 (UTC) Checkuser is required to see if there is any rangeblock potential. This user is obviously able to evade blocks, so let's stop...
Click to read more »log · active blocks · stalk · Robtex · whois · Google · ipcheck · geo · rangeblocks · spur · shodan Reason: Another IP possibly using open proxies, continuing...
Click to read more »against claims. Clerk note: there's too much IP hopping here to calculate a rangeblock effectively, although the IPs do seem to be related. Town has now been...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Positive ipcheck. See previous listings. Tule-hog...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan 49.146.2.201 · talk · contribs · block · block log ·...
Click to read more »nuke contribs · logs · filter log · block user · block log) I've also placed a rangeblock. Nishkid64 (Make articles, not wikidrama) 22:46, 30 December 2008 (UTC)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspected Tor {{notaproxy}} Q T C 07:03, 20 March...
Click to read more »check for sleepers. Rschen7754 05:34, 26 January 2013 (UTC) Doesn't appear to be any, rangeblock not possible. -- DQ (ʞlɐʇ) 10:55, 26 January 2013 (UTC)...
Click to read more »Confirmed as Sanfy (talk · contribs). I'll look into the possibility of a rangeblock, but it seems we might have a lot of collateral damage. Nishkid64 (Make...
Click to read more »three IPs are blockable. The rest are Stale for blocking purposes. No rangeblock possible here as it hits a /16 or 65536 users. -- DQ (t) (e) 02:18, 14...
Click to read more »on my user talk, is a block evasion account. If so, I am requesting a rangeblock that would hopefully stop this silly behavior. Thanks in advance. --Dr...
Click to read more »editor involved. 81M (talk) 13:05, 30 June 2012 (UTC) Administrator note Rangeblock is useless here. If they come back, report to WP:RFPP for semi-protection...
Click to read more »99.91 was too. I've flagged both accounts appropriately. Regarding a rangeblock, it looks to me as if an effective one would cause too much collateral...
Click to read more »investigated. April 6, 2017: A rangeblock was placed on Special:Contributions/172.56.28.0/23 for one year. April 6, 2017: A rangeblock was placed on Special:Contributions/208...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Vandalism R12056 (talk) 03:49, 7 June 2010 (UTC) {{notaproxy}}...
Click to read more »IP, new IP. Please block their current IPs as well - preferably with a rangeblock. The range starting with 2600:1003 would be a good start, if that wouldn't...
Click to read more »but the range is wide enough and active enough that I don't think a rangeblock would be appropriate. Kevin (aka L235 · t · c) 03:07, 22 December 2019...
Click to read more »in this section below. See Defending yourself against claims. 2601:584:4200:E540:0:0:0:0/64 rangeblock. --NeilN talk to me 04:54, 5 October 2015 (UTC)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan See request on talk page, saying that this is a Dynamic...
Click to read more »should have to put up with this juvenile garbage. I'd like to request a rangeblock if one is feasible. See Defending yourself against claims. Clerk endorsed...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Appears to have been used recently by banned user; previously...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan User requested unblock of blocked proxy. --Jayron32 04:31...
Click to read more »hopping means blocking individual addresses won't accomplish much, and a rangeblock is not feasible here without collateral damage. Sir Sputnik (talk) 22:37...
Click to read more »Unfortunately the range here is quite large and is very active. I don't think a rangeblock is going to be possible. We'll have to wait and see how this goes. --Shirik...
Click to read more »to tell, as I said I have never done this before, I am not sure if a rangeblock or if no blocks are required here.– Phoenix B 1of3 (talk) 04:06, 19 September...
Click to read more »2015 (UTC) Administrator note Blocked 1 year. I don't see a need for a rangeblock at this time, but it appears feasible should it become necessary. Shirik...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Block evasion on pl.wikinews. CheckUser block before...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan I have a hunch that a user who was recently blocked for...
Click to read more »shown to have the ability to evade blocks. This check is to see if a rangeblock is feasible, to prevent further damage. The sock above is already blocked...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits. IP sock of User:ViperNerd,...
Click to read more »the end of the school year (or at the end already), I do not think a rangeblock is needed at this time. But vigilance is still needed. Willking1979 (talk)...
Click to read more »dynamic IPs or something. Their edits aren't nearly enough to warrant a rangeblock, so I'm leaving it alone for now. Take it to AIV as necessary. — HelloAnnyong...
Click to read more »are currently blocked. This SPI was created if it is possible to put a rangeblock on this user's IP address. User was last seen using an anon IP address...
Click to read more »are any other obviously different users in that range before enacting a rangeblock. As the user has only created one account, and has only edited via IP...
Click to read more »Several accounts have been blocked/tagged for cross-wiki abuse and a large rangeblock has been placed. Please refile if more unblock accounts appear. TNXMan...
Click to read more »investigate · cuwiki · SI), but didn't see anything resembling a useful rangeblock. The ISP these are coming from is huge, sorry to say. Courcelles 16:14...
Click to read more »edited in a while and I don't see anything on the /21 that would justify a rangeblock at this time. Closing. Blablubbs|talk 11:29, 19 April 2021 (UTC)...
Click to read more »these three all turn out to have the same IP or the same range, can you rangeblock them? MelanieN (talk) 18:49, 9 November 2019 (UTC) Accused parties may...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Possible VPN. 73.67.145.30 (talk) 03:21, 8 May...
Click to read more »user I don't know if I can mention but that is blocked for a year. A rangeblock can be helpful here instead of having pages protected like this one since...
Click to read more »report Auto-generated every hour. Editor interaction utility Asking if IP rangeblock is possible + sleepers NeilN talk to me 11:55, 2 January 2018 (UTC) Accused...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Banned user User:Tennis_expert is using a new ip which...
Click to read more »any additional domains involved (so that they can be blacklisted). Is a rangeblock possible? MER-C 04:47, 17 May 2012 (UTC) Accused parties may also comment/discuss...
Click to read more »There's a lot of logged edits as well. I looked at a possibility of a rangeblock, doesn't look like there's a possibility of it. Elockid (Talk) 16:22,...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: IP requests unblock. Block reason contains the...
Click to read more »same new IP address from the same provider and location that escaped the rangeblock, same mass edit-warring on football/soccer articles. CoffeeCrumbs (talk)...
Click to read more »we could be turning away potentially valuable contributors with these rangeblocks, as evidenced by the numerous unblock-auto requests that come through...
Click to read more »the rest of it. Oaktree b (talk) 15:06, 10 July 2022 (UTC) Delete and rangeblock the sockpuppet IP too. They are canvassing people to "help to remove discussion"...
Click to read more »11:57, 28 October 2011 (UTC) Clerk note: Is the collateral check for a rangeblock? I don't really think that's necessary at this point: we don't know who...
Click to read more »by a WP:SPA and promoted bya legion of block-evading IPs, leading to a rangeblock. No reliable independent sources to show this meets WP:BAND, never charted...
Click to read more »- Self-endorsed by clerk for checkuser attention - Is it possible to rangeblock this since the user won't stop returning? Reaper Eternal (talk) 23:04...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan EraserGirl has requested unblock. I see no abuse from...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Per unblock request here. User's comment: This...
Click to read more »21:48, 4 March 2010 (UTC) Confirmed - no other socks. Bit early for a rangeblock right now - Alison ❤ 03:51, 5 March 2010 (UTC) Blocked and tagged. NW...
Click to read more »account uses new ones, the only way of dealing with this would be to /16 rangeblock a popular Indian ISP for quite some time and there would be a lot of collateral...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: At least one agent string lists itself as "http://proxy...
Click to read more »Dædαlus Contribs 21:02, 23 October 2009 (UTC) CU is required to see if a rangeblock for these SPAs is possible, as the user I'm currently using as the sockmaster...
Click to read more »articles about low-level BJP functionaries — can we please just permanently rangeblock the entire party now? Bearcat (talk) 02:10, 18 January 2020 (UTC) Delete...
Click to read more »named users are socks --Versageek 04:01, 25 May 2009 (UTC) Is there any rangeblock potential?— Dædαlus Contribs 04:38, 25 May 2009 (UTC) Not really, his...
Click to read more »them is like playing whack-a-mole. The ranges are too large to preform a rangeblock, so I am closing the case. — Jake Wartenberg 23:50, 20 June 2009 (UTC)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Came up in a recent checkuser scan; appears to...
Click to read more »ran the check before the IP showed up, and the ranges are too large to rangeblock. J.delanoygabsadds 02:22, 31 August 2009 (UTC) Conclusions Accounts blocked...
Click to read more »Wikipedia:Requests for checkuser/Case/Societyfinalclubs#Societyfinalclubs. That rangeblock was in May 2008. Starting in November (non-coincidentally 6 months later)...
Click to read more »block. However, recording here for reference; the two IPs are close so a rangeblock may be possible if the problem persists. Qwyrxian (talk) 03:57, 6 August...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Seems like an open proxy. This IP has similar...
Click to read more »Bambifan101, either. Worth a check to see if there's a hole in some of the rangeblocks.—Kww(talk) 21:03, 14 February 2010 (UTC) See Defending yourself against...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: This British IP is being used to add unhelpful...
Click to read more »necessary here. It's very obvious and I don't think we're to the point of requiring a rangeblock yet. Closing. Thanks, Spicy (talk) 17:30, 27 April 2022 (UTC)...
Click to read more »contribs · WHOIS) 91.109.107.31 (talk · contribs · IP contribs · WHOIS) A rangeblock has been deemed unfeasable by the Checkuser Luna Santin, due to collateral...
Click to read more »has just switched IPs in order to evade a block. Could someone please rangeblock him/her and warn him/her to stop socking? Stonemason89 (talk) 02:12, 13...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan IP blocked indef (?!) in 2008. Unblock-auto request by...
Click to read more »against claims. The three IPs are across a /15 which is too big for a rangeblock. The most recent address has been blocked for disruptive editing. It could...
Click to read more »hardblock on their IP does nothing. This is to check to see if a potential rangeblock is possible, and if there are any sleepers.— Dædαlus Contribs 00:15, 14...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan - Dwayne was here! ♫ 20:17, 12 September 2010 (UTC) Reason:...
Click to read more »two suspected socks, and asked for any ideas; for instance, whether a rangeblock was likely to work. EdJohnston (talk) 01:38, 1 May 2008 (UTC) See also:...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan This is the IP of a web proxy at http://www.proxy-hide...
Click to read more »blocked 1.47.0.0/16 with an expiration time of 3 months (anon. only) ({{rangeblock}}: gun hoaxster falsifies refs) 49.237.128.0/17 49.237.152.0/21 (subset...
Click to read more »PeterSymonds (talk • contribs) Minor note - rangeblocks are rarely out of the question. There are many types of rangeblock, and also IPBE now functions for the...
Click to read more »to mention that blocking them amounts to playing Whack-A-Mole, with no possible rangeblock covering all of them. –MuZemike 20:15, 2 January 2010 (UTC)...
Click to read more »about declaring a COI. The IP has been caught as collateral in a /32 rangeblock. Therefore, a CU is endorsed for Minky6879! to look for any other accounts...
Click to read more »other users Not socks, probably a bored kid at an office or something. Rangeblock would be effective if the IPs continue.Abce2|Aww nuts!Wribbit!(Sign here)...
Click to read more »striking the votes by the sock/meatpuppets. CU is needed for another rangeblock, sleeper check. I mean, they obviously got around the first one, and evaded...
Click to read more »there are any additional sleepers out there and to also properly impose a rangeblock to stop this disruptive and unwelcome user. -MBK004 05:36, 5 August 2009...
Click to read more »Closing. Bbb23 (talk) 00:21, 6 December 2021 (UTC) I added a two week rangeblock for 2003:E9:700::/42 (talk+ · tag · contribs · filter log · WHOIS · RBLs ·...
Click to read more »See Defending yourself against claims. CheckUser requested - Sleepers? Rangeblock? Ks0stm (T•C•G•E) 21:30, 3 May 2017 (UTC) I'd actually already checked...
Click to read more »effect. Could you please request checkuser and ask them to work out a rangeblock or other method of stopping this? Jehochman Talk 18:53, 27 February 2008...
Click to read more »unsourced content and edit warring. Let me know if they come back again, a rangeblock looks possible or the articles can be semi-protected. Thanks! ~ mazca...
Click to read more »to the IPs listed. Andrejj has also made no edits on Ivan's talk page. Rangeblock is not feasible and Ivan's user page is already semi-protected. I'm going...
Click to read more »(UTC) Maybe a checkuser is in place? IF its not a dynamic IP, an indef rangeblock could be used. DustiSPEAK!! 15:31, 25 June 2008 (UTC) I don't know anything...
Click to read more »these IPs frequent. Relist if it becomes more of a problem and we'll do a rangeblock or something. — HelloAnnyong (say whaaat?!) 21:52, 4 February 2011 (UTC)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits 222.89.92.106 has been edit-warring...
Click to read more »Thomas.W talk to me 15:52, 4 August 2013 (UTC) And one more IP. Seems a rangeblock, and a quick one, is the only way to stop him. Thomas.W talk to me 19:21...
Click to read more »(UTC) Re "why" — it's a real-life situation unrelated to a rangeblock; I brought in rangeblocking only because that help page is the only place where I've...
Click to read more »IP blocked - just two of them. Let me know if this restarts and I will rangeblock. It's only two narrow /25 and /20 ranges. Confirmed - Ffddd (talk · contribs)...
Click to read more »he's not as active here, so I'm requesting a check for sleepers, and a rangeblock if it doesn't result in too much collateral damage. —fetch·comms 02:45...
Click to read more »narrow IP range for this hypothetical computer lab whos IPs we could rangeblock. --barneca (talk) 16:20, 10 November 2008 (UTC) Confirmed IP blocked No...
Click to read more »TSUBAME2 and SaveDisassembledBeings accounts come from the same chap. The rangeblock should suffice for now. - Mailer Diablo 18:36, 25 March 2011 (UTC) Everyone's...
Click to read more »sleepers because creations are usually sequential, but maybe an additional rangeblock is possible. In any case, this will likely need a merge. No tags for this...
Click to read more »Any other matches? → ROUX ₪ 02:02, 6 October 2009 (UTC) And/or is a rangeblock possible? I do not want to be subjected to the sort of ongoing harassment...
Click to read more »the bot skips it. This includes if it is already subject to a local rangeblock. The bot does not check global blocks. If the proxy is an IPv6 IP, the...
Click to read more »socks at this time, but if things escalate, it may be possible to soft rangeblock the editor - Alison ❤ 04:49, 26 August 2008 (UTC) The above discussion...
Click to read more »common IP range and what, if any collateral damage there would be to rangeblock it. Thanks, Snappy56 (talk) 03:39, 13 November 2008 (UTC) The following...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Global Protect Cloud VPN hit. kline / talk /...
Click to read more »but I don't think I'm out of line to suggest that it may be time for a rangeblock against this user, who has repetitively disrupted and bypassed administrative...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits. I removed a comment from a...
Click to read more »fill me with joy, I don't think that we've hit the threshold where a rangeblock is necessary. Given the pretty narrow focus of these particular IPs in...
Click to read more »2012 (UTC) Manikg4 is a Confirmed match to the rest of the accounts. A rangeblock is not feasible at this time, as they are hopping IPs and ISPs. TNXMan...
Click to read more »same person. The range is too wide to really do any sort of effective rangeblock, and the IPs I listed seem to have been used temporarily. This person...
Click to read more »Conclusions Administrator note Article semi-protected for 1 month. An anon-only rangeblock is not feasible due to many good faith edits from other IPs within the...
Click to read more »favourite band BTW), and attack me at my user page. I don't know if a rangeblock could be done, or if the main account may be blocked to avoid future disruption...
Click to read more »again, of course. The rangeblocks seem to be helping, though, and I'm starting to collect information for the next rangeblock. Same for NisarKand, also...
Click to read more »above. All other accounts are blocked. I recommend a short-duration soft rangeblock of 92.40.0.0/16 - there may be some collateral damage, but not too much...
Click to read more »a confirmed match. No sleepers found. Unfortunately, at the moment, a rangeblock is not possible either. Salvio Let's talk about it! 01:18, 9 December...
Click to read more »case will be soon Declined if there is no any serious disruption for rangeblock. SA 13 Bro (talk) 02:40, 10 July 2017 (UTC) When given an account and...
Click to read more »A noticeboard report was made at Block evasion by TannerGoethals3 – rangeblock?, which showed Utah IPs being used by TannerGoethals3. Later, TowerPizza...
Click to read more »requesting checkuser on the accounts (not the IPs) for the potential of a rangeblock. Reaper Eternal (talk) 20:06, 11 September 2012 (UTC) Accused parties...
Click to read more »the pattern of edits by the IPs in the archive [4][5][6]. Expanding the rangeblock won't capture the new IP, so it'll need to be a fresh block. I've checked...
Click to read more »other activity on the range that looks like Chrysalix, but if they hop we may need to rangeblock. GeneralNotability (talk) 00:11, 2 September 2020 (UTC)...
Click to read more »socking activity by several IPs in the 189.41 range, too widely spread to rangeblock. JohnCD (talk) 17:35, 13 March 2013 (UTC) Accused parties may also comment/discuss...
Click to read more »2008 (UTC) Adding two more, same as above. Can we just smack them with a rangeblock pls? [ roux ] [x] 00:43, 6 November 2008 (UTC) Some of the accounts above...
Click to read more »with the filter description "Repeating characters" (details). I think a rangeblock on these IPs is needed. KMagz04 (talk) 10:27, 30 May 2020 (UTC) Accused...
Click to read more »blocked each IP for 31 hours. Not sure much can be done in the way of a rangeblock because of how wide it would need to be. SQLQuery me! 15:35, 30 November...
Click to read more »blocked and tagged per WP:DUCK. —DoRD (talk) 20:02, 5 August 2011 (UTC) Rangeblock/Master? -- DQ (t) (e) 20:17, 5 August 2011 (UTC) A lot of these are Stale...
Click to read more »person, but I don't think there's enough activity out of them to warrant a rangeblock. Honestly I'm not sure how to go from here, given that it doesn't seem...
Click to read more »(talk) 01:59, 16 July 2009 (UTC) Completed No obvious sleepers. Short rangeblocks could be possible in the event this continues. – Luna Santin (talk) 05:37...
Click to read more »think any further block is possible here. While there is a small (/24) rangeblock that could be applied, I do not think it would be particularly effective...
Click to read more »against User:Jasepl. See contribs and this SPI for evidence. Recommend IP rangeblock. BlazerKnight (talk) 14:46, 6 November 2009 (UTC) User:203.76.185.35 has...
Click to read more »(apparently the superpower is Amazing Proxy Use), and a short zero-collateral rangeblock applied to the others. — Coren (talk) 23:45, 1 April 2010 (UTC) So are...
Click to read more »Clerk declined. You already have the IPs, so CU isn't necessary here. A rangeblock is also not feasible. Elockid (Talk) 12:03, 9 June 2010 (UTC) Administrator...
Click to read more »couple of rangeblocks for the 130.88 IPs.[33] (Actually, I did it a couple of hours before this SPI was filed.) These were my very first rangeblocks, so let...
Click to read more »in this section below. See Defending yourself against claims. Damn. A rangeblock doesn't even look possible. King of ♥ ♦ ♣ ♠ 22:34, 16 June 2013 (UTC)...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan IP is edit warring on the article Pro-life movement which...
Click to read more »appear to belong to a Peruvian ISP, but the range is way too wide for a rangeblock, so unfortunately this will be a game of whack-a-mole. GeneralNotability...
Click to read more »issues associated with rangeblock. GiantSnowman 00:29, 15 April 2011 (UTC) If you now favor a community ban over a rangeblock, then perhaps the header...
Click to read more »Rlevse about the continuous flow of sockpuppets. I'm requesting that a rangeblock be applied to include the underlying IPs, assuming the collateral damage...
Click to read more »another being blocked, so there are multiple underlying IPs. Is a short rangeblock feasible to try to keep the sock-drawer closed? DMacks (talk) 02:36, 5...
Click to read more »blocks then please re-report. Thorncrag 21:02, 10 October 2010 (UTC) Rangeblock = Done. -- Cirt (talk) 11:05, 14 October 2010 (UTC) Confirmed, this range...
Click to read more »Hopefully autoblock catches any IPs they try to edit from, otherwise a rangeblock can be applied/SKP Zayn protected. Closing. DatGuyTalkContribs 12:42,...
Click to read more »Semi-protection is currently not justified due to low rate of edits. Rangeblock would be overkill (>10 constructive edits every day). Procedure: Report...
Click to read more »only account to account. If there is no serious disruption to warrant a rangeblock, then this case may be declined. jd22292 (Jalen D. Folf) (talk) 05:42...
Click to read more »May 2014 (UTC) Now at Wikipedia:Administrators'_noticeboard/Incidents#Rangeblock_possible.3F --NeilN talk to me 14:08, 31 May 2014 (UTC) The above discussion...
Click to read more »stopped Pflanzgarten's huge empire of sockpuppets by placing a 6 month rangeblock on the underlying IP, and by blocking all of the sleeper accounts, but...
Click to read more »seeking checkuser to root out sock farm, to investigate a potential rangeblock, and to see if there are possible open proxies being used to evade the...
Click to read more »indefinitely. As the IPs have stopped and the IPs are slightly too dynamic for a rangeblock, I've left them alone. Icestorm815 • Talk 19:45, 24 May 2009 (UTC) Conclusions...
Click to read more »Contribs 07:14, 22 April 2009 (UTC) Checkuser is required to see if a rangeblock can be issued on this IP address, to prevent further block evasion. Also...
Click to read more »(already blocked for three months as an open proxy). Yes, some sort of rangeblock is definitely required. SuperMarioMan 23:46, 6 August 2011 (UTC) 64.79...
Click to read more »user to get around the block easily. User:Nancy previously declined to rangeblock the IPs, but the editing pattern has persisted, rendering the indefinite...
Click to read more »collateral on the rangeblock. Hold tight.--Jezebel's Ponyobons mots 19:53, 3 July 2015 (UTC) I tried a couple different rangeblock options and all had...
Click to read more »Iranian Azeris last year [5] and again today on Iranian Kurdistan [6]. A rangeblock may be warranted if abuse continues. And of course, that last edit illustrates...
Click to read more »Britneyspearsfan17 was "my friends account".[1] This person is persistent; needs a rangeblock. Binksternet (talk) 00:15, 24 April 2015 (UTC) I don't understand, isn't...
Click to read more »by clerk for Checkuser attention. Clerk endorsed for a sleeper sweep/rangeblock. Tim Song (talk) 00:51, 13 April 2010 (UTC) A Imp Imp Imp (talk+ · tag ·...
Click to read more »2009 (UTC) Underlying IPs are too dynamic and the range to wide for a rangeblock to be useful now, unfortunately. -- Avi (talk) 05:55, 29 March 2009 (UTC)...
Click to read more »the same person, and that this person is IP-hopping; unfortunately, rangeblocking is out of the question. But I ask: is there a reason why a block is...
Click to read more »Defending yourself against claims. Administrator note I've redone my previous rangeblock of the /24, this time for a month; let me know if it reoccurs again. I've...
Click to read more »Defending yourself against claims. I've made a couple of underlying rangeblocks (as a regular admin action) to help with the TA creations. I'll leave...
Click to read more »note Confirmed account is blocked and tagged. And I think the IP is within an IP rangeblock. — HelloAnnyong (say whaaat?!) 02:05, 6 November 2010 (UTC)...
Click to read more »contribs) and Typhoonwikihelper3 reborn (talk · contribs). If possible, a rangeblock of the underlying IP (something in the range of 116.48.192.134 (talk ·...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan which also edit warred on the Teardrop trailer article...
Click to read more »May 2010 (UTC) Clerk endorsed to check for sleepers and also a possible rangeblock. Also note that White Trillium is a flower just like what Sego Lily has...
Click to read more »couple more socks lying around that we don't initially spot. Also, can a rangeblock please be implemented for this user, because he's being doing this since...
Click to read more »sleepers. Ks0stm (T•C•G•E) 23:48, 15 December 2015 (UTC) Also, a check for a rangeblock would be helpful; that's a lot of accounts in a short time. Ks0stm (T•C•G•E)...
Click to read more »this section below. See Defending yourself against claims. Note On the rangeblock, short-term may be preferred as the master has used different ranges (on...
Click to read more »do here. With edits this infrequent we can't really justify a longterm rangeblock, and all the articles they edit are different enough that we can't protect...
Click to read more »Snowball91 (talk · contribs). —Soap— 18:46, 11 September 2010 (UTC) A rangeblock would be nice to prevent any more of these popping up. As a would a sleeper...
Click to read more »requested and endorsed by clerk - A brief look to see if an underlying rangeblock is possible would be great; if not, it's not exactly strenuous work here...
Click to read more »Administrator note I've blocked all three IPs for a few days. Note that a rangeblock isn't possible here; from what I can see there'd be collateral. — HelloAnnyong...
Click to read more »suggesting it is highly dynamic. With just 2 IPs, I can't really tell if a rangeblock would be possible or if feasible. Shubham Chaturvedi salted for 1 week...
Click to read more »hour. Clear block evasion (same behaviors); requesting CU for sleepers/rangeblock. ᴀɴᴏɴʏᴍᴜᴤᴤ ᴜᴤᴇʀ (ᴛᴀʟᴋ) 23:40, 4 March 2019 (UTC) Diff: [1] Diff: [2] Accused...
Click to read more »and IPv6 respectively). The first highlighted possible problems with rangeblocks, while the second related to a number of issues, including problems with...
Click to read more »all the same person just moving around, but it's far too wide to do a rangeblock. Is anything else needed? — HelloAnnyong (say whaaat?!) 04:10, 8 January...
Click to read more »2010 (UTC) This is getting rather tiring. I request a CU to see if a rangeblock is feasible, and to indeed see if there are any other socks out there...
Click to read more »comment/discuss in this section below. See Defending yourself against claims. Rangeblock in place. In the future, it's best to take this kind of thing to WP:AIV...
Click to read more »bored of it. 74.13.33.150 (talk) 15:53, 20 November 2007 (UTC) A 3-hour rangeblock of 74.13.0.0/16 brought only temporary relief, and this user is back restoring...
Click to read more »check to see if this is part of a bigger spam farm and to possibly set a rangeblock to contain this. -- asilvering (talk) 14:48, 7 July 2025 (UTC) CU says...
Click to read more »so as to ensure that there is no collateral damage in the event that a rangeblock is implemented on the 149.135.147.x addresses, and to identify sleepers...
Click to read more »and is IP hopping more frequently now to avoid being blocked. Again, rangeblocking is not an option, as most of the IPs he is using are assigned for a...
Click to read more »appears to be in the same range as prior socks. I am guessing that the rangeblock entered after the most recent report has expired. JohnInDC (talk) 03:46...
Click to read more »confirm block evasion and look for sleepers. Checkusers may advise whether rangeblocks may prove effective at preventing further disruption. — Berean Hunter...
Click to read more »patrolling admin and checkuser comments Clerk endorsed to check for rangeblock potential. — Jake Wartenberg 21:47, 22 June 2009 (UTC) Confirmed Superkierz...
Click to read more »endorsing now to check for sleepers and to see if we can get some form of rangeblock. — HelloAnnyong (say whaaat?!) 21:29, 8 January 2011 (UTC) No other sleepers...
Click to read more »IPs (172.129.0.0/16) would have considerable collateral damage, so a rangeblock is more or less out. — HelloAnnyong (say whaaat?!) 02:23, 30 July 2011...
Click to read more »checkuser to find the master and issue a stern warning, potentialy a rangeblock, depending on how much disruption has been caused. – Phoenix B 1of3 (talk)...
Click to read more »this editor persists in socking, it may be possible to apply a narrow rangeblock which will not affect other editors as they're all in a /22 range - Alison...
Click to read more »core packaged with 1.20wmf5 including drastically increasing the IPv6 rangeblock limit to /19 in size and changing the display order for the recently separated...
Click to read more »against claims. Yes, we need a thorough sweep for sleepers and possible rangeblock. Please. Thanks —DoRD (talk) 15:50, 9 September 2011 (UTC) Clerk endorsed...
Click to read more »account in a week and a half, a check for sleepers and/or an underlying rangeblock would be great. --Jack Frost (talk) 01:44, 24 February 2022 (UTC) In progress...
Click to read more »utility Need a CU magic wand to pull out the whole series, and hopefully rangeblock (yes, some collateral damage is likely). I suspect there are dozens, and...
Click to read more »are you proposing we do here? Given the wide range of IP addresses, a rangeblock is not possible. At best, we will just have to play whack-a-mole. Tiptoety...
Click to read more »GP38-2. Forgive me but I do not understand ranges of IPs very well, can a rangeblock be applied here? Trainsandotherthings (talk) 00:35, 18 January 2022 (UTC)...
Click to read more »making a report here to hopefully flush any sleepers out, and to see if a rangeblock is possible. Simplexity22 (talk) 04:07, 12 August 2017 (UTC) Accused parties...
Click to read more »a lot lately (example 1 example 2), it got so bad JamesBWatson had to rangeblock 2600:1:b14a:576::/64 due to the disruption. Sro23 (talk) 17:38, 9 October...
Click to read more »here. --ToonLucas22 (talk) 22:07, 10 March 2015 (UTC) I'm afraid that a rangeblock (of 101.191.0.0/17) would cause too much collateral damage, i.e. innocent...
Click to read more »I'd recommend to RBI. Amalthea 11:16, 30 April 2013 (UTC) Clerk note: A rangeblock has been applied, but for now it's just WP:RBI and protect targets (like...
Click to read more »rangeblocks beyond a certain time period will be reviewed. The rangeblock is reverted unless there is strong reasons not to. All reverted rangeblocks...
Click to read more »CU necessary. –MuZemike 16:42, 26 May 2010 (UTC) Administrator note Rangeblocking is not possible due to collateral damage. Columbia, South Carolina semi-protected...
Click to read more »that I have blocked the user who created this, and another admin did a rangeblock on all the IP addresses they were using to add nonsense to this article...
Click to read more »IPs. --Deskana (talk) 20:51, 18 July 2010 (UTC) Blocked and tagged. No rangeblock on 115.117.224.0/19 as there is insufficient disruptive activity to warrant...
Click to read more »feel it is appropriate. If the ips begin editing again, we can look to rangeblock if nessasary, or if you see anymore accounts, please reopen this case...
Click to read more »hard to block – range but clearly them, see [10][11][12][13][14][15]. A rangeblock doesn't strike me as justifiable at this point, but temporary /64 blocks...
Click to read more »except block them as spam-only accounts. Typically a CheckUser-based rangeblock requires far more abuse than this. King of ♥ ♦ ♣ ♠ 02:08, 26 June 2013...
Click to read more »Sjones23 (talk - contributions) 16:11, 31 July 2010 (UTC) I've placed a rangeblock on 113.22.0.0/17, which should at least slow him/her down. Worth keeping...
Click to read more »checkuser request to root out sock-farms, or possibly institute some form of rangeblock or something. I don't think its gotten there yet, and so far we've been...
Click to read more »removal and same edit summary almost every time. Added all the IPs incase a rangeblock is called for, and the fact that two named accounts were made without...
Click to read more »MurunB is Unlikely, all the rest are Likely or Confirmed. Unfortunately a rangeblock is not possible here, and trying to find other accounts preemptively is...
Click to read more »each other. All of them are confirmed by virtue of sheer craziness. Rangeblocks were considered, but the range is a bit too big. Drmies (talk) 16:49...
Click to read more »these accounts have been tagged and blocked. As to the IP, there's a rangeblock currently in effect for it, I think, so there's not much more to do here...
Click to read more »21:22, 12 March 2011 (UTC) No sleepers that I saw. As for the IP block, a rangeblock is a no-go and this ISP seems to reassign IPs pretty quickly anyway. TNXMan...
Click to read more »They're also on the same /24 as previously, which could do with another rangeblock (noting that any action taken will not be publically confirmed). Jack...
Click to read more »two, I'm going to say that they are not related. However, I have made a rangeblock on 79.139.202.144/28 (as opposed to the singular block on 79.139.202.149)...
Click to read more »might be needed because the IP is moving around and I don't know if a rangeblock is needed but I'm almost positive there's another IP I've just missed...
Click to read more »transcluded. (r41861, bug 13179) Searching Special:IPBlockList now reveals rangeblocks that block a particular IP, as well as blocks directly on that IP. (r41902...
Click to read more »range. Admins routinely disregard or give less weight to AFD votes. Rangeblocking does not appear practical or necessary to deal with AFDs. His range...
Click to read more »disruptive edits. Further disruption can be reported to AIV, or if the IP hopping continues, a rangeblock can be considered. TNXMan 15:10, 25 August 2010 (UTC)...
Click to read more »station articles that are unsourced or unintelligible gibberish. A long rangeblock might be appropriate if possible since these are dial-up IPs from a glance...
Click to read more »tagged; Clerk declined for the IPs although I will see about constructing a rangeblock. Ivanvector (Talk/Edits) 14:00, 13 February 2018 (UTC) Clerk note: I can't...
Click to read more »address changes often (the only consistent IP being 98.219.220.18), so a rangeblock might be needed. That's just a suggestion, as I am no administrator. DarkKnight2149...
Click to read more »Defending yourself against claims. There's a very large and very long-term rangeblock in place where some of these accounts have edited, so it's hard to say...
Click to read more »Shirik's comment below, I've separated some of the similar IPs and used the rangeblock calculator on those. Here is what I got: 123.237.208.0/21 (block range...
Click to read more »awards, endowments, and rankings. To date, this has led to numerous /16 rangeblocks, the long-term full-protection of at least two articles, and an unsuccessful...
Click to read more »serious problem it might be worth considering an SPI case / checking for rangeblocks / etc, but currently not necessary. Closing, given that both accounts...
Click to read more »useful; they are BT Public Internet Service and too widely scattered for a rangeblock. CU requested to see if there are any sleepers or any more we have not...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Seems like many persons are using this IP. Possible proxy...
Click to read more »account above does not have any sleepers I saw and there is already a rangeblock in place. I don't see much to do here and am thus marking for close. TNXMan...
Click to read more »caught in an autoblock based on talk page. Check for sleepers/possible rangeblock. Jon Kolbert (talk) 05:45, 28 March 2019 (UTC) Accused parties may also...
Click to read more »be done here. The ranges are far too wide to do any sort of effective rangeblock. Closing for now, but relist if things change. — HelloAnnyong (say whaaat...
Click to read more »filter log · block user · block log) There's the possibility of a /24 soft rangeblock here, if this guy persists - Alison ❤ 19:37, 29 September 2008 (UTC) Clerk...
Click to read more »be cleaned up. Hoping a checkuser can look into this and formulate a rangeblock to deal with it. Beeblebrox (talk) 15:36, 8 July 2015 (UTC) Accused parties...
Click to read more »used too, but he seems to switch several times a day so significant rangeblocks would be required. I'm not sure if that's the route you want to go. Previously...
Click to read more »spamming external links to howtodiscuss.com. See contribs. I would suggest a rangeblock for the IPs. 4thfile4thrank (talk) 03:00, 1 January 2021 (UTC) Accused...
Click to read more »claims. They IP-hopped, looks like a fairly dynamic range. Applied a rangeblock for a couple weeks. Closing. GeneralNotability (talk) 03:11, 21 August...
Click to read more »Defending yourself against claims. I'm not sure if I can even do such a rangeblock, nevermind it being so big, it could have major affects blocking that...
Click to read more »edited Film noir - oh dear! IP blocked - all of them. There is also a wide rangeblock active. - Alison ❤ 01:09, 17 December 2007 (UTC) OrderOfBush4 (talk+ ·...
Click to read more »left that one alone for now. If the socking continues, I'll reconsider a rangeblock. Nishkid64 (Make articles, not wikidrama) 19:39, 1 December 2008 (UTC)...
Click to read more »person is going from IP to registered account and now back to IP. Now, a rangeblock on 76.16.176.0/21 might be possible to prevent abuse from that range currently...
Click to read more »dynamic IPs, though a rangeblock could be considered. There is probably not enough volume of vandalism to justify a rangeblock. EdJohnston (talk) 00:52...
Click to read more »are below. Clerk endorsed To check for any more sleepers and a possible rangeblock/IP block. --Bsadowski1 07:24, 27 May 2010 (UTC) Confirmed with respect...
Click to read more »might be the best solution if this continues, as getting an effective rangeblock in place is probably going to be a bit tricky here. SpitfireTally-ho!...
Click to read more »Sockmaster appears to be User:Icecreamarmageddon. I'm applying a soft rangeblock to the ISP (AO/ACB) as almost all accounts on here are vandalism-only...
Click to read more »but perhaps CU will dredge up a couple more, or help us decide if a rangeblock is feasible. –Roscelese (talk ⋅ contribs) 00:21, 25 September 2011 (UTC)...
Click to read more »block · block log · CA · CheckUser(log) · investigate · cuwiki · SI) A rangeblock is not possible. Page protection might be the best thing to do. WilliamH...
Click to read more »Netsnipe ► 10:56, 16 April 2010 (UTC) Clerk endorsed for a sleeper check. Rangeblock is out of the question, though. Tim Song (talk) 11:15, 16 April 2010 (UTC)...
Click to read more »Interaction Timeline · SPI Tools Created 6 days after the most recent rangeblock was handed down and immediately returns to the same topics. Someone who's...
Click to read more »nyah-nyah at my talk page in second edit. [8] Might want to look at a rangeblock. Wikishovel (talk) 17:32, 15 February 2024 (UTC) Accused parties may also...
Click to read more »comment/discuss in this section below. See Defending yourself against claims. A rangeblock may be needed, as a similar anonymous reversion attempt was made yesterday...
Click to read more »Range blocked. —DoRD (talk) 15:16, 5 October 2012 (UTC) Sorted with rangeblock. Tagged users. NativeForeigner Talk 02:54, 8 October 2012 (UTC) Facebookfakename...
Click to read more »Mayalld (talk) 12:37, 27 April 2009 (UTC) Clerk endorsed to seek possible rangeblock Mayalld (talk) 12:37, 27 April 2009 (UTC) Clerk, patrolling admin and...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Obvious block evasion by 91.155.234.89 (talk · contribs ·...
Click to read more »again. So, can an administrator/checkuser look at the IP range and do a rangeblock? Can the checkuser investigating this case also see if there are any older...
Click to read more »deleted contribs · logs · filter log · block user · block log) I foresee a rangeblock or two in the near future! - Alison ❤ 21:36, 27 August 2008 (UTC) Clerk...
Click to read more »requesting a checkuser to check for collateral damage associated with a rangeblock to address this issue. --Shirik (Questions or Comments?) 03:55, 22 April...
Click to read more »user is hopping across IPs, and 24.4.0.0/16 is too busy to anon-only rangeblock. Hence, blocking the IPs won't do much good here. MuZemike 19:45, 19 October...
Click to read more »functional "range contributions" tool to facilitate the calculation of rangeblocks. Statistics suggest that IPv6 addresses account for some 50 million Wikimedia...
Click to read more »Mark Arsten (talk) 03:44, 12 October 2013 (UTC) All three Confirmed. Rangeblocks unfortunately impossible. NativeForeigner Talk 10:25, 12 October 2013...
Click to read more »the way, 6-12 month rangeblocks would be really helpful here in suppressing IP socking and serial sock creation. (Shorter rangeblocks have already proven...
Click to read more »are continued edits in violation of policy from this range, then a narrow rangeblock might be justified. ☺ · Salvidrim! · ✉ 18:01, 1 December 2015 (UTC)...
Click to read more »Conclusions Accounts blocked indefinitely. The 68.80.. is too big to rangeblock, 67.201.. is possible, but undesirable (16000+ IPs). I'd suggest semiprotection...
Click to read more »active blocks · stalk · Robtex · whois · Google · ipcheck · HTTP · geo · rangeblocks · spur · shodan Reason: Suspicious edits Background at User_talk:TFOWR#Vandal_alert...
Click to read more »whack-a-mole. The British IPs are messy ranges and I'd advise not to rangeblock those. Elockid (Talk) 22:13, 2 May 2011 (UTC) Yeah, there really isn't...
Click to read more »attacks and harrassment. Could someone who knows about rangeblocks consider whether a rangeblock is feasible to cover other IPs that have evidently used...
Click to read more »(UTC) Clerk, patrolling admin and checkuser comments Clerk endorsed A rangeblock would be nice if possible; otherwise semi-protection is the only way to...
Click to read more »Defending yourself against claims. Gross. Here I was hoping we could set a rangeblock or something. Blocking and tagging who I can, closing. asilvering (talk)...
Click to read more »can you please implement a rangeblock on all of this guy's IP ranges? You mentioned earlier that we could consider a rangeblock later on. It's pretty obvious...
Click to read more »them together. The IPs are entirely separate, so there's no sort of rangeblocking I could do here anyway, and I'm not going to go around protecting all...
Click to read more »Contribs 01:22, 18 November 2009 (UTC) Checkuser is required to see if a rangeblock is feasible, as this user continues to evade his block, disrupting wikipedia...
Click to read more »not blocking it. Although if more IPs come, we can see if we can do a rangeblock. Anyways, I've blocked Brendamwilliams for 2 weeks for repeated abuse...
Click to read more »Google: search • meta • Domain: domaintools • AboutUs.com Please look for a rangeblock (blacklisting requested). MER-C 07:55, 3 June 2013 (UTC) Accused parties...
Click to read more »blocked 1 month. I'm afraid there would be too much collateral damage for a rangeblock. –MuZemike 17:24, 19 March 2010 (UTC) Sonasty1 (talk+ · tag · contribs ·...
Click to read more »the IP Range would also get a multi-month rangeblock, but anything short of an "anon-only" Global Rangeblock would likely fail to be fully effective. LightandDark2000...
Click to read more »Sleepers, other socks and a couple of open proxies have been blocked, but no rangeblock is possible at this time. —DoRD (talk) 15:56, 29 September 2012 (UTC)...
Click to read more »a checkuser to check the range for active users and consider doing a rangeblock. —— nixeagleemail me 14:52, 11 February 2009 (UTC) Actually... yea lets...
Click to read more »12:26, 21 August 2013 (UTC) Add 111.90.189.42 as another sock. Perhaps a rangeblock is in order? --Saddhiyama (talk) 09:09, 22 August 2013 (UTC) See also...
Click to read more »keeps removing my deletion template on the current page. We might need a rangeblock? ImacelebritygetmeoutofhereAU is indefinitely blocked. This can be closed...
Click to read more »the CIDR notation (which is essential for any type of rangeblocking) and have made many rangeblocks. I am also able to read WHOIS and geolocation information...
Click to read more »Administrator note In addition to Elen's block, I have placed a short rangeblock. Elockid (Talk) 00:50, 10 March 2011 (UTC) Suspected sockpuppets 79.113...
Click to read more »IP used, so blocked that for a short amount of time. Unfortunately, a rangeblock doesn't look likely as the range is to big. Elockid (Talk) 00:23, 17 April...
Click to read more »contribs), Nickyjboy (talk · contribs). If we could get a CU to do a rangeblock, that would be great. I've semiprotected the article, so now they got...
Click to read more »comment about the identification of the user, but I can tell you that a rangeblock is impossible. Each IP is just going to have to be blocked when it comes...
Click to read more »requesting CU not because of sleepers, but to see if anything like a rangeblock can be done. The evidence is [3] and [4]. They also spam the same thing...
Click to read more »Blocked for 48 hours. NW (Talk) 02:04, 10 September 2009 (UTC) Actually rangeblocking may be a more efficient solution, so I have done that instead (159.91...
Click to read more »semi-protection) due to the good faith IPs editing there. A CheckUser has said that rangeblocking is not feasible here. –MuZemike 03:11, 14 July 2010 (UTC)...
Click to read more »