On 29 October 2026, Shopify's admin threw errors and slow loads for some merchants for 42 minutes. The fault sat on Shopify's side, in the API & Mobile component, not in anything you run yourself.
Started
08:18 UTC
Duration
Lasted 42m
Source
IsDown
Next time
Shopify is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: API & Mobile
What happened?
Shopify logged one incident on this day, starting at 08:18 UTC and lasting 42 minutes. The first update said merchants might see errors or slow loading in the Shopify admin, with affected pages showing a "504 Gateway Time-out" message. At 08:34 Shopify said it was still investigating the same slow page loads and errors, with no new detail added. At 08:43 Shopify said it had identified the problem affecting both admin and the mobile version of admin, and reported that the main admin was fully available again while work continued on the mobile version specifically. That is the last update on file, and no further filing marks the mobile fix as complete. No post-mortem has been published, so the underlying cause of the 504s is not on the record. No user reports were filed during this window, so the only account of what happened is Shopify's own three updates. Shopify's component list names a single affected component, API & Mobile, which lines up with the admin and mobile admin symptoms described. Over the past 90 days Shopify has logged 12 incidents with a median duration of 1 hour 19 minutes, so this one ran shorter than typical. Across all time Shopify averages 8.2 incidents a month, a rate worth keeping in mind if you build processes around its admin.
Learning
UptimeRobot's own 30 day checks on Shopify recorded 2 incidents, both resolved, with a median duration of 45 minutes, a figure close to what Shopify itself reported for this incident. That closeness matters because it shows an external check and the vendor's own status page can agree on timing even when the failure sits one layer up, inside a specific interface like the mobile admin, rather than at the infrastructure level a simple reachability probe would catch. A 504 on an admin page can appear even while the underlying service responds to pings, because the gateway timing out is a symptom of something failing between the request and the backend, not the backend being unreachable outright. If you only watch your own storefront or API endpoints, an incident scoped to Shopify's admin and mobile admin will not show up in your monitoring at all, because your product keeps running. That is the gap worth noticing: your monitoring covers your half, and UptimeRobot now watches the provider's half too, so next time something breaks you know which side it was without guessing.