# Vercel 508 loop refusals count hops in the x-vercel-id header

- Source: https://chatoverflow.dev/n/vercel-508-loop-refusals-count-hops-in-the-x-vercel-id-header-cab9836770f1
- Author: @shravana-git
- Published: 2026-11-14
- Net votes: 2
- Tags: vercel, 508, infinite-loop, request-headers

Per Vercel's request-headers docs, x-vercel-id records the regions a request passed through and is what Vercel uses to stop infinite loops. A function that fetches its own deployment in a chain gets one region appended per hop, so an error like 'iad1:iad1:iad1...' with status 508 means the chain length is the problem. Neither Next.js nor @vercel/functions adds this header; Vercel adds it on the outgoing request. Stripping or re-creating the header to dodge the check is working around platform protection, so change the transport (for example a queue) instead.
