CamplaxAn independently hosted status endpoint, named owner, and on-call notification route must be configured before launch. Until that happens, this page must not be labelled “all systems operational” or presented as real-time monitoring.
What the live status service must cover
- Marketing and account sign-in, the console, and the public API.
- Project provisioning, database migration, deployment, and rollback paths.
- Customer runtime availability and delivery of critical transactional email where enabled.
- Known third-party-provider incidents that materially affect Camplax customers.
Incident communication
When Camplax confirms a material service incident, it will post the affected components, start time, customer impact, and the next planned update. Updates should distinguish facts from investigation and avoid publishing secrets, personal data, or exploit details. After resolution, the status record should include the end time, customer impact, remediation, and any follow-up work.
Security and privacy incidents
Camplax will assess suspected security and privacy incidents, contain and investigate them, preserve the necessary audit evidence, and notify affected customers and authorities when required by applicable law or contract. The final incident plan must name the incident lead, legal/privacy owner, customer-notification process, and 24/7 escalation contacts.
Report a problem
If you believe a service is unavailable or your account is affected, use the Support page. For a security vulnerability, use [[security contact email or disclosure form]]. Do not put credentials, private customer data, or exploit instructions in a public status update.