Live operational status for EVE production governance services. Component health is established by server-side synthetic checks — including a real governed transaction verified end‑to‑end — not by deployment state.
Everything in this block is measured across the whole service by external synthetic probes, over the audit period selected below. The per-component figures further down are separate measurements, each with its own and usually shorter recorded history — they are not the denominator for any number here.
All production governance services are operating normally.
A synthetic governed transaction is executed end‑to‑end against the production decision path each interval, and the resulting certificate is verified. This checks that EVE’s governance works — not merely that an endpoint responds.
Last verified:
Per-component scope. Each component below is a separate measurement that began being recorded on its own date, so a low “days recorded” count here describes that component's own history and does not qualify the service-wide figure above.
Deterministic policy evaluation returning ALLOW / BLOCK / MODIFY.
Policy pack 'lending_v1' evaluated two synthetic transactions.
Component availability recorded on 30 of the last 30 days.
Authority resolution and the execution gate that precedes any connector call.
Compliant transaction ALLOWED; non-compliant transaction BLOCKED.
Component availability recorded on 30 of the last 30 days.
Signed evidence certificate minted for each governed decision.
Signed decision certificate minted for the governed decision.
Component availability recorded on 30 of the last 30 days.
Offline verification of issued certificates against the published key.
Verified under ECDSA-P384-SHA384-KMS.
Component availability recorded on 30 of the last 30 days.
Durable, tamper-evident storage of decision and audit records.
Decision chain verified and continuous.
Component availability recorded on 26 of the last 30 days.
Edge gateway and public HTTP surface.
Serving requests normally.
Component availability recorded on 30 of the last 30 days.
Sign-in, session issuance, and the customer dashboard.
Session token issuance and validation verified.
Component availability recorded on 30 of the last 30 days.
Public product and API documentation.
141 documentation pages available.
Component availability recorded on 30 of the last 30 days.
No active incidents. A resolved critical incident in this period is listed below.
Started 30 Sep 2026, 00:00 UTC → Resolved 04 Oct 2026, 00:00 UTC
Started 28 Sep 2026, 01:42 UTC → Resolved 28 Sep 2026, 05:09 UTC
Every incident in the selected period is listed with its severity, when it opened, when it resolved, and how long it took — the record an auditor needs for SOC 2 CC7.3 / CC7.4, not just today’s open incidents. Availability is sampled continuously and persisted, so history survives deployments and is never back-filled.
No maintenance is currently scheduled.
| Tier | Uptime target |
|---|---|
| Standard | 99.5% |
| Enterprise | 99.9% |
| Sovereign | 99.99% |
Targets are the published commitments on the Service Level Agreement. Not every plan carries the highest tier — see pricing for the tier included with each plan.
Get notified when the status changes, an incident opens or resolves, or maintenance is scheduled.
Email: Not yet available — email delivery is not enabled for this deployment.
Status is machine-readable. All endpoints are public, read-only, and CORS-enabled.
GET /api/status/summary — full status as JSON (eve.status.v1)GET /api/status/feed.xml — Atom feed of incidents and maintenanceGET /api/status/badge.svg — embeddable status badgeGET /api/status/uptime — availability history and incident recordIf this page is unreachable: status.evecore.com serves a published snapshot from an independent origin that does not depend on EVE’s production infrastructure — so it still answers during an outage. It states how old its snapshot is and reports unknown rather than a stale reading once that snapshot passes the freshness threshold.