3 months ago
hello, Fastly is blocking traffic to my site.
a bunch of requests are failing with "503 Service Unavailable". we've been experiencing unstable behaviour for the last hours.
response body: "Same machine same service in the most recent hop on cache-ams21027-AMS: scJ4iSV4UkyHDI2juJNzrcUzYk/oO1PMCyYg4bz5Utg!AMS!cache-ams21027-AMS"
4 Replies
3 months ago
I have escalated this to Fastly. Do you know how frequently this is happening?
thanks @Phineas, it’s happening on all /api/trpc/* routes in my app.
frequency-wise, it’s constant. i’ve already tried both 5G and Wi-Fi, and the behavior is the same
3 months ago
Hey I had loop detected issue with Upstash workflows maybe what I've found would be helpful for you. A bit different issue I believe but might be related to headers.
https://station.railway.com/questions/production-api-unreachable-requests-no-6d15c4fb#wwpd
3 months ago
Thanks both. Our SSR tRPC calls were exiting the server, traversing Fastly, and coming right back to the same Next.js process. This unnecessary hop in the server config was causing the behavior.