What is actually answering, right now.
A status page is only worth reading if it can say no. This one runs its checks when you open it, reports exactly what came back, and refuses to claim a service is up until something on the other end has proven it.
Checking
Running the probes now. Nothing is reported until they answer.
This page reports three things and nothing else: whether the edge answers HTTP, whether the management API answers, and whether this website is serving. It is a reachability check run from one place. It does not measure your own origin, it does not see a rule that is challenging traffic it should be passing, and it will not notice a fault that only shows up on one route or from one network. Green here is not a promise that your site is fine.
If something is wrong and this page has not noticed, tell us. A hostname and a rough timestamp are enough to start.
Nothing here is decorative
Each row is the result of a request made when you loaded this page. If a probe times out or the endpoint answers something unexpected, the row says down or degraded. There is no default state and no way for this page to show green without a reply behind it.
It refreshes, politely
The page re-checks about every thirty seconds while you are looking at it, with a little jitter so readers do not arrive in lockstep. It stops entirely while the tab is in the background, and if the endpoint ever refuses a request it stops asking and backs off instead of retrying into a wall.
One vantage point
These probes run from the server rendering this site, not from a network of external monitors. That is enough to tell you whether the edge and the control plane are answering. It is not enough to tell you what a client in another country sees, so treat it as a first signal rather than a verdict.