v4.2.0

System status

All systems affirmed.

Revocation is the critical path. Everything else — including onboarding, billing, and this status page — degrades gracefully before a safeword ever slows down.

revocation p99

0.6ms

aftercare sla

99.98%

override success

0.00%

reason fields

0

control plane components
  • Global revocation bus

    eu-lju · eu-west · us-east · ap-south

    p99 0.6msaffirmed
  • Hard-limit evaluator

    compiled into binary

    0.00% override rateimmutable
  • Heartbeat & dead-man switch

    per-session edge

    100% miss-to-revokeaffirmed
  • Aftercare SLA router

    global

    p95 4m responseaffirmed
  • Reason-field ingest

    —

    structurally absentdecommissioned

Past incidents

2026-09-14nominal

Platform admin attempted to override hard limit body:permanent

An internal operator tested an emergency-bypass flag against a hard limit in staging. The policy engine rejected the request in 0.2ms, rotated the operator's credentials, and opened a mandatory reflection ticket.

2026-06-02resolved

Misconfigured client tried to cache verbal affirmation across window boundary

A third-party integration cached affirmation:verbal for 90 minutes past window close. Server-side per-call evaluation denied all 47 calls with 401 AffirmationStale.

2026-02-19resolved

Revocation propagation regression in us-east (1.4ms)

Propagation latency briefly spiked to 1.4ms (above our 1.0ms target) during a BGP flap. No stale tokens survived; aftercare windows opened on schedule.