@tappof - do you think having a static site in S3 as discussed on IRC would be sufficient? Would cert management etc make it easier to serve this out of mw-misc internally?

Historically we have served this record outside of our infrastructure in order to protect against outages. I don't think we need to militantly stick to this assumption given that wikimediastatus.net has been the standard status point for at least 4 years and we don't serve any content other than a redirect, but I'm open to debate on that.

@hnowlan have we already opted to keep the URL accessible? I mean, it’s (let me say) a 'redirect disclosure' from 2022… can we simply remove the endpoint?

I thought the certificate for wikimedia-static was generated via AWS ACM, but instead Let’s Encrypt was used. So we don’t have ACM already operational for wikimedia.org, and serving the ‘redirect disclosure status page’ directly from S3 will require a little extra effort (or we could serve it using plain HTTP).

Given that, my opinion is that after four years we can safely remove the endpoint. However, if it’s still needed, it might make sense to keep it hosted outside our infrastructure, mainly because I believe many users try status.example.com first.

We (observability) asked about this in the all-SRE meeting and most preferred to 301 status.wm.o -> wikimediastatus.net on the grounds that there are many Wikimedia properties using third-party tools and hosting with different privacy policies. Another option presented was to host a small static page on miscweb.

I agree that status.<site> is a common pattern for many sites, so it's probably a benefit to keep it alive in some form. Since status.wm.o is not the canonical domain, and has not been so for 4+ years, I do not think that status.wm.o requires external hosting.

I'm ok to either point the domain to the wikitech page, host the static html on miscweb, or use ncredir to 301 to wikimediastatus.net.

Let's pick one and go so we can finally retire the ancient wikitech-static host. 🎉

cwhite opened https://gitlab.wikimedia.org/repos/sre/miscweb/status.wikimedia.org/-/merge_requests/1

initial port

Change #1237524 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/deployment-charts@master] admin_ng: add status.wikimedia.org to miscweb TLS extra SANs

https://gerrit.wikimedia.org/r/1237524

The repo for this that was already created:

https://gitlab.wikimedia.org/repos/sre/miscweb/status.wikimedia.org/-/tree/main?ref_type=heads

dzahn merged https://gitlab.wikimedia.org/repos/sre/miscweb/status.wikimedia.org/-/merge_requests/1

initial port

In T414098#11591965, @Dzahn wrote:

The repo for this that was already created:

https://gitlab.wikimedia.org/repos/sre/miscweb/status.wikimedia.org/-/tree/main?ref_type=heads

Great! I just noticed the CI pipeline fails because the project has not been added to the list of trusted projects: https://gitlab.wikimedia.org/repos/releng/gitlab-trusted-runner/-/blob/main/projects.json?ref_type=heads.

hnowlan opened https://gitlab.wikimedia.org/repos/releng/gitlab-trusted-runner/-/merge_requests/144

Add status.wikimedia.org miscweb service to projects

dancy merged https://gitlab.wikimedia.org/repos/releng/gitlab-trusted-runner/-/merge_requests/144

Add status.wikimedia.org miscweb service to projects

Yay:) I was going to ask about this (comments over on gitlab) and you guys already fixed it, thanks!

publish image pipeline job worked:

docker-registry.discovery.wmnet/repos/sre/miscweb/status.wikimedia.org:2026-02-06-155121

Change #1237524 merged by jenkins-bot:

[operations/deployment-charts@master] admin_ng: add status.wikimedia.org to miscweb TLS extra SANs

https://gerrit.wikimedia.org/r/1237524

deployed cert addition to admin_ng per https://wikitech.wikimedia.org/wiki/Kubernetes/Remove_a_service#Deploy_changes_to_helmfile.d/admin_ng

Change #1240412 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/deployment-charts@master] miscweb: add release for status.wikimedia.org

https://gerrit.wikimedia.org/r/1240412

Change #1240414 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/dns@master] switch status.wikimedia.org from rackspace to wikimedia

https://gerrit.wikimedia.org/r/1240414

Change #1240416 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/puppet@production] trafficserver: add map for status.wikimedia.org to miscweb-k8s

https://gerrit.wikimedia.org/r/1240416

Change #1240417 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/puppet@production] microsites: add monitoring for status.wikimedia.org

https://gerrit.wikimedia.org/r/1240417

Change #1240420 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/puppet@production] httpbb/miscweb: add test for status.wikimedia.org

https://gerrit.wikimedia.org/r/1240420

Change #1240412 merged by jenkins-bot:

[operations/deployment-charts@master] miscweb: add release for status.wikimedia.org

https://gerrit.wikimedia.org/r/1240412

Change #1242499 had a related patch set uploaded (by Cwhite; author: Cwhite):

[operations/puppet@production] ncredir: add wikimediastatus.net funnel

https://gerrit.wikimedia.org/r/1242499

Change #1240416 merged by Dzahn:

[operations/puppet@production] trafficserver: add map for status.wikimedia.org to miscweb-k8s

https://gerrit.wikimedia.org/r/1240416

Change #1240420 merged by Dzahn:

[operations/puppet@production] httpbb/miscweb: add test for status.wikimedia.org

https://gerrit.wikimedia.org/r/1240420

Change #1247125 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/deployment-charts@master] miscweb: fix typo in image name for status release

https://gerrit.wikimedia.org/r/1247125

Change #1247125 merged by jenkins-bot:

[operations/deployment-charts@master] miscweb: fix typo in image name for status release

https://gerrit.wikimedia.org/r/1247125

The release for status.wm.org has been deployed to _staging_ on the k8s cluster within the miscweb service.

Not yet on prod but getting closer.