Shopify Sidekick is unavailable
Shopify Sidekick was unavailable. The issue affected the Admin and Support components. Shopify reports that the issue is resolved. It lasted 22 minutes.
State
Resolved
Started
Lasted
22 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
22 min 100%
Updates
Times in UTCAs posted by Shopify
Between 22:00 – 23:00 UTC, we experienced an issue with Shopify Sidekick which made the AI interface on Help Center, Canvas and Admin unavailable. A fix was implemented at 22:55 which resolved the issue. The monitoring period for this issue has ended and no further impact has been observed.
Shopify Sidekick AI agent is currently unavailable, affecting Help Center and Admin requests. We are actively investigating the issue and will provide updates on recovery.
Affected components
2Shopify in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
3
Median duration
38 min
This incident
41% shorter than the median
Other Shopify incidents
All incidentsShopify·Some merchants encountering error messages within their admins or on checkout pages
Shopify merchants had intermittent errors in the Admin, Checkout, Storefront, and Point of Sale. Shopify says the issue is resolved. It lasted about 27 minutes, from 00:38 to 01:05 UTC.
Shopify·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.
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.
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.live/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.
https://outages.live/feed.xml?providers=shopify/feed subscribe https://outages.live/feed.xml?providers=shopifyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane