Public status
Service health must come from live telemetry
A trustworthy status page should distinguish PRUVILO services, external dependencies, maintenance, and active incidents using monitored evidence.
Pre-launch preview — there are no live production services, public monitors, incident feed, maintenance notices, or uptime history to report.
What a future status page should show
Each statement will need a measured source and timestamp rather than a manually chosen green label.
- Customer services
- Availability of the website, authentication, deal workflows, evidence capture, and support entry points.
- Critical dependencies
- Separate, evidence-backed visibility for payment, identity, messaging, storage, delivery, and inspection dependencies where disclosure is appropriate.
- Incidents and maintenance
- Start time, affected scope, current impact, updates, recovery, and a clear distinction between planned work and an incident.
- History and accountability
- Time-stamped updates and retained incident history after the monitoring and publication process is approved.
Understand the product being prepared
Read the purpose, principles, and pre-launch limits behind PRUVILO.