Last modified: 2012-07-30 18:31:26 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 6643 - Mysterious IP block
Mysterious IP block
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-07-12 06:30 UTC by mango_juice
Modified: 2012-07-30 18:31 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description mango_juice 2006-07-12 06:30:56 UTC
This happened on en.wikipedia.

I was briefly blocked two separate times tonight; my IP address was, but the 
block page listed the blocker as "[[User:|]]", which I know isn't right.  I looked through 
enough of the IP block list to be sure no applicable block was out there.  It didn't last very 
long (about 5 minutes max?), but this would be very annoying to a less seasoned editor than 
myself ([[User:Mangojuice]] on en.wikipedia.)
Comment 1 Nicolas Ray 2006-07-13 09:37:04 UTC
Just to mention that it also happened to me several times in the same conditions
with the same message on fr.wikipedia ([ Ray]).
Being admin over there, I checked and my IP address wasn't registered as blocked
in the logs.

Comment 2 Melancholie 2009-02-10 18:03:46 UTC
Does this still happen?
Comment 3 matanya 2012-07-30 18:31:26 UTC
didn't hear about it for more than 3 years. works for me.

Note You need to log in before you can comment on or make changes to this bug.