Status & Service Commitments
Operational status and what we commit to
Tricognita is in its founding-cohort phase. This page states our current service commitments honestly — the targets we hold ourselves to today and the ones still on the roadmap — plus the independently verifiable status of every dependency we run on.
Service commitments
Availability target
99.5% / moFounding-cohort availability target for the control plane. This is a target and operating practice; a contractual uptime SLA is part of enterprise agreements, not this page.
Support hours
IST business hoursFounding-team triage during business hours (IST). A formal 24/7 support SLA is on the roadmap and will replace this line when it ships — we will not claim it before it is real.
Incident response
Same business dayCritical-path incidents are acknowledged the same business day. Affected customers are notified directly by email; material incidents are also posted here.
Data-plane isolation during incidents
EnforcedYour cloud data stays in your own account; the control plane orchestrates without warehousing it. A Tricognita control-plane incident does not expose your customer data.
Dependency status
Our control-plane sub-processors (as named in the DPA). Each publishes an independent status page you can check directly.
Report an issue or request the current uptime record from your account team, or email [email protected] for security-affecting incidents.