Live

Some merchants encountering error messages within their admins

Between 07:53 - 8:45 UTC on October 29, 2026, we experienced errors affecting the Admin, including in the Shopify mobile app. A fix was implemented at 08:30 UTC which resolved the issue. The monitoring period for this issue has ended and no further impact has been observed.

The latest update from Shopify.

State

Resolved

Started

3 d ago

2026-10-29 08:18 UTC

Lasted

42 min

until 2026-10-29 09:00 UTC

Worst impact

Notice

Timeline

4 updates
08:1808:2808:3908:4909:00
NoticeUpdate postedTimes in UTC

Investigating

26 min 61%

Identified

16 min 39%

Updates

Times in UTC

As posted by Shopify

Resolved2026-10-29 09:00 UTC

Between 07:53 - 8:45 UTC on October 29, 2026, we experienced errors affecting the Admin, including in the Shopify mobile app. A fix was implemented at 08:30 UTC which resolved the issue. The monitoring period for this issue has ended and no further impact has been observed.

Identified2026-10-29 08:43 UTC

We've identified the problem impacting Admin and mobile version of Admin and we're working on a solution. Admin is now fully available and our team continues to work on the issues impacting the mobile version.

Investigating2026-10-29 08:34 UTC

We are continuing to investigate slow page loads and errors affecting Admin for some merchants. We will provide another update when more information is available.

Investigating2026-10-29 08:18 UTC

Merchants may experience errors or slow loading when trying to access the Shopify admin. Affected pages may fail to load and show the message "504 Gateway Time-out". We're investigating and will provide an update as soon as possible.

Shopify in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

1

Days with an incident

1

Median duration

42 min

This incident

About the median

Follow Shopify

Your coding agent knows when Shopify is down, and tells you when a failure is theirs, not yours. You can also get Shopify incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "shopify" and tell me if Shopify has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=shopify
Slack
/feed subscribe https://outages.cc/feed.xml?providers=shopify

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane