Switching reason · Reliability & bugs · Causes churn
Legacy projects shut down after repeated Next.js upgrade nags
1 source thread · first seen 2025-10
Summary
A user with old but still-trafficked projects was nagged to upgrade Next.js and then had them shut down with little warning. They moved to Cloudflare or self-hosting.
- Affects
- Owner of legacy projects still getting traffic
- Workaround
- Migrated to Cloudflare or self-hosting
- Switched to or considered
- Cloudflare
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“Eventually, they just shut them down without much warning”