Availability commitment and service credits
Uptime target and formula, definition and measurement of downtime, exclusions, service-credit schedule and claim window. No service-level agreement is in force; the prerequisites for the commitment to bind, and the reason no historical uptime figure is published, are set out below.
Your use of AtlasVector is governed by the Terms of Use, which provide the Service as is, do not warrant that it will be uninterrupted, and cap total liability at the greater of what you have paid us or US$100. Nothing on this page changes that. It becomes a commitment only when a signed agreement incorporates it — see negotiated terms below.
The browser requests the public API liveness route every 30 seconds and reports the result for this tab, from the time it was opened. No history is retained, the count resets on reload, and the result says nothing about any prior month: it is not a Monthly Uptime Percentage and no percentage is derived from it.
30-day uptime is not measured; the figure is unavailable until a continuous probe with retained history (see the prerequisites below) has run for a full month.
| Term | Definition |
|---|---|
| Monthly Uptime Percentage target | 99.9% of each calendar month, measured in UTC. |
| What that allows | Roughly 43 minutes of downtime in a 30-day month — the exact allowance per month length is in the table below. |
| Covered Service | The public portal API and the authenticated platform API. Availability means the service accepted and answered requests — it is not a claim about the correctness of any figure those requests return. |
| Downtime | A whole clock minute in which the majority of probe requests to the Covered Service fail or exceed a 10-second timeout. Partial minutes are counted as full minutes against us. |
| Measurement | An external probe outside our own infrastructure, at least one request per minute from at least two regions, with the raw minute-by-minute series retained and available on request. |
| Incident notice | When an incident makes the Covered Service unusable: a first notice to the address on your account within 1 hour of us confirming it, an update at least every 4 hours until it is resolved, and a written post-incident review within 5 business days. |
| Remedy | Service credits, on the schedule below, are the sole and exclusive remedy for failing the target. |
| Claim window | A credit is requested in writing within 30 days of the end of the affected month, and is applied against the next charge or invoice on the account — never paid in cash. |
| Month length | Total minutes | Downtime allowed at 99.9% |
|---|---|---|
| 28 days | 40,320 min | 40m 19s |
| 30 days | 43,200 min | 43m 12s |
| 31 days | 44,640 min | 44m 38s |
99.9% is the target to be held to under a signed agreement, not a measured result. No uptime series is retained, so no Monthly Uptime Percentage is available for any prior month.
Exclusions are limited to the following.
- Maintenance announced at least 48 hours ahead and confined to a published window, capped at 60 minutes in any month.
- Emergency maintenance to close a security defect, where waiting for the notice window would leave users exposed.
- Anything between your device and us that we do not run — your network, your ISP, your DNS resolver, your browser, or a corporate proxy.
- An outage at a third-party market-data source. Affected figures are shown as unavailable while the Service continues to answer requests; that state is not counted as downtime.
- Events outside our reasonable control: a cloud region-wide failure, a network-transit failure between providers, war, natural disaster.
- Suspension or termination under the Terms of Use — a breach, or a risk of harm to the Service or other users.
- Any feature labelled preview or in the pipeline, and any use of the Service outside a plan that carries this commitment.
| Monthly Uptime Percentage | Credit |
|---|---|
| Below 99.9%, at or above 99.0% | 10% of that month’s fee |
| Below 99.0%, at or above 95.0% | 25% of that month’s fee |
| Below 95.0% | 50% of that month’s fee |
The fee is the subscription charge for the affected month at the published list price; each credit is the stated percentage of that charge, applied against the next charge on the account. The list price is on the pricing page.
Fee and billing terms on this deployment, to which the credit schedule applies.
| Term | Provision |
|---|---|
| Fee | The subscription charge for the affected calendar month, at the list price published on the pricing page. A subscription is billed by card checkout for each monthly term in advance and renews automatically at the end of each term until it is ended; the checkout runs on the payment processor’s own pages, and AtlasVector does not hold card details. |
| Credit application | A service credit is the stated percentage of that charge, applied against the next charge on the same account. It is never paid in cash and is not transferable to another account. |
| Ending a subscription | A subscription may be ended at any time by written notice to the published mailbox. No further charge is taken once it has ended; the workspace closes to the account at the end of the paid term, and the public portal remains open to it without a subscription. |
| Refunds | No refund right arises from this page. The service credit above is the sole remedy for failing the target; any right held under applicable consumer law is unaffected. |
The published Terms of Use are consumer terms, not an institutional agreement: an as-is Service and a US$100 liability ceiling. A master agreement — with a negotiated liability cap, this service level attached and binding, a security schedule, a data-processing agreement and a defined exit and data-return procedure — is available on request. No negotiated agreement has been executed to date; no procurement process or minimum subscription count applies. Requests go to [email protected].
Four prerequisites must be met before this commitment binds. No target date is committed for any of them.
| Prerequisite | Status | Detail |
|---|---|---|
| A continuous availability probe with a retained history | Not in place | The API exposes a liveness route that answers one request at a time and retains nothing. No uptime series is retained, so no Monthly Uptime Percentage exists for any month and none is published. |
| A public status page and incident history | Partly in place | A status page at /status reports which components currently answer, probed from the visitor’s browser. No history is retained: there is no incident log and no monthly uptime figure. |
| A paid plan for a credit to apply against | In place | Subscription fees are collected by card checkout at the list price published on the pricing page. The fees and billing section states the charge, how a credit applies and how a subscription ends. |
| A signed agreement that incorporates this commitment | Not in place | Until one exists, the Terms of Use are the whole contract, and they warrant nothing about uptime. |
Related documents: the sub-processor register and the data-processing agreement are described in section 4 of the privacy policy and sent on request; feed-by-feed provenance and freshness is on data sources. No SOC 2 attestation and no third-party penetration-test report exist; the compliance program is listed in the pipeline on the platform page. Other requests: [email protected].