GhostClick · Guide

Platform Status Watch

When Shopify or Cloudflare has a bad day, find out what it means for your checkout — without asking.

What You're Trying to Do

Orders go quiet. Someone in a forum says Shopify is down. Now you have a question you can't answer from a status page: is it them, or is it me? A status page tells you a platform is having an incident. It can't tell you whether your checkout still works.

That's the gap this fills. GhostClick already drives real journeys through your store, so when a platform admits to an incident it can go and check your store and tell you what the incident actually means for you.

How It Works

Every five minutes GhostClick reads the public Shopify and Cloudflare status feeds. Nothing is asked of you and nothing is installed — it's a plain read of the same feeds you'd open yourself.

When an incident turns up that could plausibly affect storefronts or checkout — the impact is real, and an affected component is something like checkout, storefront, payments, CDN or DNS — every connected store gets one health check run against its own site. Incidents that can't touch a storefront are still recorded; they just don't trigger anything.

Status

Shopify · Checkout errors

identified

Last check on your store: passed 14:40

Where You See It

  • A banner on your dashboard for each open incident that could affect you, with its current status and what your last check found
  • The Status page in the app, which lists the incidents being watched and the checks each one triggered on your store
  • An alert, if the journey it used has alerts set up — see Alerts

The alert goes out whether the check passed or failed, because "Shopify is reporting checkout errors and your checkout still works end to end" is usually the more valuable of the two answers.

What It Costs You

Nothing. These runs never touch your monthly audit credits — the same rule as scheduled monitoring. GhostClick started the run, not you.

Info

A health check re-uses one of your saved journeys, so a store with no saved journey has nothing to run and is skipped. If you want this to work, save at least one journey that goes through checkout — see Journeys & monitoring.

How Often It Fires

A single incident won't flood you. Checks are triggered when an incident is new or when its status moves on — investigating, identified, monitoring — and then not again for six hours, with a cap of one run per store per incident. A chatty incident costs you one round of checks, not ten.

The Point

You shouldn't have to notice the outage, find the status page, and then go and test your own checkout by hand. The answer to "is it them or me" should already be waiting for you — with evidence from your own store, not from a platform's summary of its own week.