1. What we commit to
99.9% monthly availability
Measured per calendar month across the components below, excluding maintenance announced at least 48 hours in advance. 99.9% allows about 43 minutes of unavailability in a 30-day month.
We commit to a figure we are already comfortably inside rather than one that reads well. The measured record is in section 3, and it is public, so you can check that statement rather than accept it.
2. What we monitor, and how often
| Check | Frequency | What it proves |
|---|---|---|
| Component availability probes | Every 5 minutes | The website, the analytics application, the API, the webhook endpoint, the database and mail each answer independently. |
| Published customer sites | Every 5 minutes | Every site on the network, individually — not a sample, and not inferred from the platform being up. |
| Host liveness and self-heal | Every 10 minutes | A failed container is restarted without a person present. |
| Certificate and domain expiry | Daily | The most common avoidable outage is an expired certificate. This is why ours do not expire. |
3. The measured record
Read from the live monitoring tables when you loaded this page — the same source behind our public status page. It is not a figure we typed into a document.
| Component | Uptime | Checks | What it covers |
|---|---|---|---|
| Customer sites | 99.862% | 161,085 | Every published site on the network, checked every five minutes. |
| Analytics | 99.997% | 29,006 | Dashboards, reports and the numbers behind every site. |
| Database | 100.000% | 5,900 | Where analytics, accounts and billing records live. |
| 100.000% | 5,898 | Outbound mail and the inbox on every site that uses one. | |
| Website | 99.992% | 250,976 | queantic.com and every marketing page. |
| API | 99.917% | 16,924 | The REST surface your integrations call. |
| Webhooks | 99.983% | 5,992 | Payment events from Stripe. A signed request is required, so a refusal here is health. |
The status page displays a rolling 90-day window. Recorded history begins 2026-09-05, so the window is not yet full for every component — stated because "90-day history" could otherwise be read as ninety days of data, which for the newer components it is not.
4. How to verify this yourself
Go to www.queantic.com/status. There is no login, no invitation and no request form. Each component shows its current state, a day-by-day history and any recorded incident.
One detail worth knowing, because it is the difference between a status page and a status page you can trust: ours is written to a static file on every monitoring cycle, and the web server serves that file if the application is the thing that has failed. A status page that goes down with the product it reports on is worse than no status page, because it goes quiet exactly when you need it.
5. Planned maintenance
- Security patches are applied as they are released, without notice, because waiting is the greater risk. These do not take a site offline.
- Anything that could interrupt service is announced at least 48 hours in advance by email and on the status page, and scheduled outside U.S. business hours.
- Announced maintenance is excluded from the availability figure in section 1. Everything else is not.
6. Support
| Severity | Meaning | First response |
|---|---|---|
| Site down | The public site is unreachable or broken for visitors. | Within 2 hours, any day. |
| Function broken | The site is up but something on it does not work — a form, a page, a login. | Within 1 business day. |
| Question or change | A content change, a question, a request for figures. | Within 2 business days. |
Support is included in the annual fee. There is no per-ticket charge and no support tier to buy — a site we host and update is a site we answer for.
7. What we will not claim
We do not quote a recovery point or recovery time objective, because there is no automated backup schedule yet. Archives have been taken by hand. An RPO or RTO is a promise about a restore, and a promise about a restore from a backup that might be a week old is not a promise. Automating this is the top item on our security work list; the current status of it is on the security overview, and we will quote both figures the day it is true.
This document is part of Queantic's vendor packet. The rest of the packet — and the two items we supply on request rather than publish — are listed on the procurement page. Questions about anything in it: ask us directly.