Return to Civerent
TRUST / SERVICE STATUS

Service status

Public information about confirmed customer-impacting incidents and the maturity of Civerent's status reporting.

Effective September 25, 2026

Current public notice

No active public incident notice is posted on this page. This means Civerent has not published a confirmed customer-impacting incident here; it is not a guarantee that every Civerent feature or third-party dependency is uninterrupted.

If you are experiencing a problem, contact support@civerent.com with the affected workspace, approximate time, page or feature, and a description of the behavior. Do not send passwords, payment credentials, secret keys, or unnecessary personal information.

Covered service areas

  • Public website and authenticated governance dashboard.
  • Authentication, organization access, database, and evidence workflows.
  • Stripe-hosted checkout, subscription status, billing portal, and webhook reconciliation.
  • Transactional email, inbound support routing, and Civerent live chat.

Incident communication

Civerent first validates a report, determines scope and severity, contains the issue where possible, and works toward recovery. A public notice may be posted for confirmed material service impact. Direct customer communication may also be used where required by law, contract, or the nature of the incident.

Security and privacy events follow the response and notification commitments described in applicable policies and signed customer agreements.

Maintenance and dependencies

Planned maintenance and emergency changes may affect availability. Civerent also relies on operational providers, including Netlify, Supabase, Stripe, and Resend, whose service conditions can affect Civerent features.

Provider availability is not represented as Civerent-controlled uptime. Review the Subprocessors page for the role of each provider.

Status-reporting maturity

Civerent runs a 15-minute availability check for the public website and database. Failed checks create a GitHub Actions failure for repository maintainers. This page remains manually maintained; public uptime history, incident archives, and subscriber notifications are not yet available.

Civerent intends to expand status reporting as customer volume and operational requirements grow. Until then, this page and direct support communications are the authoritative public channels for Civerent-issued service notices.

Contact Civerent

Questions and reports

Contact Civerent about this document, report a concern, or request additional information.

support@civerent.com

Do not send passwords, authentication tokens, government identification numbers, vulnerability exploit code, or other highly sensitive information by ordinary email.