@Alan_G, we’re noticing a big cluster of timeout errors when accessing the GraphQL API. Still investigating which endpoint specifically, but I just wanted to ask if you’re seeing something on your end?
We are experiencing the same issue.
Hi folks
- thanks for flagging this. I don’t see any reports of this on my end at the moment, but since we’re seeing two independent reports I’m happy to look into this. Would you folks be able to share any request IDs for these timeout errors you’re seeing and I can prioritize looking into this right way?
We are also experiencing the same issue with version 2025-01.
Same issue here on version 2025-01. We get “Http request error, no response available”
Hi Alan, we’re trying to grab a request ID, but because these all appear to be timeouts, it’s erroring outside the GraphQL response.
For example, affecting a query like “nodes(ids: $ids) {…on Product}” and others. API version: 2025-07
graphql products API on the latest version is not returning data, it’s giving AggregateErrors
Hello, my app is facing “Http request error, no response available: GraphQL Client: request to https://galmis-test.myshopify.com/admin/api/2025-04/graphql.json failed” when fetching orders and products via the admin api.
@flavio-b - thanks for clarifying. Just sharing an update with you folks, we are seeing reports of similar behaviour from other partners/merchants now and I’m communicating with some folks internally. I’ll keep you up to date in this thread here once I can confirm a fix/next steps.
We’re experiencing the same issue on our end, and it’s currently bringing our business to a halt. Appreciate you looking into this as soon as possible @Alan_G
Error:
HttpRequestError: Http request error, no response available: GraphQL Client: request to https://xxxxxx.myshopify.com/admin/api/2024-07/graphql.json failed, reason:
Same issue here - our merchants have been facing intermittent checkout stoppage for almost three hours now. Ongoing chat in the Shopify partners chat in graphQl and appdev channels. I have an open ticket with support
as well.
My support team reports there were similar issues for about half an hour yesterday at 3pm EST as well if that helps at all. Those were acting the same but were not verified to be API timeout/unreachable.
Hi folks, just reporting back. The issue we were tracking that seems to be related to the reports here has been resolved. Could you let me know if you’re seeing improvements?
10 minutes and counting since the last of these errors hit my logs
AWS has resolved the issue:
https://health.aws.amazon.com/health/status
So most likely you were only impacted if your app was hosted in or a dependency was using us-east-1
Going to mark this thread as solved all, but if you do see any timeouts re-emerge, please feel free to ping me here and I’ll take a look.
We’ve been seeing the same issue all morning, starting at 9am Pacific Time, and continuing through now. We don’t have any request IDs to report as it seems that we’re not even able to open a connection to the GraphQL API.
Hey @Andrew_Le - thanks for reporting. Is your API integration a public app? If so, and if the issue is still persisting for you, if you’re able to share a link to the app here I can take a look in our logs to investigate further. If it’s a custom/private app, just let me know and I can set up a DM with you and we can investigate further ![]()