wrenfield.example ● Production cp-40112 ● Staging cp-40113
cp-40112.hosting.example.net ↗
Current — observed live
Storage
117 MB / 30 GB
0% of your quota
Databases
0
MySQL, via phpMyAdmin
User access
0
SFTP and SSH logins
Gap observed: "Not serving" renders with the same neutral grey dot used everywhere else
in this portal. It carries no more visual weight than the storage or database cards next to it,
and the only related link — "Ask us about your data" — opens a generic support form
(
type=other), not anything about a restore. A customer landing here has no way to
tell this is the thing to act on, or what to do about it.
Proposed
!
This site isn't serving requests
We first saw this 2 hours ago. If this followed a change you made — a plugin, theme, or file edit — the fastest way back is usually restoring to just before that change.
Storage
117 MB / 30 GB
0% of your quota
Databases
0
MySQL, via phpMyAdmin
User access
0
SFTP and SSH logins
Proposed: promote "not serving" to an alert treatment with a direct path into the
restore request flow, instead of a quiet status word. "View server logs" is included because
an operator-only capability already exists (log search, in the ops portal) — a read-only,
filtered view of it for the customer is a reasonable extension, but it is not built here;
treat it as a flagged idea, not a delivered screen.
Assumed, not confirmed: "first saw this 2 hours ago" implies the platform timestamps a
status change. No such timestamp was observed in the current product — this would need a
real source (e.g. the last successful health check) before shipping copy like this.