A status page has a blind spot.
It can tell you that your API is returning 502s. It can tell you that a TCP port stopped accepting connections. It can tell you when the incident started.
It usually cannot tell you why.
Was the application host out of memory? Was disk I/O saturated? Did load climb for 40 minutes before users noticed? Was the server completely healthy and the real problem somewhere else?
Those answers often live in a separate monitoring product, disconnected from the incident timeline and disconnected from the status page.
