Matched last release check
Public website
Point-in-time routes and asset delivery in the recorded release probe.
Public status and release evidence
Current response. Exact version. Bounded evidence.
This page separates what answered now from what the last exact-version release check proved. It also shows deliberate closures and public release-verification events without turning them into invented uptime history.
Reachedthis status response, now
Matchedserving version versus release record
3complete runs for the last recorded release
0days of verified historical availability
Claim boundary
This is not uptime history or a public SLA.
A successful response proves only that this route answered this request. The recorded release checks are point-in-time evidence. Qeravio has no verified 30-day availability window, and the event list is not a complete outage history.
01 / Covered surfaces
Each component carries its own evidence scope.
A release match is not a promise that every future request will succeed.
Matched last release check
Public read-only MCP
Approved-host behavior and the declared read-only tool boundary.
Matched last release check
Existing-account sign-in entry
The public entry page and guest boundary only, not end-to-end email delivery.
Matched last release check
Public editorial feed
A bounded public response, not a freshness or completeness guarantee.
02 / Deliberate closures
Closed by decision is not an outage.
- Production billingEnabled, separate evidence required
- New account registrationEnabled, separate evidence required
- Broadcast emailIntentionally disabled
- Contact intakeIntentionally disabled
- AdvertisingIntentionally disabled
- Affiliate linksIntentionally disabled
03 / Public event record
Release evidence, with customer impact left unclaimed.
Only bounded, non-sensitive records are published here.
Release verification event
Release verification observed the previous route set
The first two post-promotion probes reached the previous serving version, where the new recovery routes did not exist. Three complete follow-up probes passed. This release-verification record does not establish customer impact.
Resolved: Customer impact was not confirmedPublic website, Release verification
Release verification event
Release verification retried after two route timeouts
The first post-promotion probe completed 51 of 54 checks after two home requests timed out and one dependent asset check could not run. Three complete follow-up probes passed. Customer impact was not confirmed.
Resolved: Customer impact was not confirmedPublic website, Release verification
Release verification event
Release verification detected a mixed asset manifest
The first post-promotion probe was rejected after one asset and one localized route returned inconsistently. Three complete follow-up probes passed. This record does not establish a customer outage.
Resolved: Customer impact was not confirmedPublic website, Release verification
04 / Exact release record
The record either matches the serving version or it does not.
- Verified Worker version
94005006-2ac6-445d-b145-a2fc818a0955- Deployment
548a3bb8-b8bf-4d5a-b6c8-7d713a7883af- Immediate rollback
0af1a5ed-02d7-4df5-8be0-c82c3df7a48d- Immutable preview
- 3 × 114/114
- Public domain
- 3 × 118/118
- Verification completed
- 5 Oct 2026, 20:24:32 UTC
- Evidence record
qeravio-guide-schema-continuation-20261005
Separate proof, separate claims