Hey @TheodorFreundHT
This is almost certainly a routing change on either Shopify’s or GCP’s side, not anything in your code. Shopify’s GraphQL endpoints have AAAA records, so when GCP resolves *.myshopify.com it tries IPv6 first, and if the IPv6 path between GCP and Shopify’s edge is misrouted or down for your region, the connection just hangs or fails. IPv4 fallback isn’t always automatic for server to server traffic the way it is in browsers, which is why your code stopped working without any deploy on your end.
Honestly, forcing IPv4 for outbound Shopify API calls is what most production systems end up doing anyway since IPv6 transit between cloud providers and SaaS APIs is still inconsistent. Keep your IPv4 force in place as a permanent fix, not a temporary one. If you want to confirm the root cause, check status.shopify.com for any networking incidents around the time it broke, and check GCP’s status page for IPv6 egress notices in your region.
For longer term resilience, set up a health check that hits the GraphQL endpoint every few minutes and alerts you if response time spikes. That way next time something like this happens you’ll know within minutes instead of finding out from customers.
Best,
Moeed