This is similar to multiple other feature requests. However, those requests focus mainly on how the page isn’t automatically updated, which is not the point of this feature-request.
As a Roblox developer, it is currently too hard to determine the impact of an outage on my Roblox experiences. As of right now, we have multiple different ‘components’ as well as ‘locations’ to help us determine whether our experiences may or may not be affected by an outage. So let’s look at this page during an outage and reflect:
Oh my! An outage, I better scroll down to see if my experience is affected!
“That must be a pretty severe game join issue to the point that it apparently affects not only the ‘game join’ location but also the ‘asset delivery’, ‘data store’, ‘talent’, ‘documentation’, and ‘forum’ locations!!!”
Obviously, looking at the above screenshot these ‘locations’ are obviously not all affected and in-theory, if it is just a ‘game-join issue’ only the ‘game-join’ option should be marked as ‘service disruption’. However, all of them are set as ‘service disruption’, making the issue look way worse at a glance.
Now, you may be assuming that Roblox simply doesn’t know what is affected. Look, they eventually changed the statuses to be more granular!
However, the issue is that most developers will be checking the status site immediately when they see Roblox starting to crumble, not 30 minutes later when Roblox has had time to investigate further and implement ‘more granular’ statuses (assuming they even do that, most past incidents never received this treatment).
If this is truly the case and Roblox simply isn’t aware of the impact, there needs to be a way for developers to know that certain aspects have not yet been confirmed to be affected and that the team is still investigating so that we can wait for an official update at a later time rather than panicing about our game dying due to everything being down.
I also just wish to comment on the above ‘granular status change’. This creates more confusion, “why is ‘avatar’ down if it’s just a game-join issue?”, for example. There is no explanation on why each location is affected and, therefore, no way for developers to temporarily mitigate issues, if even applicable.
If Roblox is able to address this issue, it would improve my development experience because I would be able to determine an outage’s impact on my Roblox experience at a glance without having to experiment myself.