All public surfaces, with their service-level objectives.
Civic Anchor is in a supervised pilot phase. The service-level objectives below describe the operational targets for contracted production traffic; pilot traffic is best-effort unless a partner agreement states otherwise.
All systems operational
Last checked: Tue, 16 Jun 2026 07:20:55 GMT · region cpt1
Public surfaces
| Hostname | Purpose | Scope | Status |
|---|---|---|---|
| civicanchor.id | Public DID resolver | Public · Pre-GA | — |
| civicanchor.me | User wallet PWA | Public · Pre-GA | — |
| civicanchor.co.za | ZA country marketing + Trust + Status | Public · Pre-GA | — |
| agents.civicanchor.id | Partner verification API | Partner only | Operational |
Service-level objectives
Targets the platform commits to for contracted production traffic. Measurement window: rolling 30 days. Failure to meet a published SLO over two consecutive months triggers a customer-visible post-mortem.
- Public DID resolver99.9% monthly · ≤ 200ms p95 SSR
- Verification API (per-region)99.95% monthly · ≤ 250ms p95
- Wallet PWA99.9% monthly
- Country marketing surfaces99.9% monthly · ISR-served
Incident disclosure
Confirmed incidents are posted here within 72 hours, with a full post-mortem (timeline, root cause, mitigation) within 14 days. POPIA s22 notifications run in parallel where the incident reaches the threshold. See the Trust Centre for the full disclosure policy.
Incident history
Published disclosures and post-mortems from the incident workflow.
No confirmed security incidents have been published.
This list is populated from the incident-disclosure system of record.
Reporting a vulnerability
Coordinated disclosure: write to security@civicanchor.africa with a description, reproduction steps, and your preferred acknowledgement. We respond within one business day. Critical findings are eligible for a recognition fee once the public bug-bounty programme opens.