Wikipedia:Requests for page protection
 | This page has an administrative backlog that requires the attention of willing administrators. Please replace this notice with {{no admin backlog}} when the backlog is cleared. |
| Welcome—request protection of a page, file, or template here. | ||
|---|---|---|
|
Before requesting, read the protection policy. Full protection is used to stop edit warring between multiple users or to prevent vandalism to high-risk templates; semi-protection and pending changes are usually used to prevent IP and new user vandalism (see the rough guide to semi-protection); and move protection is used to stop pagemove revert wars. Extended confirmed protection is used where semi-protection has proved insufficient (see the rough guide to extended confirmed protection). After a page has been protected, it is listed in the page history and logs with a short rationale, and the article is listed on Special:ProtectedPages. In the case of full protection due to edit warring, admins should not revert to specific versions of the page, except to remove obvious vandalism.
Request addition of protection to a page, or increasing the current protection level
Request removal of protection from a page, or reducing the current protection level
Request a specific edit be made to a protected page
Request the non-urgent protection of multiple pages that do not require immediate administrator attention
| ||
Current requests for increase in protection level
Place requests for protection increases at the BOTTOM of this section. If you cannot find your request, check the archive of requests or the page history. Only recently answered requests are still listed here.
Indefinite create protection: Repeatedly recreated – As one user has repeatedly recreated this template under multiple names, please set to require at least WP:TPE to create if not admin only. Zackmann (Talk to me/What I been doing) 14:05, 1 August 2026 (UTC)
Temporary semi-protection: Persistent addition of unsourced or poorly sourced content – Persistent unsourced additions of a possible football transfer. • Quinn (talk • it/its) 17:19, 1 August 2026 (UTC)
Pending changes protection: Persistent addition of unsourced/poorly-sourced material + sockpuppetry + vandalism. TA edits are rarely consecutive in this article. So I think it would be a good idea to put all non-autoconfirmed edits under review. Giovanni Potage (talk) 19:31, 1 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism – TA hopping vandal. at least 3 today. Jackjd0 (talk) 19:53, 1 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism. 海盐沙冰 / aka irisChronomia / Talk 04:55, 2 August 2026 (UTC)
Temporary semi-protection: Persistent sockpuppetry – Vandalism edits by TA/IP Address. Gunther : Talk 04:58, 2 August 2026 (UTC)
Temporary semi-protection, vandalism, persistent removal and distortion of the well-sourced content. Vuzorg (talk) 10:10, 2 August 2026 (UTC)
Temporary semi-protection: Persistent sockpuppetry. Peterxy（talk） 10:24, 2 August 2026 (UTC)
Temporary pending changes: Persistent disruptive editing. Entranced98 (talk) 12:01, 2 August 2026 (UTC)
- Hyderabad Disaster Response and Asset Protection Agency (edit | talk | history | links | watch | logs)
Temporary semi-protection: Persistent disruptive editing – An IP user keeps on coming with different temporary accounts and continues bolding a certain section in the lead "Enforcement Vigilance and Disaster Management Department (EV&DM)" unnecessarily. It's not per MOS:BOLD. I tried contacting them in all instances to get their inputs on this. No response has been received. Even their edit summary doesn't say anything. Requesting temporary semi protection due to the disruptive editing by a non-responsive user. Wikipicked (talk) 13:26, 2 August 2026 (UTC)
Extended confirmed protection: Persistent disruptive editing – Doing promotions with new accounts. Niasoh ❯❯❯ Wanna chat? 15:31, 2 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism. HanTsî (talk) 16:55, 2 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism. Tbhotch™ (CC BY-SA 4.0) 18:27, 2 August 2026 (UTC)
Temporary semi-protection: Persistent addition of unsourced or poorly sourced content – Repeated attempts at adding a Fandom-backed TV inclusion. In solidarity, Jalen Barks (Woof) 19:11, 2 August 2026 (UTC)
Reason: There is frequent disruption from TAs, some related to ARBPIA and some related to his nationality/ethnicity/identity Rainsage (talk) 20:29, 2 August 2026 (UTC)
Reason: Indefinite semi-protection. Persistent IP and SPA vandalism for more than a year . Some BLP violations too . WP:ARBGSCT and WP:CT/BLP apply here. V. S. Video (talk) 23:38, 2 August 2026 (UTC)
Reason: Persistent addition of negative content to an article covered under WP:BLP. Has been occurring for at least 2 years at this stage. Homeostasis07 (talk/contributions) 01:47, 3 August 2026 (UTC)
Reason: Non-constructive edits by temp accounts, see Special:Diff/1367454370, Special:Diff/1363931829, and Special:Diff/1363131690. Musashi1600 (talk) 09:31, 3 August 2026 (UTC)
Reason: High level of recent temporary account vandalism. ~2026-42834-99 (talk) 13:58, 3 August 2026 (UTC)
Temporary semi-protection: Persistent sockpuppetry – Persistent block evasion. MrOllie (talk) 14:41, 3 August 2026 (UTC)
Create protection: Repeatedly recreated – LTA hoax. –LaundryPizza03 (dc̄) 16:24, 3 August 2026 (UTC)
Reason: WP:CT/IMH pattersonuwu njz (talk) 17:23, 3 August 2026 (UTC)
Semi-protection: Persistent vandalism – Possible sockpuppets as well. –Skywatcher68 (talk) 17:36, 3 August 2026 (UTC)
Semi-protection: Disruption (including vandalism) from multiple temporary accounts. SNUGGUMS (talk / edits) 18:18, 3 August 2026 (UTC)
Semi-protection: Persistent disruptive editing. -- Alex talk 23:16, 3 August 2026 (UTC)
Reason: Temporary account vandalism in ctop aesurias (ping me in your reply, or I won't see it) (talk) 03:02, 4 August 2026 (UTC)
- Vandalism continues. aesurias (ping me in your reply, or I won't see it) (talk) 10:45, 4 August 2026 (UTC)
Semi-protection: Persistent disruptive editing – Over the past couple weeks, various TAs and newly-registered editors have been attempting to use the subject's own birthplace myth as undisputed fact. –Skywatcher68 (talk) 05:08, 4 August 2026 (UTC)
Reason: He (my brother) has died. NAQW93 (talk) 05:29, 4 August 2026 (UTC)
- (Non-administrator comment) Correction: User:NAQW93 is the page to be protected. –LaundryPizza03 (dc̄) 07:29, 4 August 2026 (UTC)
Semi-protection: Persistent sockpuppetry – Contrary to WP:NOTLIST, SPA continues to add store locations despite the registered account (Daniel Mansell (talk · contribs)) being blocked from editing live pages. –Skywatcher68 (talk) 05:50, 4 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism – Player changed his name, editors adding back the old one. Kante4 (talk) 08:02, 4 August 2026 (UTC)
Type of protection: Semi-protection (or extended confirmed protection if deemed more appropriate).
Reason: Article experiencing persistent disruptive editing from IP and newly registered account despite repeated reverts.
- https://en.wikipedia.org/wiki/Special:Contributions/~2026-38357-34
- User:Itsekiri writing (also noted at https://en.wikipedia.org/wiki/Talk:Itsekiri_people#h-Restoration_of_the_article_and_notice_regarding_disruptive_editing-20260727082700)
Article history: https://en.wikipedia.org/w/index.php?title=Yoruba_people&action=history
Dolpina (talk) 12:05, 4 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism – Protecting this due to upcoming game. Can we do this for a week?. Bryce M (talk) 12:53, 4 August 2026 (UTC)
Reason: High level of vandalism and editing traffic. Fixingthelies2025 (talk) 14:01, 4 August 2026 (UTC)
Indefinite extended confirmed protection: Arbitration enforcement – WP:CT/PIA. Isi96 (talk) 14:04, 4 August 2026 (UTC)
Extended confirmed protected indefinitely. Yue🌙 (talk) 20:27, 4 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism. In solidarity, Jalen Barks (Woof) 14:33, 4 August 2026 (UTC)
Reason: High level of temporary account vandalism - unconfirmed reports of subject's passing with vandal edits linking to a disreputable source that's potentially malware. E247G (talk) 14:41, 4 August 2026 (UTC)
Semi-protection: Persistent addition of unsourced or poorly sourced content. Dieter Lloyd Wexler 14:58, 4 August 2026 (UTC)
Indefinite template protection: High-risk template – Requesting protection for newly created talk page template. - Otherwise (Antibacklog Aktion!) (talk?) 15:05, 4 August 2026 (UTC)
Temporary semi-protection: Persistent vandalism – Edit-warring between two TAs. A war seems like it shouldn't be open for just anyone to edit. HerrHeulsuse (talk) 17:26, 4 August 2026 (UTC)
- Support upping to indefinite extended confirmed protection as this should be covered under arbitration enforcement. Netstars22 (talk to me!) 17:49, 4 August 2026 (UTC)
- Support this as well. The 2026 Iran War is explicitly restricted as part of PIA, and this is a subtopic of it that also deals with PIA issues. I'm here because I was requesting PP myself and saw someone had already requested it. It's a freaking mess in there thanks to TA's fighting each other. CoffeeCrumbs (talk) 21:36, 4 August 2026 (UTC)
Semi-protection: Persistent disruptive editing – Persistent disruption to overturn a consensus merge decision. --JBL (talk) 17:39, 4 August 2026 (UTC)
Indefinite extended-confirmed protection: Arbitration enforcement. WP:CT/PIA Netstars22 (talk to me!) 17:52, 4 August 2026 (UTC)
Declined – Pages are not protected preemptively. Page does not fall strictly under PIA. The Bushranger One ping only 22:23, 4 August 2026 (UTC)
- @The Bushranger Question/for further clarity: would this and similar articles not fall under PIA per the March 2026 clarification? Netstars22 (talk to me!) 22:43, 4 August 2026 (UTC)
- I read that as the war and articles directly about the war fall strictly under PIA/A-I, due to the involvement of Israel. Articles such as this do not strictly fall under it; they can if there is discussion about the Israeli involvment in the war, but there isn't in this case, so in the absense of direct, active disruption it falls back to normal protection policy. - The Bushranger One ping only 22:45, 4 August 2026 (UTC)
- @The Bushranger Question/for further clarity: would this and similar articles not fall under PIA per the March 2026 clarification? Netstars22 (talk to me!) 22:43, 4 August 2026 (UTC)
Temporary semi-protection: Persistent sockpuppetry. Tbhotch™ (CC BY-SA 4.0) 17:56, 4 August 2026 (UTC)
Temporary semi-protection: Persistent sockpuppetry. Tbhotch™ (CC BY-SA 4.0) 17:56, 4 August 2026 (UTC)
Indefinite semi-protection?: This article just got unprotected following a two-day full protection. However, the protection log shows that the article was actually semi-protected indefinitely before a series of disruptive page-moves caused the move protection to be upgraded, but also for the edit protection duration to be changed from indefinite to two days before getting fully protected. Given that the article continues to see vandalism even with semi-protection, and the request leading to the indefinite protection stating that it has been "going on for years", should this article have its indefinite semi-protection restored? BriDash9000 (talk) 18:00, 4 August 2026 (UTC)
- Automated comment: A request for protection/unprotection for one or more pages in this request was recently made, and was denied at some point within the last 8 days.—cyberbot ITalk to my owner:Online 18:14, 4 August 2026 (UTC)
- Automated comment: One or more pages in this request appear to already be protected. Please confirm.—cyberbot ITalk to my owner:Online 20:16, 4 August 2026 (UTC)
Already protected by administrator CoconutOctopus. Favonian (talk) 20:20, 4 August 2026 (UTC)
Reason: Persistent addition of copyrighted material by new accounts. Mellamelina (talk) 18:03, 4 August 2026 (UTC)
Indefinite full protection: requesting indefinite administrator level for this -- per filter log. Preventing further triggers or access. And also, I will not be editing that page myself. — B.J (talk) 18:04, 4 August 2026 (UTC)
- Declined – Pages are not protected preemptively. The lengthy edit filter log is evidence that the edit filter is working as intended, not that protection is needed. - The Bushranger One ping only 22:21, 4 August 2026 (UTC)
Indefinite full protection: Generic file name. Also salted on commons. ScalarFactor (talk) 20:03, 4 August 2026 (UTC)
Reason: Persistent temporary account vandalism. See also Wikipedia:Sockpuppet investigations/Lakers96 and Wikipedia:Sockpuppet investigations/Lakers96/Archive. Jacob Rampino (talk) 20:24, 4 August 2026 (UTC)
Semi-protection: Persistent disruptive editing – Consistent POV pusing from TAs that appear to be related. ButlerBlog (talk) 20:43, 4 August 2026 (UTC)
Current requests for reduction in protection level
Reason: unupdated page since June https://www.thestatesman.com/world/iran-power-struggle-erupts-as-khamenei-corners-pezeshkian-hands-irgc-chief-control-over-us-policy-report-1503624119.html https://gulfnews.com/world/mena/irans-power-struggle-is-mojtaba-khamenei-sidelining-pezeshkian-over-the-strait-of-hormuz-dispute-over-approach-to-us-1.500629776 https://www.aljazeera.com/news/2026/8/3/trump-blasts-duplicitous-iran-after-tehran-denies-it-is-in-talks-with-the-us https://www.nbcnews.com/world/iran/trump-iran-talks-attacks-canceled-hormuz-nuclear-rcna590535 https://www.theguardian.com/world/2026/aug/03/trump-meets-his-obstinate-match-in-irans-hardball-regime ~2026-42895-18 (talk) 07:08, 4 August 2026 (UTC)
- (Non-administrator comment) Unupdated is not a sufficient reason for unprotection (it's also wrong with 89 edits since June 30th). But getting back to here, you have not followed the highlighted rule above of contacting the protecting admin first (conditional on if they are still an active admin, and Daniel Case is). But that is a moot point, as any request for protection lowering on this article will be automatically declined as the article is protected under WP:CT/PIA and protection CANNOT be unprotected at any venue other than ArbCom enforcement. The article's talk page is not protected, so you may make reliably sourced edit requests there. Zinnober9 (talk) 16:46, 4 August 2026 (UTC)
- @Zinnober9: Unprotection can't even be done at Enforcement. It would require that WP:ARBPIA4#ARBPIA General Sanctions be amended to eliminate the XCR (which would in turn obsolete WP:ARBPIA5#ECP by default), which I don't see happening for the next several years at minimum. —Jéské Couriano v^_^v Look out it's Jimothy! 17:00, 4 August 2026 (UTC)
- I didn't mean to omit the WP:ARBPIA4#ARBPIA General Sanctions, but same difference, the unprotection request won't be granted here and will almost certainly be declined at all venues due to that ruling for many years to come due to that blanket protection on the topic. Zinnober9 (talk) 17:17, 4 August 2026 (UTC)
- @Zinnober9: Unprotection can't even be done at Enforcement. It would require that WP:ARBPIA4#ARBPIA General Sanctions be amended to eliminate the XCR (which would in turn obsolete WP:ARBPIA5#ECP by default), which I don't see happening for the next several years at minimum. —Jéské Couriano v^_^v Look out it's Jimothy! 17:00, 4 August 2026 (UTC)
Not done The Bushranger One ping only 22:18, 4 August 2026 (UTC)
Current requests for edits to a protected page
Handled requests
A historical archive of previous protection requests can be found at Wikipedia:Requests for page protection/Archive.