Nexiv Labs is now operating six divisions across healthcare, veterinary, commerce and infrastructure. See the group →
System status

Platform health at a glance

Availability, latency and incident history across every Nexiv division and the shared services beneath them.

All systems operational

No active incidents across any division or shared service.

Operational
30-day availability
99.98%
Above 99.9% target
API latency p95
184 ms
Within 300 ms objective
Open incidents
0
None active
Last DR exercise
Q2
RTO met
API latency · rolling
Region traffic
Components

Service-by-service status

ServiceDivisionStatus30-day availabilityp95 latency
Consultation platformNexiv Health Operational99.99%142 ms
Real-time media (WebRTC)Nexiv Health / Vet Operational99.97%—
Triage queueNexiv Vet Operational99.98%118 ms
Marketplace & checkoutNexiv Pets Operational99.98%203 ms
Payments & escrowShared Operational99.99%167 ms
Identity & SSOShared Operational100.00%61 ms
NotificationsShared Operational99.96%94 ms
Anchoring serviceNexiv Chain Operational99.95%—
Kubernetes platformNexiv Cloud Operational99.99%—
Public website & CDNGroup Operational100.00%28 ms

About this page. This is a published summary view, not a live telemetry feed — figures are updated from our monitoring platform and the charts above are illustrative of typical behaviour. Customers under a support agreement receive incident notifications directly and can request raw SLO reporting for their own tenant.

Recent history

Incident log

Every Severity 1 and 2 incident gets a written post-incident review shared with affected customers. Here is the shape of what that looks like.

  • SEV 3 · RESOLVED
    Elevated notification latency

    Transactional email delivery delayed by up to 8 minutes for approximately 40 minutes, caused by a downstream provider queue backlog. No messages were lost. Mitigated by failing over to the secondary sending route; provider routing now health-checked continuously.

  • SEV 3 · RESOLVED
    Marketplace search degradation

    Search results returned slowly for a subset of category filters following an index rebuild. Read traffic was served from the previous index while the rebuild completed. Index rebuilds now run blue/green rather than in place.

  • SEV 2 · RESOLVED
    Regional API error rate spike

    A deployment introduced a connection-pool regression, raising the error rate in one region. Automated rollback triggered on error-budget burn within 4 minutes and service recovered without manual intervention. Pool sizing is now covered by a load test in the release gate.

Incident severity definitions and response targets are set out in the Service Level Agreement.

Objectives
  • Availability99.9% monthly, measured per tenant as successful requests over total
  • Latencyp95 under 300 ms server-side, excluding media streams
  • RPO≤ 5 minutes point-in-time recovery
  • RTO≤ 60 minutes region failover, exercised quarterly
  • Change failureUnder 5% of deploys requiring rollback or hotfix
Get notified
  • CustomersIncident notifications are sent to your registered technical contacts automatically.
  • Everyone elseEmail support@nexivlabs.com to be added to the status distribution list.
  • UrgentCall +1 (323) 289-0039 during UK business hours.