Service status

See what matters when monitoring must stay reliable.

This page frames CashFlowCanary's critical components and how service incidents are communicated. It never publishes customer data and does not replace alerts sent to affected accounts.

Tracked components

The public status focuses on the service blocks required to operate monitoring, without exposing client stores.

Public website

Marketing pages, resources, pricing and contact form. The public website stays script-free and tracker-free.

Client cockpit

Sign-in, dashboard, incidents, reports, exports, account security and monitored sites.

Monitoring engine

Stateless checks, synthetic checkout journeys, incident detection, report anti-spam and plan cadences.

Proof delivery

PDF/CSV/JSON reports by plan, noindex proof links, transactional emails and configured alerts.

What status should prove

Status should help an agency or merchant understand whether CashFlowCanary has a service incident, which component is affected and what next update to expect. It does not publish client lists, monitored domains, alert payloads or sensitive business metrics.

Incident communication

  • A CashFlowCanary incident is described by component, impact and expected next update.
  • Affected accounts keep their dedicated cockpit or email alerts depending on configuration.
  • Client store incidents are never exposed on this public page.

Planned maintenance

Application maintenance should stay short, be announced when it can affect cockpit access or alert delivery, and remain separate from incidents detected on monitored stores.

Need a check

If you think an alert, report or proof page does not match the real state of your site, contact support with the affected site and approximate time. Do not send card data, cookies or customer cart contents.