Post planned maintenance and write up what happened. View the public page
With your PLS Microsoft account, through auth.plsok.org. What you can do here depends on your status role: view, edit (incidents and maintenance) or admin (agents).
An old status admin token, or a personal token from auth.plsok.org/account. Held for this browser tab only, and forgotten when you close it.
While a window is open the service reads “maintenance” instead of down, opens no incidents, and is left out of the uptime figures. Leave the end time empty if you do not know it yet.
Rows judged on level of service rather than on whether patrons can use them, so they are not shown publicly — ten branches reading “degraded” for ageing outdoor access points is useful for planning and misleading to someone sitting outside using them.
For something the checks cannot see or cannot explain — a vendor fault, a planned change that went wrong, an outage people are already asking about.
Add a note as things develop, then resolve. Works on incidents the prober opened too — that is how an automatic alert gets a human explanation.
Machines inside the network that report push services. To move one onto
auth.plsok.org, make it a service token with plsauth.ps1 -NewServiceToken <label> -Roles
status:ingest -SaveAs <secret>, paste the subject it prints (svc:…) here, then point
the agent at the new secret. Its old token keeps working until it is revoked.