Xythera
Checking
Status
Three public sites, checked from here.
This page asks xythera.org, openexus.cloud, and veloxity.si whether they answer, and it keeps asking. Below that is the availability language Separator will put in a written agreement.
Openexus
Checking
Veloxity
Checking
First check in progress
This visit
0%
The objective, drawn apart from the probes.
The cards above are this visit. The figure below is how a written agreement would talk about a month. Preview does not turn the figure into a credit.
Objective
99.9%
Of successful checks in a calendar month, after a maintenance window that was announced ahead of time. The figure applies once a written agreement names it. Preview does not create a credit.
About 172,800 checks12 misses in budget
One site, one check every fifteen seconds, thirty days. One tenth of one percent is about 173 misses. The bar above is that allowance drawn against the month. It is not the live probe.
Three ways a month can land
Inside
99.97%
On the line
99.9%
Outside
98.20%
Misses stayed inside the tenth of a percent.
Site check
Reachable
HTTP status below 500.
Decision target
Under 10 ms
The routing choice. Not this page.
Availability
01
What this page measures
Every fifteen seconds, while this page is open, the Veloxity web server requests xythera.org, openexus.cloud, and veloxity.si. A check succeeds when the site answers with an HTTP status below 500. The bars are the checks from this visit. They are not a stored month of history.
02
What an availability objective covers
Reachability of those three public sites is the measurement. It is not the time a model spends generating an answer, and it is not the illustrated latency in the site consoles. Those consoles run in the browser and do not call a model.
03
Decision time is a separate figure
Separator is designed so the routing decision itself lands in under 10 ms. That target belongs to the decision, not to generation, and not to whether a marketing site answered. A production agreement is where a customer pins the figure that will actually be measured.
04
Preview
The route API is in preview. This page does not create a credit, a penalty, or a promise of general availability. When a written agreement sets a monthly objective, the credit is calculated from that agreement. A reasonable production objective for the public sites is 99.9 percent of successful checks in a calendar month, excluding a maintenance window that was announced in advance.
05
Exclusions
A failed check does not count against the objective when the cause is outside the service: the visitor’s network, a registrar or DNS provider, or a maintenance window named ahead of time. A status below 500 that still returns a useful page counts as reachable.
06
How to read a red square
Unreachable means the probe did not get a status below 500 before it gave up, about eight seconds. The next check is independent. One miss on this page is a sample, not an incident report. Write to [email protected] if a miss repeats.
Separator
Put a typed route in front of the models you already call.
Decision
explanation
reason-1
4.2 ms