Queantic status
Platform
Website
queantic.com and every marketing page.
App and dashboards
Sign-in, portals, analytics and the partner console.
API
The REST surface your integrations call.
Webhooks
Payment events from Stripe. A signed request is required, so a refusal here is health.
Customer sites
Customer sites
Every published site on the network, checked every five minutes.
Infrastructure
Database
Where analytics, accounts and billing records live.
Mail delivery
Outbound mail and the inbox on every site that uses one.
How this is measured. Every component above is checked from this platform every five minutes, and each check is recorded as a pass or a failure. A check that takes longer than ten seconds counts as a failure, not a slow success. Percentages are failed checks over total checks for the window — not a guess, and never a figure derived from zero observations: a day nobody measured is drawn hatched and counts as nothing at all.
Where the older days come from. Bars marked as derived were reconstructed from web-server request logs rather than from a live probe. They are real evidence — requests served against requests that failed — but they cannot see an outage during which nobody asked for anything, so they are shown faded and counted separately.
What this page cannot tell you. It is served by the same application it reports on. If that application is down you will see a static snapshot written by the last successful check, which is at most five minutes old. If the web server itself or the machine is down, you will not reach this page at all — and neither would any status page hosted here.
Something wrong that this page says is fine? Tell us.