Skip to content
AlertPing

Guides

Why is my Shopify store unavailable?

| Guides | 8 min read

“This store is unavailable” on a Shopify storefront is almost never a Shopify outage. It is a billing or domain problem on your side. The seven usual causes, roughly in order of how often they turn out to be the answer: an unpaid or failed subscription payment, an expired trial, a store that was paused or deactivated, a store still password protected, a custom domain pointing at the wrong DNS records, a domain that expired at the registrar, and a store that was never published to the online store channel. Six of the seven you can fix yourself in the admin in a few minutes.

The reason this page is confusing is that Shopify serves it with a completely healthy HTTP 200 response. The server did its job. It returned a page, quickly, exactly as designed. The page just happens to say your store does not exist. Every uptime monitor that only watches status codes reports green while you sell nothing, which is how merchants end up finding out from a customer hours later.

First, rule out Shopify itself

Takes ten seconds, so do it first. Open shopifystatus.com and look at the Storefront and Checkout components. If they are green, the problem is yours, and you can stop wondering. If they are red, there is nothing for you to fix and you may as well go make coffee.

One caveat worth knowing: Shopify's status page carries a disclaimer that issues affecting a small percentage of stores may not be reflected there. A problem that hits only your store is by definition a small percentage of stores. So a green status page rules out a platform-wide outage. It does not prove your store is fine.

The seven causes, and how to fix each

1. A failed or unpaid subscription payment

The single most common answer, and the most embarrassing one. A card expired, a bank declined a charge as suspicious, or the billing email went to someone who left. Shopify retries, emails, and eventually freezes the store. A frozen store serves exactly this page.

Check Settings, then Billing in your admin. If there is an outstanding invoice, pay it and the storefront usually returns within minutes. Then fix the underlying cause: put a card on file that does not expire soon, and make sure billing notifications go to an address more than one person reads.

2. The trial ended

If you were on a trial and did not select a plan, the store goes offline when the trial ends. Your data is intact and nothing is lost. Pick a plan in Settings and the storefront comes back.

3. The store is paused or deactivated

Shopify has a reduced-cost pause option, and stores can also be deactivated manually or by Shopify for a terms issue. A paused store keeps your admin and data but takes the storefront down. If you did not pause it deliberately, check your email for a notice from Shopify before assuming something technical broke.

4. The store is still password protected

Every development store starts behind a password. This bites hardest right after launch: you connect the domain, tell everyone, and forget the password page is still on. Visitors see a password prompt or an unavailable page depending on the setup.

Go to Online Store, then Preferences and disable the password page. Note that on some plans the password page cannot be removed until you have selected a paid plan, which is the same problem as cause two wearing a different hat.

5. Custom domain DNS pointing at the wrong place

Now we are into the genuinely technical ones. Shopify expects your apex domain to have a single A record pointing at 23.227.38.65, and www to be a CNAME pointing at shops.myshopify.com. The things that reliably break it:

  • A leftover second A record from your previous host. DNS will round-robin between them, so your store works about half the time, which is far more confusing to debug than it being fully down.
  • An AAAA record. Shopify does not support IPv6. If your DNS answers with an IPv6 address, visitors whose networks prefer IPv6 go nowhere while everyone else is fine.
  • A DNSSEC conflict, usually after a registrar transfer, where the signing records no longer match.
  • Cloudflare proxying in front of Shopify. The orange cloud interferes with certificate provisioning and can cause redirect loops.

Fix the records at your registrar, then wait. DNS changes are not instant and propagation can take up to 48 hours, though it is usually far quicker. Resist the urge to keep changing things while you wait, which is how a one-record fix turns into an afternoon.

6. The domain expired

If you bought the domain somewhere other than Shopify, its renewal is between you and that registrar, and Shopify has no visibility into it at all. An expired domain takes your store down completely, and the recovery involves redemption fees and a wait if you let it lapse too long. Turn on auto-renew and monitor the expiry date rather than trusting a reminder email from a registrar you last logged into three years ago.

7. The store was never published to the online store channel

Rare, but it happens on stores set up for point of sale or wholesale first, where the online store sales channel was never added or was removed. No channel, no storefront.

A quick triage table

What you see Most likely cause Where to look
“This store is unavailable”Billing, trial, or paused storeSettings, Billing
Password promptPassword page still enabledOnline Store, Preferences
Browser security warningSSL not provisioned or DNS wrongSettings, Domains
Works sometimes, fails othersTwo A records, or an AAAA recordYour registrar's DNS
Site not found, DNS errorDomain expired or records removedYour registrar
Redirect loopCloudflare proxy in front of ShopifyCloudflare, set DNS to grey cloud
Blank or half-rendered pageTheme edit or app script brokeOnline Store, Themes

What about “SSL unavailable”?

Different message, related cause. Shopify provisions the certificate for you automatically, but only once your DNS is correct. If TLS setup keeps failing for around 48 hours, the domain lands in an “SSL unavailable” state and browsers throw a security warning at every visitor, which is arguably worse than being down because it looks like you have been hacked.

Almost always this is the same DNS problem from cause five. One under-known culprit: a CAA record on your domain that does not authorize the certificate authority Shopify uses. CAA records tell the world which authorities may issue certificates for your domain, and if yours lists only the one your old host used, Shopify's request is refused. Either remove the CAA record or add the authorities Shopify needs.

How to find out before your customers do

Every cause above has one thing in common: nothing tells you. Shopify does not phone you when your card declines. Your registrar does not phone you when DNS breaks. And since Shopify moved to a per-store status view behind a login, deprecating the status page SMS subscriptions and RSS feed along the way, there is no longer any way for Shopify to push you an alert at all.

So the first signal is usually a customer, and by then you have been down for hours. Often they do not even email you, they just post about it publicly, which is why plenty of merchants keep an eye on what people are saying about their brand across social as a crude backstop. It works, but it is a slow and painful way to learn your checkout is broken.

The direct approach is a check that runs from outside your store and looks at the actual page content, not the status code. Because Shopify returns 200 on all of these failures, a status-only monitor is useless here. What works:

  • Assert on a phrase that only appears when the page works, like the price or the add-to-cart label on your best selling product.
  • Invert one check: alert if the body contains “This store is unavailable”. That single assertion catches causes one, two, three and seven at once.
  • Watch the certificate expiry date separately so you get warned before the padlock breaks rather than after.
  • Check from more than one region, since a DNS or IPv6 problem often takes down some visitors and not others. A store that is up in Virginia and down in Frankfurt looks perfectly fine from your desk.

That is exactly what Shopify uptime monitoring is for: 30-second checks on the storefront, product page and cart, content assertions rather than status codes, confirmed from three regions, with an SMS when something stops matching. The live check on our demo page will run against your store right now if you want to see what it returns before signing up for anything.

The short version

If your Shopify store says it is unavailable, check billing first, then the password page, then your DNS records. It is one of those three the overwhelming majority of the time. Shopify's own uptime figure explicitly excludes theme errors, app errors and third-party services, and its status page will not show a problem that only affects you, so a green status page is not evidence that your store is selling. The only thing that tells you that is something checking your real storefront, from outside, reading the page.

Catch it in 30 seconds, not three hours

Content-aware checks that fail when your store stops saying what it should, confirmed from three regions, with SMS in every plan.

See pricing