Skip to main content

Shopify Store Down? How to Tell If It's Shopify or Your Store

Shopify store down while Shopify's status page is green? Find whether it's the platform, your domain, your theme, or private mode, and how to hear first.

FLAREWARDEN
FlareWarden Team
7 min read

Check shopifystatus.com first, then don’t trust a green page too far. Shopify’s own status page carries a line at the bottom saying that some issues affecting a small percentage of stores may not be reflected there. So a green dashboard rules out a platform-wide outage. It doesn’t rule out a problem with your store, and most Shopify store down reports turn out to be one layer above the platform.

Step One: Is Shopify Itself Having a Bad Day?

Open shopifystatus.com. It lists components separately, which matters more than the headline: Admin, Checkout, Reports and Dashboards, Storefront, API & Mobile, Third party services, Support, Point of Sale, and Oxygen (as of October 2026). A Checkout incident with a green Storefront explains a store that loads but can’t take payments.

The same page links to My Shopify Status, a store-specific view. If the public page is green, look there next, since that’s where an issue affecting only some stores is more likely to appear.

If both are green, assume the problem is in your layer and work through the next section. That’s the more common case, and the one where waiting for Shopify to fix it means waiting forever.

Step Two: Four Comparisons That Find the Broken Layer

Each of these takes under a minute and splits the problem in half.

1. Your domain vs your myshopify.com address. Every store also answers at your-store.myshopify.com. If that loads and yourstore.com doesn’t, the store is fine and the domain connection is broken. Shopify’s manual domain connection guide lists what the records should be: an A record pointing to 23.227.38.65 by default (Shopify notes it may offer a different address for your region), and a www CNAME pointing to shops.myshopify.com. It also says you can have only one A record and one www CNAME. A leftover A record from your old host, or a registrar change that reset your DNS, produces exactly this symptom.

2. Storefront vs admin. If you can sign in to your admin and work normally but the storefront is broken or blank, the platform is serving you. The difference between the two is your theme and the apps that inject code into it. Undo the most recent theme edit or app install first. If you changed nothing, an app may have shipped an update that you didn’t.

3. A real page vs a landing page. In private mode, Shopify’s help centre says, “all of your online store’s pages are hidden from visitors and search engines” and a password landing page shows instead. Someone switching it on by mistake (or a store that was never launched) looks like an outage to every customer and like a working site to you, because you’re signed in.

4. Browsing vs buying. If pages load but checkout fails, check whether the store is on Shopify’s Pause and Build plan. Shopify’s documentation says that plan deactivates checkout “across all sales channels.” Otherwise, look at the Checkout component on the status page and at any payment or checkout apps you rely on.

What you seeLikely layerCheck first
myshopify.com works, your domain doesn’tDNS / domain connectionA record and www CNAME at your DNS host
Admin works, storefront blank or brokenTheme or appLast theme edit, last app install or update
Customers see a password pagePrivate modeOnline Store → Preferences
Pages load, checkout failsPlan, checkout, or paymentsPlan status, Checkout component, payment apps
Admin and storefront both downShopifyshopifystatus.com, then My Shopify Status

Why Your Monitor Might Say Everything Is Fine

A basic uptime check asks one question: did the page answer with a success code? For several of the failures above, the answer is yes.

We checked this on October 26, 2026 against a store in private mode. Requesting its homepage redirected twice and ended on /password, which answered 200 OK. An uptime check that follows redirects, as ours does, scores that as up. The page is up. The store is closed.

A broken theme can do the same thing. If an app’s script fails and the product grid never renders, the server still sent a perfectly good HTML page. Status codes describe the server’s opinion of its own response. They can’t tell you whether customers can buy anything.

So the uptime check is necessary but not enough. It catches a dead domain and a platform outage. It misses the failures that live inside a page that loaded.

Monitoring That Separates the Layers

The fix is to watch each layer with the check that can actually see it. In FlareWarden, that’s three monitors on one store, and they share the free plan’s monitor pool:

  • An uptime check on your custom domain, not the myshopify.com address. That’s the one customers type, so it’s the one that catches a broken DNS connection.
  • A content check on a product page, looking for text that only appears when the store is really open: the “Add to cart” button label, or a product name. If private mode switches on, or a theme change stops the product from rendering, the text disappears and the check fails even though the page returned 200. Our guide to WooCommerce checkout monitoring walks through choosing what to watch, and the approach carries straight over. The content monitor docs cover the setup.
  • A dependency monitor on Shopify. When you add a site, Smart Setup looks at your domain’s DNS and recognizes a store hosted on Shopify, then offers a Shopify dependency monitor. Shopify’s status page runs on Atlassian Statuspage, a format FlareWarden reads, so the monitor follows Shopify’s own reported status. The dependency monitor docs explain how detection works.

Together they answer the question this article started with. Uptime or content failing while the Shopify dependency is green points at your layer. Both failing together points at Shopify. Our public Shopify status page shows the same platform-level picture if you just want to look.

What Outside Monitoring Can’t See

We’d rather be honest about the gaps. A check from outside sees what an anonymous visitor sees, so it won’t catch a problem that only affects signed-in customers, a discount code that stopped applying, or an app failure that only fires on a particular product. And because Shopify itself says small-scale issues may not reach its status page, a dependency monitor reading that page inherits the same blind spot. That’s the reason the content check on your own storefront matters most: it’s the only one of the three watching your store rather than the platform.

For the broader version of this problem (a vendor’s status page saying green while your integration is broken), see our piece on third-party API monitoring.


Key Takeaways

  • A green shopifystatus.com rules out a platform-wide outage, nothing more. Shopify says issues affecting a small share of stores may not appear there; check My Shopify Status next.
  • Compare your domain with your myshopify.com address to separate a DNS problem from a store problem in under a minute.
  • Admin working but storefront broken means theme or apps, so start with the last change.
  • Private mode returns a healthy 200, so only a content check notices a store that’s open to the server and closed to customers.
  • Watch each layer separately: an uptime check on the custom domain, a content check on a product page, and a Shopify dependency monitor.

Want to know your Shopify store is down before a customer emails you? Start monitoring free with FlareWarden: 15 monitors, 5-minute checks with multi-region verification, and no credit card required.