Discuss Scratch
- Discussion Forums
- » Suggestions
- » Public status/outage page
- Zro716
-
1000+ posts
Public status/outage page
As there is an outage affecting messages/comments at the moment, I would like to see if Scratch has a status page for these sort of things. Similar to what Discord has here. This would be extremely useful for live monitoring of anomalies in traffic and site health, as well as a formal place for the ST to give the heads-up about concurrent problems and maintenance. This is different from the statistics page.
As things are now, when site problems arise, only a portion of the affected users go here to complain, which is later acknowledged by the ST. This ritual is far too slow and inefficient while leaving many others without a clue of what's going on until the site goes down for fixing. Even then, there isn't much information to go on – the ST's twitter is rarely used, and sometimes doesn't even display. Us users deserve to know what's going on, how bad it is, and to get an idea of how long we need to wait. It could save the ST from the headache of having the site bombarded with constant refreshes from thousands of users, thus stalling the site from restoring.
With the status page made public, it can notify users of outages, network events, and other cool tidbits like live request rates. The ST can immediately announce issues to all its users (not just the ones on the forums) before the site has to be taken down. As with any status page, users can subscribe to the RSS feed and receive news about these events even before they go onto Scratch. If the site does go down, parts of the status page can be integrated with the “site is down” redirect, thus giving more useful information about what's happening than a vain “oopsie”.
In addition, the status page would provide a history log of network problems. That way, after an issue is resolved, users can look back on the page and find out what happened and for how long, without having to ask around and receive vague answers. It can serve useful info about patterns arising in the network, possible inadequacies, traffic congestion, server overloading, etc. to network admins and just curious users.
As things are now, when site problems arise, only a portion of the affected users go here to complain, which is later acknowledged by the ST. This ritual is far too slow and inefficient while leaving many others without a clue of what's going on until the site goes down for fixing. Even then, there isn't much information to go on – the ST's twitter is rarely used, and sometimes doesn't even display. Us users deserve to know what's going on, how bad it is, and to get an idea of how long we need to wait. It could save the ST from the headache of having the site bombarded with constant refreshes from thousands of users, thus stalling the site from restoring.
With the status page made public, it can notify users of outages, network events, and other cool tidbits like live request rates. The ST can immediately announce issues to all its users (not just the ones on the forums) before the site has to be taken down. As with any status page, users can subscribe to the RSS feed and receive news about these events even before they go onto Scratch. If the site does go down, parts of the status page can be integrated with the “site is down” redirect, thus giving more useful information about what's happening than a vain “oopsie”.
In addition, the status page would provide a history log of network problems. That way, after an issue is resolved, users can look back on the page and find out what happened and for how long, without having to ask around and receive vague answers. It can serve useful info about patterns arising in the network, possible inadequacies, traffic congestion, server overloading, etc. to network admins and just curious users.
- Scratch_Foxy_Rogues
-
100+ posts
Public status/outage page
Support, this would be quite useful
- 54329
-
500+ posts
Public status/outage page
Semi Support
I don’t feel that this is a completely urgent matter to be added in, but I will say that it looks quite useful. I can definitely agree that an “oopsie poopsie” page isn’t as helpful to people viewing the website as a fairly detailed report of what exactly is wrong.
I don’t feel that this is a completely urgent matter to be added in, but I will say that it looks quite useful. I can definitely agree that an “oopsie poopsie” page isn’t as helpful to people viewing the website as a fairly detailed report of what exactly is wrong.
- CatsUnited
-
1000+ posts
Public status/outage page
Support because while it's not something critically important, it sounds cool.
- Luvexina
-
500+ posts
Public status/outage page
Support! This can help people understand what is wrong and an estimate of how long it will take.
no this is not a necropost
no this is not a necropost
- LuckyLucky7
-
1000+ posts
Public status/outage page
Support. Usually when details about a server outage are not specific enough, users tend to post on the uploads.scratch.mit.edu forums.
On a side note, a server outage has recently occurred in the forums this month(and users were posting on the uploads forums, and I was one of them because I was bored and wanted to post on the forums).
On a side note, a server outage has recently occurred in the forums this month(and users were posting on the uploads forums, and I was one of them because I was bored and wanted to post on the forums).
- boobose1
-
5 posts
Public status/outage page
Scratch is down, the scratch database is down as if May 2, 2025
- RoboNinja4067
-
58 posts
Public status/outage page
That's, uh… quite the necropost. But still, support.
- Discussion Forums
- » Suggestions
-
» Public status/outage page