Jump to content

Wikipedia:Abuse response/121.221.222.124

From Wikipedia, the free encyclopedia

This is the current revision of this page, as edited by MalnadachBot (talk | contribs) at 05:20, 17 January 2022 (Replaced obsolete font tags and reduced Lint errors. (Task 12)). The present address (URL) is a permanent link to this version.

(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

121.221.222.124 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log)

Abuse Response
Report Status
IP Address121.221.222.124
ContributionsContributions
Page MovesPage moves
Block LogBlock log
Contribution HistoryContribution history
StatusOn hold
RequestorJevansen (talk)
Date00:47, 17 September 2010 (UTC)
InvestigatorPending
ContactorPending




Requester comments

Person has been vandalising wikipedia since late 2007. He is an IP hopper so it is impossible to meet the "five blocks" criteria requested.

Please see list at User:Jevansen/IP Vandal for a selection of 60 IPs that he has used, with the most recently active in bold. Articles or topics that he has edited are in brackets next to each IP to help prove they are all from the same author. Below the list is a legend which explains each topic and gives examples.

Geolocate reveals the following information, consistent for each and every one of the IPs -

  • ISP: Telstra
  • Domain: Bigpond
  • Weather Station: ASXX0230 - MOUNT LAWLEY PERTH METRO

Discussion

Discussion

I do agree that this is a case that we should handle and I am sorry we haven't gotten to it. So ISPs aren't going to have things older than six months so could we get a list of the IPs used in the last six months? (Because that's a huge list of IPs) and then we will report on that basis. -- DQ (t) (e) 19:24, 19 December 2010 (UTC)[reply]

Registry information


Abuse summary

No abuse summary entered.


Contact summary

No contact history entered.

Case history

Investigated by:
Contacted by: Investigator
Closed on:
Disposition:


Case log: