Status
This page cannot tell you whether the service is up, because there is no service running for customers yet and nothing measuring it.
Current status
Not reporting. PublicViews has not launched. There is no monitoring, no incident history, and no uptime figure, so there is nothing here that would be true. A green tick on a page nobody is watching is worse than an empty page.
What this page will report
Five things, because they are the five ways this product can fail a customer, and each one will carry a number rather than a colour.
- Published pages. Whether a view resolves and how long it takes to serve. This is the one that faces your client, so it goes first.
- The scheduled check against Attio. The share of sweeps that completed cleanly, and how far behind the plan interval they ran. A page that loads while quietly being nine hours stale is a failure that a plain up or down would hide.
- Approved edits reaching Attio. Split into applied, rejected by Attio, and held back because the value had moved.
- The dashboard and sign-in.
- Email delivery, since a sign-in link that does not arrive is the same as a locked page for the person waiting on it.
What it will not do
- Publish an uptime percentage we have not measured. When there is a figure, it will carry the window it covers and the date it was taken.
- Stay green through an incident. If a published page is not serving, this page will say so while it is happening, not afterwards.
- Hide the postmortem. Anything that affected customers gets a written note here and an entry in the changelog.
If a page will not load today
Check the timestamp under the table first. Every published view carries the time we last got a clean read from Attio, and if that number is old the page will say we are having trouble reaching Attio and are retrying. A stale page still serves; we do not replace it with an error.
If a view is not resolving at all, check whether it is paused, expired, or over a plan limit in your dashboard. Then email help@publicviews.app with the view link. That reaches a person.
Some things are designed not to have a status
Published pages are never held in a shared cache, so pausing or unpublishing a view takes effect on the next request rather than propagating. And a failed check against Attio does not take a page down: the last good copy keeps serving with its own timestamp on it. Both decisions are on the security page, with the reasoning.