I wanted to raise an issue I’ve been noticing with API calls across my apps for roughly the past 10 days.
I’ve been seeing significantly more API timeouts than usual. At first, I wasn’t sure whether this was specific to my setup, but I recently came across another post that seems to describe the same behavior I’m seeing in my monitoring tools.
The issue appears to be quite random. These timeouts almost never happened in the past, but I’m now seeing dozens of failed API calls throughout the day across several of my apps, with errors such as:
cURL error 28: Operation timed out after 10002 milliseconds with 0 bytes received for xxxxxx.myshopify.com/admin/api/2025-10/graphql.json
There doesn’t seem to be any obvious pattern, and retrying the same request generally works normally.
Has anyone else noticed an increase in Admin API timeouts recently?
This is especially concerning at the moment because intermittent API failures can become quite stressful when performing sensitive operations such as expiring access token migrations.
Hi @Axel, I’ll be happy to take a closer look for you.
Could you share exact UTC timestamps for a few of the timeouts, plus an x-request-id response header from a successful request made right before or after each one? The nearby successes give me something to match against on our side, since the timed-out call won’t have a request ID of its own.
Hi there, I’m the person that posted about this issue on the other thread.
I stared noticing these timeouts right after the day the new Admin UI design was announced.
As Axel stated, the timeouts are random and appear to affect different endpoints and actions within our app. Sometimes it’s when fetching a few dozen product, sometimes when fetching a single product or order, it would take like 60 seconds plus to fetch something that normally takes < 100ms.
Hello @Donal-Shopify, do you have an update on what’s happening with those timeouts?
We continue to see some random timeouts and other TCP connectivity issues. These don’t happen during the weekend, so I assume they’re part of a downtime or other kind of migration that’s happening on stores during the weekdays.
Thanks for those examples @flavio-b, and for waiting to hear back from me.
I was able to trace all three of those request IDs on our side tand can confirm they were rejected outright, with Shopify returning that SERVICE_UNAVAILABLE response within a fraction of a second, rather than a slow or hanging call.
The underlying infrastructure disruption behind those rejections has since been resolved by the team that owns it, so I’d treat those three specifically as explained.
If you’re still seeing failures this week, could you share one or two recent examples with the x-request-id from the request header (or the x-request-id of a nearby successful call, if the call actually times out with no response)? That’ll tell us whether what’s left is the same behavior or something else.
@Axel I’m still working with our infrastructure teams internally on the examples you shared, I’ll follow up as soon as I have news to share. Thanks for your patience so far!
We got the same situation in the recent weeks, already reported and partial improvement has been observed. I was also informed that they monitor on their side continuously, so while it’s good to share what we see they’re probably already on it (I hope they do)
Thank you. We have not seen any errors on Tuesday or this Wednesday morning. I will share more details if we start seeing them again. We appreciate your assistance!
Maybe I spoke too soon. While we didn’t a single API error on Tuesday and Wednesday, we’ve seen a cluster about 12 API-related errors in the last 45 minutes.
There have been no code changes on our end and traffic levels are pretty normal, server load is also normal. Unfortunately, for this cluster, I don’t see any request IDs or other details to share. For some reason the error descriptions in these cases are coming as “null”.