
May 9th, 2026
How to Change the Vercel Server Region for Next.js Projects (And Why It Matters)
Production Next.js APIs at ~800ms+ despite lean MongoDB. Moving Vercel functions from iad1 (US) to bom1 (Mumbai) cut latency to ~100ms.
13 min read
Blog · Author

@parveenkumar
Email team@parveenkumar.info
I build and ship web products, chase production bugs, and write down what actually worked—SEO, Next.js, performance, and the messy middle between “it works on my machine” and a calm dashboard.
Filter all posts by this author on the home feed.

May 9th, 2026
Production Next.js APIs at ~800ms+ despite lean MongoDB. Moving Vercel functions from iad1 (US) to bom1 (Mumbai) cut latency to ~100ms.
13 min read

April 26th, 2026
A real debugging story about fixing a Next.js sitemap when Google Search Console showed Couldn't fetch for months—and what finally worked.
10 min read

May 2nd, 2026
What I learned from a sudden 99% impression drop in Google Search Console, and why panic was the wrong first reaction.
12 min read

May 17th, 2026
App Router pushed me from Axios to native fetch: caching, AbortController, and fewer layers in production—not a package comparison rant.
14 min read

May 19th, 2026
Stale API responses overwrote fresh UI during fast navigation. AbortController and SWR fixed ghost requests in Next.js App Router.
15 min read

May 21st, 2026
Wi-Fi hid async bugs in my Next.js app. Chrome throttling exposed race conditions, stale UI, and wrong request order before users noticed.
17 min read