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 extended confirmed protection: Arbitration enforcement – Persistent disruptive editing on this page and other Ahom-related pages. Falls under WP:CT/SA, specifically WP:CT/CASTE and/or WP:CT/IMH
EDIT: User in question is the subject of a sock puppetry investigation https://en.wikipedia.org/wiki/Wikipedia:Sockpuppet_investigations/Ney_konware
Theemausoliam (talk) 05:53, 5 October 2026 (UTC)
- @Theemausoliam Isn't this article part of WP:CT/IMH and therefore requires extended-confirmed protection? GoMSTL (talk) 23:44, 6 October 2026 (UTC)
- I could see that argument, yes. One focus of the disruptive editing has been the kingdom's conflicts with the Mughals. Theemausoliam (talk) 23:46, 6 October 2026 (UTC)
- Understood. GoMSTL (talk) 00:23, 7 October 2026 (UTC)
- Updated the request accordingly. Theemausoliam (talk) 22:13, 7 October 2026 (UTC)
- Understood. GoMSTL (talk) 00:23, 7 October 2026 (UTC)
- I could see that argument, yes. One focus of the disruptive editing has been the kingdom's conflicts with the Mughals. Theemausoliam (talk) 23:46, 6 October 2026 (UTC)
Reason: Persistent disruptive editing and WP:EVASION. JimRenge (talk) 09:16, 7 October 2026 (UTC)
Indefinite pending changes: Persistent vandalism – Perennial vandalism target after a number of protections spanning several years. A few recent TA edits have, however, been constructive or at the very least made in good faith. Entranced98 (talk) 10:17, 7 October 2026 (UTC)
Temporary semi-protection: Persistent disruptive editing – recent edit-warring and clear disruptive edits by anonymous user, often unexplained. Trabzonluyuz-rumuz-elhamdulillah (talk) 10:36, 7 October 2026 (UTC)
Reason: Increased activity (for a few weeks to months now) of mostly single-purpose accounts, accounts with very few edits and single-time IP users with the specific goal of removing links to Gaza genocide article. Protection should be increased to, at least, exclude users without extended confirmed status from editing until 30 November. Impru20talk 11:09, 7 October 2026 (UTC)
Semi-protection: Unsourced claims and disruptions, such as carelessly turning a blind eye to WP:CRYSTALBALL. SNUGGUMS (talk / edits) 12:07, 7 October 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 12:18, 7 October 2026 (UTC)
Reason: Temporary semi-protection or extended confirmed protection requested. Persistent edit warring by a non-extended confirmed editor repeatedly reverting infobox cleanups (Template:Infobox company lineage parameters, MOS:NOBR, and factual studio address corrections) without engaging on the Talk page. Protection is needed to halt disruption on this breaking merger article and mandate discussion. Richardk80 (talk) 12:44, 7 October 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 12:48, 7 October 2026 (UTC)
Reason: High level of vandalism and biased materials added by a individual who has made it a habit to include Republican campaign speech and edits to demean Kulewicz and his campaign; leading to frequent rollbacks to maintain the informational integrity of the article. Current draft contains neutral language and should be protected as is. UnknownInspects (talk) 13:58, 7 October 2026 (UTC)
Declined Not sure which editor you are talking about here, but regardless all recent editors seem to be either autoconfirmed or extended-confirmed, so there isn't much that can be done on the protection side of things. Consider WP:ANI if you believe WP:POVPUSHING is an issue here. Curbon7 (talk) 21:37, 7 October 2026 (UTC)
Reason: Hello! I regret having to request protection for an article, but I am compelled to do so following attempts by several IP addresses to vandalize it. Initially, these IPs removed the reliable source cited for Poland in the opponents' table; subsequently, they inserted an unreliable English-language source containing erroneous information regarding the match statistics between Romania and Poland. It is possible that these IPs are actually correct about the extra match they keep adding, but they must provide a credible source to substantiate the changes. My understanding is that any edit on Wikipedia requires confirmation from a reliable source to avoid original research. Thank you! Patagonia41 (talk) 14:31, 7 October 2026 (UTC)
Temporary semi-protection: Persistent vandalism. Toketaatalk 15:08, 7 October 2026 (UTC)
Semi-protection: Persistent vandalism – Blocked user using temps to continue vandalism. Nswix (talk) 15:47, 7 October 2026 (UTC)
Temporary extended confirmed protection: Persistent sockpuppetry. Toketaatalk 15:56, 7 October 2026 (UTC)
Reason: IP continues violating WP:SPOILER. RamónSalamander (talk) 18:07, 7 October 2026 (UTC)
Indefinite extended confirmed protection: Arbitration enforcement – WP:CT/SA and/or WP:CT/IMH. Theemausoliam (talk) 23:29, 7 October 2026 (UTC)
Reason: Transgender woman. Under policy, transgender individuals receive blue E protection on their pages. Candidyeoman55 (talk) 23:54, 7 October 2026 (UTC)
- Declined – Pages are not protected preemptively. WP:CT/GG does not impose extended confirmed restrictions or authorize preemptive protection. As for potential semiprotection, there was some disruption earlier this week but that seems to have stopped. The Bushranger One ping only 00:09, 8 October 2026 (UTC)
Reason: There is a long-term vandal who continually removes the same content from five pages related to the Avatar films. We have blocked multiple of his accounts (and will continue to do so) but he keeps creating new accounts. We finally have pending changes protection at Stephen E. Rivkin, and it would be great if we could get that same protection at Avatar (2009 film), Avatar: The Way of Water, Avatar: Fire and Ash and David Brenner (film editor). Thanks! OrdinaryOtter (talk) 00:15, 8 October 2026 (UTC)
Semi-protection: Persistent vandalism. Filmssssssssssss (talk) 00:30, 8 October 2026 (UTC)
Semi-protected for a period of 1 year, after which the page will be automatically unprotected. Curbon7 (talk) 03:16, 8 October 2026 (UTC)
Indefinite semi-protection: Persistent vandalism – That banned user is at it again, vandalizing a U.S. state article the moment after a semi-protection expires. BriDash9000 (talk) 01:04, 8 October 2026 (UTC)
- Semi-protected for a period of 6 months, after which the page will be automatically unprotected.
One of their main goals is to cause articles to be indefinitely protected
. Curbon7 (talk) 03:21, 8 October 2026 (UTC)
Reason: Page is getting a lot of attention due to the recent attempted hijacking of Flydubai Flight 1073. This guy is a footballer and is not related to the incident, but inappropriate content has been removed numerous times over recent days. ~2026-51099-11 (talk) 01:18, 8 October 2026 (UTC)
- Semi-protected for a period of two days, after which the page will be automatically unprotected. The Bushranger One ping only 03:52, 8 October 2026 (UTC)
Semi-protection: BLP policy violations. SNUGGUMS (talk / edits) 01:25, 8 October 2026 (UTC)
Temporary semi-protection: Persistent vandalism – LTA target. Sumanuil. (talk to me) 03:32, 8 October 2026 (UTC)
Temporary semi-protection: Persistent vandalism – Unregistered user has been vandalising this page since at least July 2026. They have continued to vandalise the page despite a currently active talk page discussion. Steelkamp (talk) 03:53, 8 October 2026 (UTC)
Semi-protection: Persistent disruptive editing. SNUGGUMS (talk / edits) 04:11, 8 October 2026 (UTC)
Current requests for reduction in protection level
Reason: Protection was bumped from semi to extended confirmed in 2022 after a multi-day long vandal spree waged by a known LTA through multiple throwaway accounts. In the four years since, they are seemly inactive, with their last known account discovered on July 2023 (see Wikipedia:Sockpuppet investigations/Awolf58/Archive). With this in mind, it doesn't seem too unreasonable to give semi another wurl. Giovanni Potage (talk) 11:39, 5 October 2026 (UTC)
- Based on the disruption on that article and the time elapsed, I think it would be appropriate to downgrade to semi protect the article. It will be enough to stop new vandals and disruptors but not enough to prevent inexperienced editors to do productive changes. The sock puppeteer is user:klayclax and has moved on to other articles. Giovanni has made edits on the talk page.~2026-53576-33 (talk) 12:53, 6 October 2026 (UTC)
- Have you checked with the still-active admin who protected the page, per the above instructions? – Muboshgu (talk) 15:40, 6 October 2026 (UTC)
- @Muboshgu I requested here because @El C is only semi-active. Regardless, I'm pinging them and @Favonian (who restored the EC protection after a short full protection lasped) for their input. Giovanni Potage (talk) 18:23, 6 October 2026 (UTC)
- I don't think he meant me since I currently am not the protecting admin. El_C 18:47, 6 October 2026 (UTC)
- Right, I meant Favonian. – Muboshgu (talk) 19:37, 6 October 2026 (UTC)
Unprotection: Protected after socking in 2012, which is unlikely to be a problem again. Worth a shot. CutlassCiera 22:10, 6 October 2026 (UTC)
- Are you sure this is the right article? The protection timeline of its former title Las Vegas, Nevada tells the story of a popular vandal target that had to be repeatedly protected throughout several years, not an article that unfortunately fall victim to a dedicated sock/troll with a short shelf life. We're tried WP:TRYUNPROT with other prominent city articles in the past, and most of the time, it was evident protection was still needed. Not to mention, a not insignificant number of people still visit the article daily. (Non-administrator comment) Giovanni Potage (talk) 00:15, 7 October 2026 (UTC)
- I did misread the protection summary but I still don't think semi-protection is needed for this article. CutlassCiera 14:56, 7 October 2026 (UTC)
Unprotection: Given that on wheels vandalism requires page moves, I think that the semi edit protection can be converted to PC, this article has basically no pageviews, protected 15 years ago, and barely gets edited (50 edits in 16 years). Protecting admin is inactive. (Keep the sysop move protection though). Toketaatalk 13:17, 7 October 2026 (UTC)
Unprotection: The article is part of the series of Ronhjones' indef protections, for articles with little disruption at the time of protection. I've requested similar articles to be unprotected with similar relevance and popularity (namely Jeep, Hyundai Motor Company, Saab Automobile, or Bentley) and these have shown no major issues. Tbhotch™ (CC BY-SA 4.0) 20:57, 7 October 2026 (UTC)
Unprotection: The article is part of the series of Ronhjones' indef protections, for articles with little disruption at the time of protection. I've requested similar articles to be unprotected with similar relevance and popularity (namely Jeep, Hyundai Motor Company, Saab Automobile, or Bentley) and these have shown no major issues. Tbhotch™ (CC BY-SA 4.0) 20:58, 7 October 2026 (UTC)
Unprotection: The article is part of the series of Ronhjones' indef protections, for articles with little disruption at the time of protection. I've requested similar articles to be unprotected with similar relevance and popularity (namely Jeep, Hyundai Motor Company, Saab Automobile, or Bentley) and these have shown no major issues. Tbhotch™ (CC BY-SA 4.0) 21:00, 7 October 2026 (UTC)
Unprotection: The article is part of the series of Ronhjones' indef protections, for articles with little disruption at the time of protection. I've requested similar articles to be unprotected with similar relevance and popularity (namely Jeep, Hyundai Motor Company, Saab Automobile, or Bentley) and these have shown no major issues. Tbhotch™ (CC BY-SA 4.0) 21:00, 7 October 2026 (UTC)
Unprotection: The article is part of the series of Ronhjones' indef protections, for articles with little disruption at the time of protection. I've requested similar articles to be unprotected with similar relevance and popularity (namely Jeep, Hyundai Motor Company, Saab Automobile, or Bentley) and these have shown no major issues. Tbhotch™ (CC BY-SA 4.0) 21:03, 7 October 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.