Hello, I can't seem to log into Wikimedia sites, including Phabricator. I'm getting this message:
"The database is currently locked to new entries and other modifications, probably for routine database maintenance, after which it will be back to normal.
"The system administrator who locked it offered this explanation: The wikis are currently read-only"
I don't see any announcement of a planned activity that would block logins. And I tried to log in with 2 different web browsers.
Pine🌲
Hello Pine,
Please see https://www.wikimediastatus.net/incidents/z7qjmqtrh8yq
Greg
On Thu, Mar 5, 2026 at 7:54 AM Pine W via Wikitech-l < wikitech-l@lists.wikimedia.org> wrote:
Hello, I can't seem to log into Wikimedia sites, including Phabricator. I'm getting this message:
"The database is currently locked to new entries and other modifications, probably for routine database maintenance, after which it will be back to normal.
"The system administrator who locked it offered this explanation: The wikis are currently read-only"
I don't see any announcement of a planned activity that would block logins. And I tried to log in with 2 different web browsers.
Pine🌲 _______________________________________________ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-leave@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
The issue is known and is currently being addressed: https://phabricator.wikimedia.org/T419143#11678144
Neriah
בתאריך יום ה׳, 5 במרץ 2026 ב-18:05 מאת Greg Grossmeier via Wikitech-l < wikitech-l@lists.wikimedia.org>:
Hello Pine,
Please see https://www.wikimediastatus.net/incidents/z7qjmqtrh8yq
Greg
On Thu, Mar 5, 2026 at 7:54 AM Pine W via Wikitech-l < wikitech-l@lists.wikimedia.org> wrote:
Hello, I can't seem to log into Wikimedia sites, including Phabricator. I'm getting this message:
"The database is currently locked to new entries and other modifications, probably for routine database maintenance, after which it will be back to normal.
"The system administrator who locked it offered this explanation: The wikis are currently read-only"
I don't see any announcement of a planned activity that would block logins. And I tried to log in with 2 different web browsers.
Pine🌲 _______________________________________________ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-leave@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-leave@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
My common.js stopped running, and I think it happened after the DB unlocking. May there be any connection?
Yes, user javascript was temporarily disabled.
-- Brian
On Thursday, 5 March 2026, Bináris via Wikitech-l < wikitech-l@lists.wikimedia.org> wrote:
My common.js stopped running, and I think it happened after the DB unlocking. May there be any connection?
Thanks to those who responded to the incident. An after-action report would be interesting to read, including the root cause analysis & how the response happened, preferably without providing a roadmap for bad actors. Perhaps the report could be posted on https://diff.wikimedia.org/. I'd understand if assembling the report takes a few days & is published next week.
Thanks, Pine🌲
On Thu, Mar 5, 2026 at 1:31 PM Brian Wolff via Wikitech-l < wikitech-l@lists.wikimedia.org> wrote:
Yes, user javascript was temporarily disabled.
-- Brian
On Thursday, 5 March 2026, Bináris via Wikitech-l < wikitech-l@lists.wikimedia.org> wrote:
My common.js stopped running, and I think it happened after the DB unlocking. May there be any connection?
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-leave@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
The incident was at the top of hn, with comments (correctly) describing exactly what happened. I think the ship has sailed on any sort of WP:BEANS concerns.
-- Brian
On Thu, Mar 5, 2026 at 5:25 PM Pine W via Wikitech-l < wikitech-l@lists.wikimedia.org> wrote:
Thanks to those who responded to the incident. An after-action report would be interesting to read, including the root cause analysis & how the response happened, preferably without providing a roadmap for bad actors. Perhaps the report could be posted on https://diff.wikimedia.org/. I'd understand if assembling the report takes a few days & is published next week.
Thanks, Pine🌲
On Thu, Mar 5, 2026 at 1:31 PM Brian Wolff via Wikitech-l < wikitech-l@lists.wikimedia.org> wrote:
Yes, user javascript was temporarily disabled.
-- Brian
On Thursday, 5 March 2026, Bináris via Wikitech-l < wikitech-l@lists.wikimedia.org> wrote:
My common.js stopped running, and I think it happened after the DB unlocking. May there be any connection?
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-leave@lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-leave@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
On Thu, 2026-03-05 at 17:24 -0800, Pine W via Wikitech-l wrote:
Thanks to those who responded to the incident. An after-action report would be interesting to read
https://meta.wikimedia.org/wiki/Wikimedia_Foundation/Product_and_Technology/...
andre
wikitech-l@lists.wikimedia.org