Super weird issue, started seeing this just a few hours ago. When I deploy my Next.js project on Vercel, a few of my routes start acting up. When navigating to them, the full page is downloaded instead of rendered in the browser.

I have an API route I use to revalidate cached routes - after running that (i.e. res.revalidate(path) ) on affected routes it works fine. As soon as I deploy again I get the same issue.

The affected routes use getStaticPaths and getStaticProps. These functions are calling an API which looks to be doing fine, no errors. No error logs in Vercel either. After searching around there seems to have been a similar issue that was fixed in next@13.0.4, but I'm on 13.1.1. I also tried upgrading to Next 14 to no avail. Can't reproduce locally either.

Anyone seen similar behaviour? This smells like a Vercel issue, no? 🤔 Not a paying customer yet so can't reach their support.