A more accessible status page

During the last lichess outage there was a notification that the status of Lichess could be found on X.com or Discord.
However as I don't have an account for either I found it difficult to review the status.

For x.com it actually seemed like everything was fine (it showed some normal posts, and even after scrolling quite a bit I did not see anything about an outage).

Discord first suggested I could easily view the channel, but then 'there is something unusual about my signup' (perhaps a lot of people wanting to check the channel suddenly during an outage...), so it requested me to put in my phone number which I would not like to do.

In the end I ended up on some reddit post where someone had found a message on X.com and copied it there so I had some understanding of what to expect, but this did prompt me to make this suggestion.

sitechecker.pro/
www.virustotal.com/gui/home/upload/
however as many believe a 200 html must be inspected as there was no maintenance announced prior.
F12 or right click mouse Inspect page, click console, out click the arrows in the CSS code.
www.reddit.com/r/selfhosted/comments/mi7pi4/down_detector_for_home/?rdt=60478/ uptimerobot.com/
CURL command,
$: curl example.com > not a good way.
Amongst various others answers are on the net, there are many site's to see.

Just to clarify, the challenge does not seem to be about just detection (when I went to the site it properly showed a page showing that it was down and where I could find info).

The point is that the two places where info could be found were not very accessible, and me and others ended up on something like reddit for understanding what may be expected because someone with no relation to the site happened to have posted it there.

I found the Lichess updates on Mastadon. They probably are copies of what Twitter has. But Mastadon presented them in chronological order, so the useful outage notices were all at the top.

Given that Lichess was directing us to Twitter instead of X, I suspect the placeholder page was written a long time ago, and not thought about much afterward. I bet at the time, Twitter messages were chronological, too.

FWIW, the issue with X presenting tweets in non-chronological order may be an issue of using X without being logged into an account. I noticed the same thing. After signing in, the tweets appeared as expected with latest updates at the top.

@MentalFugues said in #5:
> may be an issue of using X without being logged into an account
And that's the problem. Not everyone wants to have accounts on all currently popular social networks and some of them go quite far in showing people who just followed a link that they are not welcome until they create an account.