Starting on the 8th of June, 2022, our status page will be updated automatically, bringing us closer to our goal of better communicating outage statuses with our community. The URL stackstatus.net will not change.
The SRE (Site Reliability Engineering) Team has been working behind the scenes to create tooling that allows us to better communicate with everyone during site outages. With the final bits now in place, we will be migrating our status page from a manually-updated page (powered by Tumblr) to one integrated with our incident management tool.
The status page URL will not change. We will be updating the DNS record for stackstatus.net; the new page is actually currently live at https://www.stackstatus.net.
The content from before May is still in Tumblr, just no longer behind the custom domain. If you have old URLs pointing to specific incidents prior to May of 2022, you'll need to change the domain from
stackstatus.tumblr.com (more info here).
During an incident, we will be able to update the status page from within our incident management tooling, which removes a layer of friction that we previously had. We’ve also created internal tooling that will automatically update our Twitter account, @StackStatus, within our incident management tool, which will further help us share timely updates with the community.
https://www.stackstatus.netwould redirect to
https://www.stackstatus.netto my browser it loads for a long time and eventually showing "This site can’t be reached<newline>stackstatus.net took too long to respond". (screenshot).
https://www.stackstatus.net/then I get a https everywhere message and, I too, can't load
https://www.stackstatus.net/; the connection eventually times out.