User talk:91.121.6.61


 * It would be helpful to reviewing admins if you could copy over the block notice you see when trying to edit. This IP is not directly blocked so it is difficult to evaluate the reasoning behind it. You are probably either autoblocked or rangeblocked. Without knowing which it is it is difficult to review the situation. It also appears that these block appeals are the first ever edits from this IP. If you do have an account it may be possible to grant an IP block exemption but we would need to know what account to apply it to. Beeblebrox (talk) 00:19, 9 October 2012 (UTC)


 * The block message is "open proxy - web hosting company OVH" - you can use the "active blocks" link in the unblock template (second after the IP address) to locate any rangeblocks.
 * As to the block itself, regardless of how stringent their access policies are, I still do not feel that editing from this network is permissible under the no open proxies policy. We do not make a habit of contacting ISPs to determine who is editing from a particular IP address, and use of this network in combination with a "normal" internet connection could allow someone to easily abuse multiple accounts and evade detection. I can certainly see the appellant's side of things, especially since British ISP's are notoriously problematic for checkusers, but I still cannot see that it's worth making an exception for this particular service. To answer the appellant's question, no, it is not possible to unblock a single IP address within a blocked range. Hers fold  non-admin (t/a/c) 16:13, 9 October 2012 (UTC)
 * Well, technically it is possible to recalculate the block and replace it with two narrower rangeblocks, but a) that takes more confidence in one's math and network management skills than most of us would profess and b) we haven't yet had a case where that was deemed to be of such benefit to the project that we needed to do it. Daniel Case (talk) 13:27, 16 October 2012 (UTC)
 * Depending on the size of the range, that also means replacing a single block with around half a dozen or more, which makes things much more difficult to track and manage. Hers fold  (t/a/c) 02:44, 17 October 2012 (UTC)

Will not unblock
The short of it: 99.9% of the traffic from hosting services (and that includes OVH) is disruptive. Those ranges host spambots, open proxies, anonymizers used for socking and trollings, and myriads compromised boxen part of zombie botnets (OVH is only very marginally better than others at preventing those – and yes, I am very familiar with their policies: not only did I work briefly for them as a sysadmin, I also still have servers hosted there).

I did not block this particular range, but I do block those I come across; there are so very few legitimate editors coming from dedicated and VPS ranges that it makes no sense to not block them at the first sight of abuse. So, no, the range will not be unblocked.

Even if you are unwilling or unable to change your routing/proxy use to avoid using that endpoint while editing Wikipedia, you can ask for a named account using this tool, which could then be allowed to edit through the block. (You might want to mention this discussion in the comments field to simplify and expedite matters). &mdash; Coren (talk) 13:44, 19 October 2012 (UTC)