Jump to content

User talk:Cromium/Archive 18

Add topic
From Meta, a Wikimedia project coordination wiki
Latest comment: 3 years ago by Xaosflux in topic 10.64.32.67


17:45, 30 November 2020 (UTC)

16:15, 7 December 2020 (UTC)

21:34, 14 December 2020 (UTC)

20:54, 21 December 2020 (UTC)

15:42, 11 January 2021 (UTC)

16:10, 18 January 2021 (UTC)

18:31, 25 January 2021 (UTC)

22:38, 1 February 2021 (UTC)

17:42, 8 February 2021 (UTC)

17:56, 15 February 2021 (UTC)


00:17, 23 February 2021 (UTC)


19:08, 1 March 2021 (UTC)

17:51, 8 March 2021 (UTC)

23:23, 15 March 2021 (UTC)

16:53, 22 March 2021 (UTC)

17:31, 29 March 2021 (UTC)

19:41, 5 April 2021 (UTC)

Mistakenly blocked in a global IP block

[edit]

Hello,

It appears I have been mistakenly included in a global IP block you made today on 10.64.32.67. I have never vandalized Wikipedia or any MediaWiki project, and you can see my contributions here: https://en.wikipedia.org/wiki/Special:Contributions/Percivl Weirdly enough, I'm not editing on a proxy nor have I ever edited on a proxy, so I'm not sure why I was included in this ban.

Is there a way for you to permit me a global IP block exemption? I'd sincerely appreciate it.

Thanks, Percivl (talk) 18:29, 7 April 2021 (UTC)Reply

  • I'm also blocked from editing enwp, the message says something about a proxy server ... I am not using a proxy server. Mistake? - Bri (talk) 18:33, 7 April 2021 (UTC)Reply
  • I am also included in this global IP block, despite the fact that I am not using a proxy server, I am using the same apartment WiFi that I've been using the whole time I've edited. Kncny11 (talk) 18:40, 7 April 2021 (UTC)Reply
I have also been affected by this block, presumably by mistake. I'm not editing on a proxy (I don't even know how those work), much like the two contributors above me. The block reason was for "cross-wiki spam", but I only edit on the English Wikipedia and mainly do vandalism reverting there. MerelyPumpkin (talk) 18:41, 7 April 2021 (UTC)Reply

One of my IP's are banned?

[edit]

Ok so when I tried editing a article, it said that the ip of 10.64.32.67 was blocked for one year... despite the fact that I never used this proxy. I have no idea how this specific IP has affected me but I can't even edit in articles anymore. I use public IP's on at least 3 different devices though they are all logged in with this account and I never editied anonymously. I want to continue editing in enwiki but I don't know how to do when it feels like my account is blocked, is there anything I can do to continue editing? --SuperSkaterDude45 (talk) 18:40, 7 April 2021 (UTC)Reply

10.64.32.67

[edit]

Hi GG, looks like there is something odd going on with your block of 10.64.32.67. Not sure why anyone is presenting with this unroutable IP but it prob shouldn't be blocked? — xaosflux Talk 18:48, 7 April 2021 (UTC)Reply

Hi Green Giant. I pinged stewards on IRC and Martin Urbanec has removed the block while we figure out what happened here...it's unclear exactly what went wrong, but it looks like this global block somehow hit a LOT of people it shouldn't have. I'm curious where this IP came from in the first place, since 10. IPs would be internal to the WMF network... GeneralNotability (talk) 18:49, 7 April 2021 (UTC)Reply
Apologies to the people affected by this @Percivl, Bri, Kncny11, MerelyPumpkin, Teishin, Mediocre Legacy, and SuperSkaterDude45:. It wasn’t intended to block any of you specifically and I hope you are now able to edit again.
@Xaosflux, GeneralNotability, and Martin Urbanec: I’m not sure what has happened here but this IP was one of three being presented on an XFF header when I checked an IP being used by a spammer. I am not sure how we can look into it further without repeating the Checkuser I did earlier. Martin, thank you for undoing the block. --Green Giant (talk) 22:45, 7 April 2021 (UTC)Reply
We chatted in IRC a bit on this, maybe there is something on your stewards mailing list. Seems to be a possible temporary problem with one of the load balancers/WMF proxies passing that on. FWIW anything in RFC 1918 ranges usually mean something is broken :) — xaosflux Talk 00:47, 8 April 2021 (UTC)Reply

16:49, 19 April 2021 (UTC)

21:25, 26 April 2021 (UTC)