NexaGuard
  1. Enterprise-and-Legal
NexaGuard
  • Getting-Started
    • NexaGuard Developer Documentation
    • Quickstart (5 to 10 Minutes)
    • Documentation Overview
    • Concepts and Glossary
  • Compliance-and-Standards
    • Compliance Overview
    • IAB TCF v2.3 Support
    • Google Consent Mode v2 Validation
    • TCF API Validation
    • Audit Checklist (Pre-Launch)
  • Web-and-CMS-Integrations
    • NexaGuard CMP SDK – Web & GTM Setup
    • Integrate NexaGuard CMP with Webflow and Wix
    • Integrate NexaGuard CMP with WordPress
    • Integrate NexaGuard CMP with Drupal
    • Integrate NexaGuard CMP with Shopify
  • Mobile-SDKs
    • NexaGuard CMP SDK - iOS Setup
    • iOS SDK API Reference
    • NexaGuard CMP SDK - Android Setup
    • Android SDK API Reference
    • App Attribution Partner (AAP) Integrations
  • Developer-Reference
    • Web JS API Reference
    • Consent Event Schema
    • Deployment and Environments
    • NexaGuard Debug Tool
    • Troubleshooting Playbook
    • Performance and Best Practices
    • Accessibility and UX Guidelines
    • Localization Workflow
    • Migration Guide
  • Security-and-Privacy
    • Security Overview
    • Privacy Architecture
    • Data and Logging Transparency
    • Subprocessors
    • CSP and Network Allowlist
  • Enterprise-and-Legal
    • DPA and Legal Pack
    • RFP Feature Matrix
    • Status and Reliability
    • Support and Escalation
    • NexaGuard CMP SDK – Commercial Licence
  • Operations
    • Changelog and Version Policy
  1. Enterprise-and-Legal

Status and Reliability

Last updated: February 18, 2026
This page outlines NexaGuard CMP's service availability posture, operational commitments, and change management practices.

1. Service Status#

Public status page: https://status.nexaguard.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
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.
NexaGuard 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.

6. Operational References#

Support and Escalation
Deployment and Environments
Security Overview
Previous
RFP Feature Matrix
Next
Support and Escalation