Message I get: You are currently unable to edit Wikipedia. You are still able to view pages, but you are not currently able to edit, move, or create them.
Editing from 190.10.0.0/17 has been blocked (disabled) by GeneralizationsAreBad for the following reason(s): Banned proxys.svgThe IP address that you are currently using has been blocked because it is believed to be an open or anonymizing proxy. To prevent abuse, these proxies may be blocked from editing Wikipedia. If you are using an open proxy you will need to turn it off to edit Wikipedia.
If you believe you are not running an open proxy, the most likely cause is that another customer using your IP address who was previously assigned this IP address was running an open proxy. You may appeal this block by adding the following text on your talk page:
Rivercosta (block log • active blocks • global blocks • contribs • deleted contribs • filter log • creation log • change block settings • unblock • checkuser (log))
Request reason:
Caught by an open proxy block but this host or IP is not an open proxy. My IP address is 190.10.113.97. Place any further information here. Rivercosta (talk) 21:34, 31 December 2018 (UTC)
Accept reason:
See below. You should be able to edit now. NinjaRobotPirate (talk) 12:43, 1 January 2019 (UTC)
.
You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined using whatismyip.com. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system.
More rarely, your network equipment or that of your service provider may be misconfigured or compromised by malicious software (such as a virus). For more information, see the WikiProject on Open Proxies.
This block has been set to expire: 01:44, 30 January 2021.
Even if blocked, you will usually still be able to edit your user talk page and email other editors and administrators.
- To the next reviewing admin, note that 190.10.113.97 does not appear to be running an open proxy any more. However, I'm stepping out so cannot investigate to be sure it's been closed down. I leave that to you. Rivercosta, if you don't get a response in the next 15 hours, please ping me and I'll try to investigate further. --Yamla (talk) 22:55, 31 December 2018 (UTC)
- GeneralizationsAreBad - Would you mind rechecking this range please? I don't see an open proxy on this host specifically, but I'm not sure what lead to the rangeblock, either. SQLQuery me! 02:52, 1 January 2019 (UTC)
- @GeneralizationsAreBad, Yamla, and SQL: Well, I don't anything about this range block, but there was definitely something fishy happening on this IP range in the past. That can probably be explained by this page, which offers colocation services. My guess is that this range block needs to be narrowed, perhaps to 190.10.8.0/21 (tagged as "Servicio Co-Location RACSA"). However, GAB seems to have taken a break for the holidays, so I've gone ahead and done this unilaterally – if someone thinks this needs to be further changed, go for it. NinjaRobotPirate (talk) 12:39, 1 January 2019 (UTC)
- @NinjaRobotPirate, SQL, and Yamla: Thank you all very much for taking care of this. I would appreciate your advice on dealing with sketchy ranges. Best, GABgab 21:10, 1 January 2019 (UTC)
- @GeneralizationsAreBad, Yamla, and SQL: Well, I don't anything about this range block, but there was definitely something fishy happening on this IP range in the past. That can probably be explained by this page, which offers colocation services. My guess is that this range block needs to be narrowed, perhaps to 190.10.8.0/21 (tagged as "Servicio Co-Location RACSA"). However, GAB seems to have taken a break for the holidays, so I've gone ahead and done this unilaterally – if someone thinks this needs to be further changed, go for it. NinjaRobotPirate (talk) 12:39, 1 January 2019 (UTC)
- GeneralizationsAreBad - Would you mind rechecking this range please? I don't see an open proxy on this host specifically, but I'm not sure what lead to the rangeblock, either. SQLQuery me! 02:52, 1 January 2019 (UTC)