Insight4 min read

Enterprise SLA Q3: 99.99% Held Across Carrier and Energy Workloads

Quarter close: 99.99% held, fallback tested, rollbacks lineage-gated — Q3 SLA review across carrier and grid.

Technology · SLA Review · Q3 2026

Quarters end; SLAs do not. For Q3, Nervyra held 99.99% uptime across carrier orchestration (four countries) and energy dispatch workloads — on fallback routing, edge holdout and lineage-gated rollbacks, not luck. This is the receipt behind the $12M ARR deal and the November sovereign update.

Key takeaways — Q3

  • 99.99% held; fallback tested live; rollbacks replayable in minutes.
  • Latency −40% composite intact; audit-prep collapsed (see thesis).
  • Grid + telecom reuse: dispatch forecasting + congestion shaping.
  • Next: third market, edge release, cutover rehearsal.

1. The 52-minute budget: 99.99% in plain English

Four nines allow 52.6 minutes of downtime per year — per workload, all causes. Q3 spent a fraction of its quarterly share, with no single incident exceeding single-digit minutes. Brownouts (see edge holdout) and storm-season dispatch (see monsoon memo) both stayed inside budget because fallback, not heroics, absorbed them.

2. What kept it: fallback, edge, lineage, congestion

Fallback routing (multi-region) 38% of the budget defense; edge runtimes (offline-tolerant) 27%; lineage-gated rollbacks 21%; congestion models from Rimvo traffic 14% — the same split from our deal anatomy, now with a quarter of receipts. Weekly reviews tracked burn-down like cash (see cadence).

“Uptime is not a promise. It is a budget, spent in minutes, reconciled weekly.” — Nervyra, Reliability Lead

3. Exhibit: Q3 SLA spend

Figure 1. Illustrative quarterly budget vs. spend (minutes).
ItemMinutes
Quarterly share of 99.99% budget13
Actual unavailability (composite)4
Planned maintenance (hitless)9

Illustrative reconciliation; table canonical. Hitless maintenance excluded from unavailability.

Uptime99.99%
ARR base$12M
Markets4
Latency cut−40%

4. Rollbacks with receipts: lineage as safety

Every disputed inference replays exactly — prompt, retrieval, transform, approval — exported in minutes. Bad releases roll back by lineage gate, not by meeting. Carrier auditors received the same packet that won procurement; energy dispatchers received the same for tariff-relevant runs. Boring, auditable, continuous.

5. Q4: rehearsal before expansion

Third-market tenants pre-provisioned, joint edge release with the tuck-in team, cutover rehearsal under SLA credits. Expansion triggers on latency/audit/uptime — the contract, not the deck. Founders building orchestration that survives brownouts: bring logs.

Rehearsal culture: cutovers without drama

Cutover rehearsals run like fire drills: fallback paths invoked, edge holdout timed, lineage exports pulled mid-incident. Q3 spent only a fraction of its 13-minute quarterly share because rehearsal, not heroics, absorbed variance. Planned maintenance stayed hitless — excluded from unavailability by definition, included in trust by performance. The 2 a.m. review template (what failed, what fallback did, what lineage shows) is the same packet procurement received pre-sale. Boring, auditable, continuous.

Energy dispatch shares the discipline: forecast, prestage, isolate, reconcile — the monsoon memo’s 91% peak cover and 82 outage-minutes index. Telecom congestion shares it too: Rimvo rural traces shaping carrier peaks. Reliability travels because weekly rooms travel — the same cadence that cut decision latency 45% across holdings.

Expansion on triggers, not promises

Third market, joint edge release, cutover rehearsal — then expansion on latency/audit/uptime triggers written in the contract. Founders building orchestration that survives brownouts should bring fallback logs and lineage exports to the first meeting; production evidence prices best with patient buyers. While TechCrunch tracks multiples, we track merged pull requests and resolved incidents — the $200M 2026 plan funds hardening, not hype.

Buyer packet: lineage, fallback, review

Lineage exports on live workloads, fallback logs from brownouts, 2 a.m. incident reviews — the packet that won 4 countries and opened a second sovereign market. Request it via data room; vendors with decks instead should be scored accordingly. Uptime is a budget reconciled weekly; Q3 spent little of its 13 minutes because rehearsal absorbed variance. Q4 rehearses, then expands on triggers — not promises.

Drill cadence: fallback as habit

Fallback invoked, edge timed, lineage pulled mid-incident — rehearsal, not heroics, spent little of the 13-minute quarterly budget. Hitless maintenance excluded; trust included. Carrier and grid share the room; congestion and dispatch share the discipline. Rehearse, then expand.

Q4 rehearses cutovers under SLA credits, then expands on latency, audit and uptime triggers written in the contract. Founders with brownout-proof orchestration should bring fallback logs and lineage exports first — production evidence prices best with patient, weekly-governed buyers.

Energy and telecom share fallback, edge and lineage discipline — dispatch forecasting plus congestion shaping from the same weekly room. Reliability travels because cadence travels; Q4 proves it before expansion triggers fire.

FAQ

Credits paid?

None triggered in Q3; SLA credits contractual per market. Forward-looking; subject to risks.

How to diligence?

Request lineage export, fallback log, incident review template via data room.

Energy link?

Dispatch forecasting reuses carrier hardening; see Energy Transition.

Sources: SLA + incident logs Q3 (management). External links for context only.

SLA Review Published by Tilly Boddington, Director of Digital Transformation, Neyius Corporation · In conversation with Mandee Woodard, Executive Vice President, Business Affairs · Vice Chairman, Board of Directors · Reviewed by Neyius Advisors, external counsel & communications · Disclosures: Informational only; composite figures; forward-looking expansion subject to risks. · Contact · © Neyius Group. Dated Nov 10, 2026.