ISR not working on application root with i18n when deployed to Vercel

[Guiso92]

Link to the code that reproduces this issue

https://github.com/theirc/refugee.info-greece

To Reproduce

1. Go to the current deployment
2. Check on the terminal the request headers

Current vs. Expected behavior

I set up a revalidation time on getStaticProps for index.tsx expecting the ISR to work every 60 minutes but currently that's not happening and you can see that the request header comes as STALE. All of the others dynamic routes ISR are working but not for index.tsx This is happening only on PRODUCTION and not locally.

Verify canary release

• [X] I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: macOS
  Arch: arm64
  Version: Sonoma 14.0
Binaries:
  Node: 18.17.0
  npm: 9.6.7
  Yarn: 1.22.17
  pnpm: N/A
Relevant Packages:
  next: 12.3.0
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 4.8.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Data fetching (gS(S)P, getInitialProps), Internationalization (i18n)

Additional context

I tested this both locally and deployed to Vercel. Locally works fine but when deployed to Vercel the ISR it's not working at all.

[samuelsalter]

Did you ever find a solution to this problem? As we're facing it as well.

[abysmapithecus]

Yep, doesn't work for me either, cache revalidation is broken