Service status page

The status page shows whether CampaignHQ's key systems are healthy, so customers can check it during an outage or maintenance window instead of waiting to hear back.

What it shows

• Overall status — operational, degraded, or down (worst component wins).
• Components — API, funnel pages, checkout & payments, email & automations — each with its current state and when it was last checked.
• Incidents — a timeline of current and recent issues with updates.

The public status data is available at /status.json (also used by external monitors).

How status stays accurate (auto-probes)

Component status is set automatically by health probes that check each system on a schedule: a system that fails a check is marked down; one that responds slowly (above the latency threshold) is marked degraded. When a probe trips a component, the page auto-opens an incident — so the status is right before customers call in — and auto-resolves it when the system recovers. This avoids the classic "status page says green while everything's on fire" problem.

For platform admins

Admins can:

• Post and update incidents manually (investigating → identified → monitoring → resolved).
• Pin a manual status on a component (overrides the probe, e.g. during planned maintenance).
• Status changes and incidents email subscribers automatically.

Customers can subscribe to status updates by email from the status page.

Maintenance windows

Planned maintenance is announced via the platform announcements banner (admin → Announcements → "Scheduled maintenance" template), where the date/time fill in from pickers automatically. See the announcement tooling for details.