Service Level Agreement

LocusVia publishes an availability commitment only from measured SLO data. The commitment currently reads pending measurement (0 resolution samples in the current window).

Availability and latency commitments are computed from the following service-level indicators:

• Resolution success rate — fraction of link resolution attempts that complete with a routing decision, over the measurement window.
• p50, p95, and p99 link-resolution latency — nearest-rank percentiles over valid latency samples in the same window; published values are measurements, never targets.

Current measured values: resolution success rate pending measurement and p50 / p95 / p99 latency no data. The current report contains 0 valid latency samples; no observed window is published while the sample count is zero.

Once the 30-day measurement window has accumulated, the monthly availability commitment equals the measured resolution success rate for the month, published on the public status page. Until then the published commitment reads "pending measurement".

• P1 — Critical — platform-wide resolution outage or data loss; 24/7 coverage with immediate response.
• P2 — High — degraded resolution performance or partial outage; response within one business hour.
• P3 — Normal — non-urgent defects and questions; response within one business day.
• P4 — Low — cosmetic or informational issues; handled on a best-effort cadence.

For enterprise agreements, service credits are the sole and exclusive remedy for availability shortfalls, computed on the monthly fixed fee, capped per the agreement, with a defined claim window and evidence process documented in the contract. Credits apply only where the measured commitment published on the status page was missed.

Live component status, measured SLIs, and the current availability commitment are published at locusvia.com/status.

Authentication, tenant isolation, data handling, cryptographic audit trails, and current assurance boundaries are documented in the security architecture.