Is Shopify down?
Is Shopify down, or is the problem limited to your store, browser, network, account, or custom domain? Check Shopify’s current status, then isolate storefront, admin, checkout, and integration failures with targeted tests.
Site Administrator
Last reviewed: September 25, 2026
LATEST RECORDED STATUS
Up Shopify’s website appeared to be up and responding normally at the last check.
| Endpoint | Status | Observed |
|---|---|---|
| shopify.com | Operational | 2026-11-09 14:09 UTC |
Is it working for you?
0 recent reports — more reports are needed for a useful trend.
For the full picture, including partial or regional outages a single external check may miss, see Shopify’s official status page. official status page.
What this check can tell you
- Check the official Shopify status page before changing store settings or repeatedly retrying a failed action.
- If several Shopify stores or platform areas fail at the same time, a Shopify incident is more plausible than a problem on one device or network.
- If only one store is affected, compare its Shopify-provided store address with the custom domain to help isolate DNS, SSL, or redirect problems.
- A private window, another browser, and a different network can reveal cached data, extensions, expired sessions, or connection-specific failures.
- Record the exact error, affected URL, time, browser, network, and area involved—storefront, admin, checkout, or integration—before escalating.
About Shopify reliability
Understanding Shopify availability
Shopify availability can differ by platform area. A storefront may load while the admin is unavailable, or product pages may work while checkout fails. An issue may also affect only one store, account session, device, network, or custom domain.
Check the official Shopify status page for an incident affecting the specific function that failed. If no matching incident is listed, compare the affected store with another Shopify storefront, test a private browser window, and switch between Wi-Fi and mobile data. These checks help distinguish a Shopify-wide incident from a local or store-specific problem.
A custom-domain error does not by itself mean Shopify is unavailable. DNS records, SSL configuration, redirects, registrar settings, and DNS propagation can prevent access to one store while Shopify-hosted services continue to operate normally.
How to troubleshoot Shopify
Troubleshooting Shopify problems
Check for a Shopify-wide incident
Open the official Shopify status page and look for an incident affecting the specific area that is failing. If a relevant incident is listed, avoid unrelated store configuration changes and retry after Shopify reports recovery.
If the status page is clear, continue with the checks below. A clear status page does not rule out a store-specific, account-specific, domain, or regional connection problem.
Identify the affected Shopify function
- Storefront only: Test the store from another device or network. If the Shopify-provided store address works but the custom domain does not, focus on DNS, SSL, redirects, or registrar settings.
- Admin or sign-in only: Test a private window and confirm that the account session is valid. A failure limited to one account or browser is less suggestive of a platform-wide outage.
- Checkout only: Check whether product pages and the cart load normally. Record the exact checkout message and whether it affects every product, customer, payment method, or only one order path.
- Several Shopify stores or functions: Compare the results with the official status page. A broad, simultaneous failure is more consistent with a Shopify service incident.
- API or integration only: Check whether the equivalent storefront or admin action works in a browser. An integration-only failure may involve authentication, permissions, request handling, rate limits, or the integration itself rather than Shopify’s public availability.
Rule out browser and device causes
Reload the page, then test in a private window or another browser. Temporarily disable extensions that modify pages, scripts, cookies, or privacy settings. Clear site data only if you are prepared to sign in again, and test the same action on another device.
Rule out network and DNS causes
Switch between Wi-Fi and mobile data. If the store works on one network but not another, investigate the local connection, DNS resolver, firewall, filtering, or corporate network policy. For a custom domain, review its configuration with the relevant registrar or DNS provider and allow time for DNS changes to propagate. Do not repeatedly edit DNS records during a suspected Shopify incident.
Use the exact browser message to identify the likely layer. DNS_PROBE_FINISHED_NXDOMAIN points toward name resolution; a connection timeout points toward reachability; a certificate warning points toward TLS or domain configuration; and a redirect loop points toward URL or redirect settings. These errors do not all indicate a Shopify-wide outage.
Check store-specific and account-specific causes
If other Shopify stores work and the official status page is clear, focus on the affected store, custom domain, account, recent configuration change, or specific page and action. Capture the affected URL, timestamp, browser, network, account area, and exact error before contacting Shopify or another responsible provider.
Retry integrations and actions safely
For automated requests, record the returned HTTP status and response details and retry only when the operation is safe to repeat. For orders, payments, or other actions that may have completed despite an error, verify the result before submitting the action again. A timeout or server error is not proof that every Shopify service is unavailable.
Related troubleshooting guides
TROUBLESHOOTING GUIDE
500 Internal Server Error
A 500 Internal Server Error means the server encountered an unexpected problem while processing the request. The browser usually cannot identify the cause, so start by matching the failure time with PHP, application, and web-server logs. Recent code, plugin or theme changes, `.htaccess` rules, permissions, resource limits, and deployment settings are common causes.
TROUBLESHOOTING GUIDE
502 Bad Gateway
A 502 Bad Gateway means a reverse proxy, load balancer, or CDN could not obtain a valid response from the backend server. Check the backend process, proxy error log, upstream host or port, socket permissions, resource limits, and CDN-to-origin access. The fault is usually between servers rather than in the browser.
TROUBLESHOOTING GUIDE
503 Service Unavailable
A 503 Service Unavailable response means the service cannot handle the request at that time. Common causes include exhausted CPU, memory, worker, or connection capacity; incomplete maintenance mode; an unavailable database or other dependency; or a proxy, WAF, rate limiter, or load balancer returning 503. Identify which layer generated the response, then review logs and resource usage before changing settings.
TROUBLESHOOTING GUIDE
504 Gateway Timeout
A 504 Gateway Timeout means a proxy, CDN, load balancer, or gateway waited for a backend response but its timeout expired first. The backend may still be running; common causes include slow database queries, overloaded workers, long-running tasks, delayed third-party services, and restrictive intermediary timeouts. Compare direct backend timing with the full gateway path before changing timeout settings.
TROUBLESHOOTING GUIDE
DNS_PROBE_FINISHED_NXDOMAIN
DNS_PROBE_FINISHED_NXDOMAIN means DNS could not find the exact hostname requested. Check the spelling, subdomain, authoritative nameservers, required A, AAAA, or CNAME record, and domain registration status. If the DNS change was recent, cached negative responses may persist; it is usually a DNS or domain configuration issue rather than a web-server outage.
TROUBLESHOOTING GUIDE
ERR_SSL_PROTOCOL_ERROR
ERR_SSL_PROTOCOL_ERROR means the browser could not complete a TLS handshake with the server. Common causes include plain HTTP on port 443, an incorrect HTTPS virtual host, a CDN or proxy mismatch, or an incompatible TLS configuration. Test the HTTPS endpoint and certificate from the server or network side before changing browser settings.
TROUBLESHOOTING GUIDE
ERR_TOO_MANY_REDIRECTS
`ERR_TOO_MANY_REDIRECTS` means the browser is trapped in a redirect loop instead of reaching the requested page. Common causes include conflicting HTTP/HTTPS or www rules, a CDN SSL-mode mismatch, stale cached redirects, or an application that does not recognize HTTPS forwarded by a proxy. Trace the `Location` headers first, then correct the conflicting layer and retest with fresh headers.
Sources & references
Official source
- Shopify status page — Check current Shopify service availability, incident notices, and recovery updates.
Use the status page to assess platform-wide incidents. For a problem affecting one store, domain, browser, account, network, or integration, combine that status check with the targeted tests above. For implementation details, consult Shopify’s official documentation for the specific admin, storefront, checkout, domain, or API feature involved.
How this check works
Every time this page loads, our server makes its own request to shopify.com (and its API domain, when applicable) and reports what it got back — a real HTTP response, a timeout, or a connection failure. That result is cached for up to 2 minutes.
This confirms external reachability; it does not test every feature, region, account, or network path. Cross-check the official status page when one is available.
Embed this live status badge
Add this badge to a dashboard, documentation page, or blog. The badge reads the cached Erriscope observation and links back to this status page.
<a href="https://erriscope.com/status/shopify/"><img src="https://erriscope.com/status/badge/shopify.svg" alt="Shopify status on Erriscope" width="210" height="34"></a>Frequently asked questions
Is this the same as Shopify's official status page?
No. This is a live, one-off connectivity check run from our own server, not Shopify's own incident reporting. Their official status page can show partial, regional, or component-level issues our single external check cannot detect.
Why does this show "Up" when Shopify feels slow or broken for me?
A basic reachability check confirms that the server responded to our request. It does not test every feature, region, ISP, browser, or account-specific issue.
How often is this checked?
A check is refreshed after the two-minute cache expires. The displayed check time shows when the observation was made.
Does an API outage mean the whole product is down?
Not necessarily. Many services split their website and API onto separate infrastructure, so one can fail while the other keeps working.
How can I check whether Shopify is down?
Check the official Shopify status page for an incident affecting storefronts, admin, checkout, or another Shopify function. If no incident is listed, test the affected store from another network and browser to identify local or store-specific causes.
Why does my Shopify store not load when the status page is clear?
The problem may be limited to your custom domain, DNS, SSL configuration, browser, network, device, store settings, or account session. Compare the custom domain with the store’s Shopify-provided address, then test a private window and a different network.
Why is Shopify admin unavailable while my storefront works?
Shopify functions can be affected separately. Check for an admin or sign-in incident, then test a private window, another browser, and another network. If only one account or device fails, an authentication session, extension, or local connection is more likely than a platform-wide outage.
What should I do if Shopify checkout is not working?
First check whether product pages and the cart load normally. Record the exact checkout error and whether it affects every product or only one order path, then check Shopify’s official status page before changing payment, shipping, or store settings.
Is a Shopify DNS error always caused by Shopify?
No. DNS errors can affect one custom domain while Shopify remains available. Compare the custom domain with the Shopify-provided store address, test another network, and review DNS records with the domain provider before treating the problem as a Shopify outage.
When is it safe to retry a Shopify request?
Retry only after confirming that the action is safe to repeat. For an order, payment, or other action that may have completed despite a timeout or error, verify its result first to avoid creating a duplicate.
This is a live connectivity check from our server, not an official statement from Shopify. A down result may also reflect a regional or partial outage.
LIVE CHECKS
