Status, monitoring, and incident response

Status, monitoring, and incident response

How we watch the systems we run for you — and what happens when something breaks.

Monitoring

Every managed system has monitors checking it continuously: is it up, is it responding, is it behaving. You can see the current state at a glance — overall status plus each monitored component.

When something fails

1. The monitor fires — usually before a human notices.
2. An incident opens automatically and pages whoever is on call.
3. You get a plain-language notice: what is affected, what we know, what happens next.
4. Updates land as facts change; the incident closes with a short write-up of cause and fix.

Priorities

A failing monitor on a production system is an Urgent incident by default — it does not queue behind everyday tickets.

Seeing something we do not?

Open an Urgent ticket. A report from you plus a clean monitor is useful signal, not an inconvenience — monitors have blind spots, and you are often the fastest detector.

Related: Escalating a stalled ticket.