Status and Reliability

Last updated: July 1, 2026

This page outlines Cybexo CMP’s service availability posture, operational commitments, and change management practices.

1. Service Status

Public status page: https://status.cybexo.com
Incident history: available via the public status page, including historical uptime and resolved incidents.

The status page reflects real-time system health across:

CMP loader delivery
API endpoints
Pulse public scanner
consent storage services
dashboard services

Major incidents and scheduled maintenance events are documented publicly.

2. Availability Commitments

Target availability (SLO): 99.9% monthly uptime
Measurement window: monthly
This target is operational guidance and not a contractual SLA unless explicitly stated in a signed agreement.

Availability is calculated based on public API and loader endpoint responsiveness, excluding:

scheduled maintenance windows
force majeure events
customer-side integration errors
third-party platform outages (for example Google, Shopify, and CMS providers)

3. Maintenance Policy

Planned maintenance notice period: at least 48 hours in advance when service impact is expected.
Maintenance communication channel: public status page plus email notification for affected customers where applicable.

Routine updates that do not impact service availability may be deployed without prior notice.

4. Change Notification

Release updates are documented in the Changelog.
Major feature releases and compliance updates are announced via:
- changelog
- dashboard notifications (where applicable)
- email announcements for material updates
Breaking changes are explicitly documented in the changelog and announced in advance where feasible.

Cybexo follows semantic versioning principles for SDKs and public APIs.

5. Operational Practices

Production and non-production environments are logically separated.
Monitoring and alerting are configured for key system components.
Critical production issues are triaged according to internal severity classification guidelines.
Infrastructure updates are deployed using controlled release processes.

Key public checks include:

https://cmp.cybexo.com/loader.js
https://pulse.cybexo.com/
https://pulse.cybexo.com/v2/public-scan/healthz
https://api.cybexo.io/v2/public-scan/healthz

Browser-based public scanner traffic should use pulse.cybexo.com. The api.cybexo.io public scanner route is maintained for compatibility and API clients.