Wikipedia:Abuse response/38.116.200.64

Discussion

This IP has recently been unblocked after a 6-month block for anonymous edits. Abuse has continued starting December 11 on only a handful of pages (see contribution history for IP). This may be worth keeping an eye on given the block history for this IP. Didn't check the range. Pieter-Bas (talk) 21:27, 13 December 2007 (UTC)

Just checked for range. Abuse happens for many IPs in this range. Found concrete examples of vandalism for .65, also .60 and .53. Possibly these all belong to the same range for this school, but I could not confirm this from whois. Leaving this to the wikipedia admins for the rest, but it seems this deserves attention. Pieter-Bas (talk) 21:44, 13 December 2007 (UTC) Please contact abuse@cogentco.com. GO-PCHS-NJROTC (talk) 22:51, 28 January 2008 (UTC)
 * Accept for investigation, report all of these vandal IPs. GO-PCHS-NJROTC (talk) 00:56, 25 January 2008 (UTC)

=Contact Report= Taking case for contact. -- zrulli 19:42, 6 February 2008 (UTC)

Initial contact sent, awaiting reply. -- zrulli 20:07, 6 February 2008 (UTC)

Still Waiting. -- zrulli 13:05, 21 February 2008 (UTC)

This ip is a schoolip, suggest that you try contacting Peel District School Board, Mississauga, Ontario, http://www.peel.edu.on.ca who have one ip per school through the entire 38.116.200.* range. Most of these have been ongoing problems to a greater or lesser degree.LeadSongDog come howl  20:02, 20 May 2009 (UTC)

Reattempting Contact
Since it has been a while since anyone from Abuse reports has sent an abuse report to the responsible organization, I'm going to send another email to notify them of the abuse. If you need to contact me, please message me on my talk page. Thanks.

I've closed all requests that have this template, because a second attempt was done to contact the responsible organizations. The results were overall positive, as I did receive some replies that indicated that the responsible organization was going to look into the issue. The reports that were sent to ISPs all received automated responses, also promising to look into every case. Netalarm 15:28, 21 July 2009 (UTC)  Netalarm  04:57, 19 July 2009 (UTC)
 * Update