Status and uptime communications

This page defines how VeliKey communicates service health status and how uptime evidence references are published.

Service health communication

  • Service-impact notices are sent through support channels and customer account contacts.
  • Security-impact notices follow incident response escalation and communication review paths.
  • Customer inquiries on health state are routed through support@velikey.com.

Uptime evidence references

  • Deployment validation context: EC2/EKS deployment validation.
  • Operational claims are linked to reproducible evidence artifacts before publication.
  • External uptime statements require trust-claim signoff before launch messaging changes.

Launch-state disclosure

  • Public status dashboard: Not yet publicly available (launch state as of 2026-02-22).
  • Interim communication method: direct support and account-team updates for impacted customers.
  • Planned next step: publish a public status endpoint and update this page with the URL.

Next-step ownership

  • Owner: Operations Lead and Platform Engineering.
  • Reviewer: Security leadership and legal/comms approver for external wording.
  • Publishing gate: trust claims review workflow signoff.