## Next.js 12: Full page reload failing for 3-4% users after Chrome 141 update (Oct 16)

### Problem
Route navigation failures started on October 16th, affecting 3-4% of users (90% are Windows Chrome 141).

### Environment
- Next.js 12.x
- Red Hat Fusion (containerized)
- Issue rate: 3-4% of traffic

### Behavior
1. Initial page load: ✅ Works
2. After API call → router.replace('/target-page')
3. Page fails to load for affected users
4. All errors are from full page reload (URL shows /target-page, not .json)
5. Once user experiences issue, it persists

### What I've tried
1. Changed router.replace() to location.replace() - still failing
2. Verified deployment and URL pattern changed
3. Infrastructure team confirmed no config changes on Oct 16
4. No source code changes before issue started

### Questions
1. Anyone experienced full page load failures with Next.js 12 + Chrome 141?
2. What could cause page load to fail only for specific users after browser update?
3. Known compatibility issues between Next.js 12 and Chrome 141?
4. Should I upgrade Next.js version?

Any help appreciated!