We noticed today that res.revalidate function (for page router sites) no longer works, looks like those pages are cached on CDN regions.
ie. After deploying a website, and then revalidate some of the pages, if a page has been cached on a CDN region, it does not get cleared even the page content has been changed.
This only happens for page router sites though, does anyone else experiencing the same issue as us?
This is also happening to us. We noticed on the 18th that revalidation is not propagating to all regions. It’s clearing DUB1 but then that revalidation is not working in, for example, Canada where one member of the team sees stale content. (NEXTJS 14.2.35)
@gudmundurbjarkisigur Have you guys got any response from support or do you have and solutions to this?
We still have quite a few websites using page router and apparently this is affecting all the page router sites.
Nope, no response from support and we haven’t found any solutions either 
It looks like they just updated the Vercel CDN Cache page today so I suspect they made some changes to the CDN settings?
Hopefully it’s fixable and can be fixed soon !! 
Hi there, thanks for sharing this. Our team is currently investigating it, and I’ll share updates here.
This should be fixed now as of about an hour ago, can you test again?
Seems to be fixed thanks !!!