Service Availability and Recovery
Limited Availability. Vagaris and the Vagary services listed below are currently offered in Limited Availability. We do not provide a contractual uptime SLA, service credits, a committed Recovery Time Objective, or a committed Recovery Point Objective at this stage.
1. Observed availability
The figures below describe availability observed by our own external monitoring over the window stated for each service. They are historical measurements, not future commitments or contractual service levels. Each service is measured independently and the windows differ, because each monitor has its own retention; a single blended “Vagary uptime” number would obscure that.
| Service | Observed availability | Measurement window (UTC) | Samples |
|---|---|---|---|
| Index of News | 92.67% | 2026-08-05 16:07 to 2026-09-04 06:06 | 2059 |
| Vagary Voice | 95.72% | 2026-08-12 00:11 to 2026-09-04 06:06 | 1962 |
| Vagary Voice API | 92.57% | 2026-08-19 05:50 to 2026-09-04 06:04 | 417 |
Measurement source: external customer-path probes. Derived: 2026-09-04 06:06 UTC. These values are point-in-time and are not refreshed automatically by this page. Current and historical service state should be read from the live status surface rather than from a fixed percentage here. Where a figure cannot be re-derived it will be shown as measurement unavailable rather than silently retaining an old number.
2. Current recovery posture
Infrastructure snapshots currently run daily at approximately 05:00 UTC. Selected planned deployments also create a pre-change database dump. For systems whose recovery depends primarily on the daily snapshot, a qualifying recovery event may expose up to approximately twenty-four hours of data change. This describes the current snapshot interval; it is not a contractual Recovery Point Objective.
In two observed application restart events, service restoration completed in approximately twelve to fifteen minutes. This is observed restoration performance for those events. It is not a contractual Recovery Time Objective, and it should not be read as evidence of full host-loss, database-corruption, complete data-restore or regional disaster recovery within the same period — those scenarios have not yet been validated end to end as a single recovery objective.
3. Availability commitment
No contractual availability commitment currently applies to Limited Availability services. Customer-specific service levels, support coverage, recovery commitments and remedies apply only where they are expressly included in a signed agreement or order form.
Formal service commitments will be introduced only when the relevant product architecture, operating coverage, recovery testing and incident response capability can consistently support them. Customers requiring contractual availability or recovery commitments should obtain separately agreed service terms before relying on the service for critical workloads.
4. Related
Security and compliance posture is described on the Security page, and the consolidated view on the Trust Center. Live availability is published at status.vagarylabs.com.