As a software engineer, I’ve always been a fan of Vercel. A few weeks ago I migrated a project from Cloudflare to Vercel—and it worked great until I accidentally triggered an SSR endpoint (/_render) that spiked resource usage and paused my entire account. (learn more here)
🚨 Quick recap
| Issue | Impact |
|---|---|
| Deployment | Project favorite ran SSR on Vercel |
| Usage Spike | Millions of SSR calls → account paused |
Route /_render |
112k+ requests in <12 h, 2.38 GB out, 14M invocations |
🔧 Temporary fix: migrate to Netlify
- Deleted/Paused the project from Vercel (June 16)
- DNS now points to Netlify at jpdiaz.dev
- Portfolio is live at jpdiaz.netlify.app
- Vercel account is paused jpdiaz.vercel.app
Next: switch the project to static generation, cache SSR, and block crawlers before re-deploying it safely.
How to temporarily migrate your Hosting from Vercel to Netlify
- Login to Netlify and Porkbun.
-
Go to Porkbun and save your records (A, CNAME, etc). I mean the records that point to your domain.
You only need to change the A and CNAME records
DNS Records Update
Tipo Host Vercel Value Netlify Value A lujoymoda.com 76.76.21.21 75.2.60.5 CNAME www.lujoymoda.com cname.vercel-dns.com dyr.netlify.app ALIAS *.lujoymoda.com cname.vercel-dns.com apex-loadbalancer.netlify.com - Go to Netlify and create a new project with the repository you want to migrate.
- Once the project is setup. Add a domain
lujoymoda.comto the project. - Go to Porkbun and update the records to point to the new IP address of Netlify.
- Wait for the DNS to propagate.
- Visit
lujoymoda.comto verify.
This experience reminded me of the importance of understanding how SSR impacts serverless costs. From now on, I’ll default to static generation when possible — and always back up my critical projects across providers.
My DNS Configurations (Backup Records)
Before doing the migration, it’s a good idea to save the DNS records.
JCDistributionCorp.com
Records that you should NOT change:
- MX records (email): fwd1.porkbun.com y fwd2.porkbun.com - KEEP IT THE SAME
- TXT record (SPF for email): El SPF para correo - KEEP IT THE SAME
- CNAME wildcard *.lujoymoda.com: OPTIONAL, but better keep it
lujoymoda.com
**You only need to change the A and CNAME records**
- Record A: `lujoymoda.com` → `76.76.21.21`
- This should change to the IP of Netlify: `75.2.60.5`
- Record CNAME: `www.lujoymoda.com` → `cname.vercel-dns.com`
- This should change to the domain of Netlify: `dyr.netlify.app`
To learn more about how to migrate your Hosting from Vercel to Netlify, check out the [step by step guide](#step-by-step-guide)
talentoparati.com
| Type | Host | Answer | TTL | |
|---|---|---|---|---|
| A | talentoparati.com | 76.76.21.21 | 600 | |
| Notes: REPLACE THIS RECORD | ||||
| CNAME | www.talentoparati.com | cname.vercel-dns.com | 600 | |
| Notes: REPLACE THIS RECORD | ||||
| CNAME | new.talentoparati.com | cname.vercel-dns.com | 600 | |
| Notes: github.com/JuanPabloDiaz/new-site-astro-talentoparati | ||||
| CNAME | url.talentoparati.com | cname.dub.co | 600 | |
| Notes: acortador de links con app.dub.co | ||||
| CNAME | www.links.talentoparati.com | cname.vercel-dns.com | 600 | |
| Notes: linke.ro/talentoparati | ||||
| CNAME | *.talentoparati.com | pixie.porkbun.com | 600 | |
| Notes: | ||||
| CNAME | professional.talentoparati.com | cname.vercel-dns.com | 600 | |
| Notes: github.com/JuanPabloDiaz/professional | ||||
| CNAME | profesional.talentoparati.com | cname.vercel-dns.com | 600 | |
charlotte-us.com
 **You only need to change the A and CNAME records** - Record A: `charlotte-us.com` → `76.76.21.21` - This should change to the IP of Netlify: `75.2.60.5` - Record CNAME: `www.charlotte-us.com` → `cname.vercel-dns.com` - This should change to the domain of Netlify: `charlotte-us.netlify.app`miguediaz.com
**You only need to change the A and CNAME records** - Record A: `miguediaz.com` → `76.76.21.21` - This should change to the IP of Netlify: `75.2.60.5` - Record CNAME: `www.miguediaz.com` → `cname.vercel-dns.com` - This should change to the domain of Netlify: `madiaz.netlify.app`jpdiaz.dev
**You only need to change the A and CNAME records**
- Record A: `jpdiaz.dev` → `76.76.21.21`
- This should change to the IP of Netlify: `75.2.60.5`
- Record CNAME: `www.jpdiaz.dev` → `cname.vercel-dns.com`
- This should change to the domain of Netlify.
Step by Step Guide
The above table is a summary of the changes you need to make. but here is a step by step guide using the example of lujoymoda.com
lujoymoda.com
1. Change the A record:
- Type: A
- Host:
lujoymoda.com - Value: Change from
76.76.21.21→75.2.60.5
2. Change the CNAME record of www:
- Type: CNAME
- Host:
www.lujoymoda.com - Value: Change from
cname.vercel-dns.com→apex-loadbalancer.netlify.com
Important:
- DO NOT touch the MX records (email)
- DO NOT touch the TXT (SPF)
- DO NOT touch the wildcard
*.lujoymoda.com
After the change:
- Save the changes in your DNS
- Wait 5–30 minutes for propagation
- Visit
lujoymoda.comto verify
Conclusion
This journey taught me valuable lessons beyond the technical fix:
- 🤯 Challenging my comfort zone: Working with Netlify, rediscovering Cloudflare, and revisiting Porkbun’s DNS reminded me how quickly essential workflows can slip—and how valuable it is to keep them sharp.
- 🧩 Architecture matters: SSR without caching, rate limiting, or crawler controls can easily drive resource usage through the roof.
- ☁️ Redundancy isn’t optional: Deploying key projects to multiple platforms provides peace of mind—unexpected failures won’t take everything down.
- 🛠 Be proactive, not reactive: I’m migrating to static builds, adding robots.txt, caching, and monitoring to stay ahead of future issues.
⸻
While I planned and built in public, nothing beats real-world learning. What started as a downtime incident became a catalyst for growth—technically, strategically, and personally. If you’ve faced similar surprises, I’d love to hear how you bounced back.