This page explains how Traiq deployments are run, how incidents and maintenance are communicated, and how to reach us if something looks wrong.
On our roadmap — a public status page with live checks and uptime history, fed by real monitoring. Until it exists, we won't decorate this page with a green badge no system is actually updating. A status indicator you can't trust is worse than none at all.
In the meantime, status works the way the rest of Traiq works: directly. If something affects your deployment, you hear it from us by email — and if you think something is wrong, one email gets a human looking at it.
Traiq deployments run on separate infrastructure from this marketing site. An issue with one says nothing about the other.
The platform team monitors availability and application errors, aiming to catch problems before they're widely felt — finding out from a customer email is the failure mode we design against, not the plan.
If something affects your deployment, your named contacts are told by email as soon as we have something worth telling you.
Your teams can't work. Everything else stops until service is restored, and you get updates as we go.
The system is up, but something material is broken or slow. Worked with urgency, with your contacts kept informed.
A defect with a workaround. Logged, prioritised and fixed in the course of normal releases — and you're told when it ships.
Your named contacts hear what we know, even while it's still incomplete — "still investigating" is a legitimate update; silence is what we're trying to avoid.
Progress updates while we work — what we've ruled out, what we're trying, what it means for your operation.
An incident is over when your operation says it's working — not when a chart on our side turns green.
For anything significant, affected customers can expect a short summary afterwards: what happened, what we changed, and what it means going forward.
You'll notice there are no per-severity response times printed here. We'd rather publish numbers when we can evidence them than decorate this page with promises — the commitments we do make, we keep in writing.
Maintenance is how incidents get prevented. The rule is simple: you find out before it happens, never after.
Planned work that could affect your deployment is emailed to your named contacts before it happens — with what's changing and what, if anything, you need to do.
We schedule maintenance away from your working hours wherever we can — and when we can't, we tell you why and agree the window with you rather than around you.
Email us with your company name and what you're seeing. You'll get a written reply within 24 hours — and if your operation is stopped, say so in the subject line.
