Yes we worked through the troubleshooting guide but were not able to find anything that looks overly suspect. Vercel is not showing logs for the page view and there’s no system we can see that would result in oversized headers on certain responses.
We’ve had incidents in the past where the 520 was caused by overly large CSP headers but the headers on this page are static at 6kb so shouldn’t be triggering the 520. Given that it’s Vercel it feels unlikely to be a HTTP/2 misconfiguration so we’re a bit stuck.
Security Events shows no findings for the RayID in question and the time period concerned.
