We clearly have different definitions of solved.
29 July, 10:21 GMT. My homepage returned a 429. Body local_rate_limited, retry-after 60. Request ID f867da48-8b8b-4c07-82ff-c739738857bc-1785320517, cf-ray a22b664f98b53eb9-LHR.
Support’s answer: my session had a fraud score of 99, and “rate limiting under these conditions is expected.” I was classified as a bot — while I was in the middle of a conversation with them.
Your own post here says: “VPN use does not automatically result in a 429, but there is not yet a complete solution for false positives.”
That same thread is now marked solved.
Which is it?
This thread was marked as solved back in May once we resolved the widespread issue that was blocking a large percentage of customers. If you’d prefer to continue the discussion here instead of the new thread, I’m happy to reopen this one. Just let me know.
Hello @Paige-Shopify
On VPN, on the Cart AJAX API.
What I’m doing: browsing the live store in Microsoft Edge on Windows. Add to bag / change qty / remove a line. The failing calls are:
POST /cart/changeGET /cart.jsonGET /cart.json?vsly=t (Visually)
Every request? Once it starts, yes. Cart writes and idle cart reads all 429. It is not one burst then recovery.
Request IDs: Shopify x-request-id is often missing because Cloudflare returns the 429. When headers are present:
POST /cart/change → 429
Date: Wed, 02 Sep 2026 14:54:06 GMT
Cf-Ray: a34d5918fa5b4133-LHR
Cf-Mitigated: challenge
Server: cloudflare
Content-Type: text/html; charset=UTF-8
No x-request-id
Earlier same session:
POST /cart/change → 429
Date: Wed, 02 Sep 2026 14:48:17 GMT
Cf-Ray: 834d44dc9b32771f-LHR
Server: cloudflare
On later 429s Edge shows Response headers (0) + “Provisional headers are shown” — the connection is dropped before Shopify can stamp an ID.
Please help!
@MarkBaginski thanks for reaching out! I couldn’t find any logs for 834d44dc9b32771f-LHR, but a34d5918fa5b4133-LHR needs further investigation. I’ll reach out to the relevant engineers and get back to you.
Thank you @Paige-Shopify, do you have any update on this please and would need more information?
@MarkBaginski, you’ve already shared all the information we needed. I’m waiting on the investigation results, which should be ready soon, and I’ll update you once I have more to share.
@MarkBaginski I have a question after all. Are you encountering this issue often?
Hey @Paige-Shopify 429’s have not been seen for the past 2 days, can you see anyway Shopify would have changed anything? Thanks for your support.
Thanks for letting us know, @MarkBaginski. We’re continuously improving the logic that returns 429 responses, so it’s possible a recent adjustment resolved the issue for you. Please reach out if you encounter it again.