Is your checkout working right now? Find out in a few minutes, free, no sign-up.Scan my store

Blog

Your uptime monitor says the store is up. Are you still selling?

Most Magento problems that cost money keep every page loading. Here is why uptime checks miss them, and what to watch instead.

An uptime monitor asks one question: does the page answer? For a Magento store that is the easy part. The problems that quietly cost money almost never take the home page down.

Problems that keep the lights on

These are the kinds of failures agencies and store teams run into again and again. Every page loads while each one happens:

  • A payment method breaks. Customers choose it, the payment never completes, and orders sit in "pending payment". The checkout page itself looks fine.
  • Cron stops. Magento runs prices, stock, search, indexes and order emails through its background jobs. When cron stops, the store keeps serving pages from the last good state, and slowly drifts out of date.
  • An index falls behind. Shoppers see old prices, or buy items you no longer have.
  • Order emails stop going out. Customers think the order failed and call, or order again.
  • Add to cart fails after a deployment. A stale full-page cache or a broken extension can stop the cart while the product page renders perfectly.

What to watch instead

If the question is "can people buy?", the checks have to follow the money:

  1. Do the purchase. Open a product, add it to the cart, reach the shipping and payment step. Stop before paying. If that works, the most important path works.
  2. Compare orders with normal. Not with yesterday, but with what is normal for this hour on this day of the week. A quiet Tuesday night is not an outage; a quiet Saturday lunchtime might be.
  3. Watch each payment method on its own. One broken method hides inside healthy totals.
  4. Watch what runs behind the scenes. Cron, failed jobs, queues, indexes and unsent emails.

Why "plain words" matters

When something breaks, the store owner needs to know three things: what happened, what it is costing, and what to do now. The developer needs different things: which step failed, what changed just before, where to look. One alert that serves both, badly, gets ignored.

This is the gap StoreOnCall is built for. You can see how it handles each of these on the what we check page, or run a free scan of your own store.

WhatsApp us