CamplaxWhere incidents are posted
Camplax posts incidents at [[address of the status page Camplax posts incidents to]]. Updates cover:
- Marketing and account sign-in, the console, and the public API.
- Project provisioning, database migration, deployment, and rollback.
- Customer apps staying up, and delivery of critical email where it is turned on.
- Known third-party-provider incidents that materially affect Camplax customers.
Incident communication
When Camplax confirms a material service incident, it posts the affected components, start time, customer impact, and the time of the next update. Updates separate what is known from what is still being investigated, and never publish secrets, personal data, or exploit details. After resolution, the record includes the end time, customer impact, the fix, and any follow-up work.
Security and privacy incidents
Camplax assesses suspected security and privacy incidents, contains and investigates them, preserves the necessary audit evidence, and notifies affected customers and authorities when applicable law or contract requires it.
Your own app’s status page
Each project can publish its own status page for its users, with uptime checks and incidents. How to turn it on is in the uptime docs.
Report a problem
If you believe a service is unavailable or your account is affected, use the Support page. For a security vulnerability, use the report form. Do not put credentials, private customer data, or exploit instructions in a public status update.