This is an archived case at Abuse Response. | ||
![]() |
The page you are viewing is an archived case (or possibly other) page located at
Abuse Response. It is no longer used but is preserved for archival purposes. You may observe anomalies, inconsistencies, or other general weirdness, which is to be expected. No warranty of usefulness or satisfaction implied. |
![]() |
Discussion
This IP has gotten blocked five times for vandalism and has a bunch of warnings on its talk page. However, the WHOIS data and nslookup fail to turn up any evidence that this is a school. A recent open proxy check shows that this is not one of them, and the checker thinks that this is probably a school. However, WHOIS states that the owner of this IP is Cox Communications, a cable company which sells cable modem services. If this is a school, we need to let its administrators know about the situation. If it is just a bad cable modem customer, a bad relative of a cable modem customer, or someone using an open Wi-Fi router, Cox needs to be notified so that it can throw off the bad customer or have the customer do something about the bad relative or enable WPA2 on the Wi-Fi. Jesse Viviano ( talk) 04:40, 22 February 2008 (UTC)
The following abuse report was sent to abuse@cox.net on 02/22/2008:
Please see these vandalism logs: THESE LOGS USE GMT -05:00
Log of 68.96.16.71:
Auto reply recieved
GO-PCHS-NJROTC ( talk) 01:39, 24 February 2008 (UTC)
Since it has been a while since anyone from Wikipedia: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 05:00, 19 July 2009 (UTC)
This is an archived case at Abuse Response. | ||
![]() |
The page you are viewing is an archived case (or possibly other) page located at
Abuse Response. It is no longer used but is preserved for archival purposes. You may observe anomalies, inconsistencies, or other general weirdness, which is to be expected. No warranty of usefulness or satisfaction implied. |
![]() |
Discussion
This IP has gotten blocked five times for vandalism and has a bunch of warnings on its talk page. However, the WHOIS data and nslookup fail to turn up any evidence that this is a school. A recent open proxy check shows that this is not one of them, and the checker thinks that this is probably a school. However, WHOIS states that the owner of this IP is Cox Communications, a cable company which sells cable modem services. If this is a school, we need to let its administrators know about the situation. If it is just a bad cable modem customer, a bad relative of a cable modem customer, or someone using an open Wi-Fi router, Cox needs to be notified so that it can throw off the bad customer or have the customer do something about the bad relative or enable WPA2 on the Wi-Fi. Jesse Viviano ( talk) 04:40, 22 February 2008 (UTC)
The following abuse report was sent to abuse@cox.net on 02/22/2008:
Please see these vandalism logs: THESE LOGS USE GMT -05:00
Log of 68.96.16.71:
Auto reply recieved
GO-PCHS-NJROTC ( talk) 01:39, 24 February 2008 (UTC)
Since it has been a while since anyone from Wikipedia: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 05:00, 19 July 2009 (UTC)