Does Vercel have a region in Nigeria?
No. Vercel has no region in Nigeria. Its nearest compute region is Cape Town — cpt1, roughly 4,600 km from Lagos — and it is not the default: every new Vercel project runs its functions in Washington, D.C. (iad1) until somebody changes it. Static and cached content is fast almost anywhere, because Vercel terminates TCP at one of its 126 points of presence and serves from cache; anything dynamic runs in the region you chose, and anything that touches a database runs at the distance between that region and the database. Naijacloud runs af-west in Port Harcourt, with the container, the Postgres instance and the object storage bucket all in-country, so a dynamic request and every query it makes stay inside Nigeria.
The distinction that matters is between the edge and the origin. Vercel’s CDN is genuinely excellent and a cached page will reach a Lagos browser quickly, because the TLS handshake terminates at a nearby PoP and the bytes come from a regional cache. That is the part people measure when they say Vercel is fast, and they are right.
What is not at the edge is your data. Vercel Functions execute in one of 20 compute regions, defaulting to iad1 in Washington, D.C. for all new projects. A page that renders from a database therefore costs the round trip from Lagos to the PoP, the private hop to the region, and then the function’s own round trips to wherever the database lives. Six sequential queries against a database in Virginia is six transatlantic round trips inside one page render, and no amount of CDN improves it.
You can move the functions. Cape Town (cpt1) is a real Vercel region, and on a Pro plan you can run in up to five regions; Hobby is one. Two caveats before treating that as the answer. Cape Town is about 4,600 km from Lagos on a different set of subsea cables, so it is nearer than Virginia and not near. And Vercel’s own failover table lists cpt1 last, at P19, behind every other region — which tells you where it sits in the network’s topology.
The harder problem is the database. Vercel has no first-party managed Postgres in Cape Town; databases come from marketplace partners, and the common ones have no African region either. So the realistic Vercel shape for a Nigerian app is functions in cpt1 or iad1 and a database in the US or Europe — which puts the slowest hop in the middle of every request, exactly where a CDN cannot reach it.
And if the requirement is residency rather than speed, none of this applies at all. A contract that says Nigerian customer data stays in Nigeria is not satisfied by Cape Town, by Frankfurt, or by a cache in Lagos. It is satisfied by the volume being in Nigeria.
Platform comparison
Scored out of five on what actually changes your day.
Where a cached page is served from
Naijacloud
4/5Cloudflare in front of every customer hostname, so cached assets are served from a nearby edge — including Lagos.
Vercel
5/5126 points of presence with TCP terminated at the nearest one. For static content this is as good as it gets.
Where dynamic code runs by default
Naijacloud
5/5In the region you picked, and af-west is Port Harcourt. There is no default that quietly puts you on another continent.
Vercel
2/5Washington, D.C. (iad1) for all new projects. Nigerian users pay a transatlantic round trip for anything not cached until someone changes it.
Nearest region to Lagos
Naijacloud
5/5af-west, in Port Harcourt. In-country, on domestic routes.
Vercel
3/5Cape Town (cpt1), about 4,600 km away — a real African region, and listed last in Vercel’s own failover priority.
Where the database can sit
Naijacloud
5/5In af-west beside the app, reached over a private address. The app-to-database hop never leaves the region.
Vercel
2/5A marketplace partner in a region of its own, and none of the common ones offer Africa. The app-to-database hop is usually the longest one in the request.
Satisfying a Nigerian data-residency clause
Naijacloud
5/5Compute, database and object storage all in Port Harcourt. The volume is in the country named in the contract.
Vercel
1/5Not possible. There is no Nigerian region to put the data in, and edge caching is not residency.
Regions you can run in at once
Naijacloud
2/5One region per service. Three exist: Port Harcourt, London, Paris.
Vercel
5/5Twenty compute regions; five at once on Pro, all of them on Enterprise.
Frequently asked
It is, and it is worth using if you are staying on Vercel — cpt1 is real compute in af-south-1. It is just not a Nigerian one: about 4,600 km from Lagos on a different cable path, and Vercel’s own documentation lists it last in the failover order from iad1. It helps with latency and does nothing for a residency requirement that names Nigeria.
Because what you are measuring is probably the cache. Static assets and cached pages come from a nearby PoP and will feel fast. Open the network tab on a page that renders from the database, or on a form submission, and look at that number instead — that is the request that goes to iad1 or cpt1 and then on to wherever your database is.
Yes — set `regions: ["cpt1"]` in vercel.json or change the default in the project’s function settings. Hobby projects get one region and Pro gets five. It is the right move if you are staying, but check where your database is first: functions in Cape Town talking to Postgres in Virginia is slower than both being in the same place.
The container your code runs in, the managed database it queries, and the object storage bucket it reads from — all in af-west in Port Harcourt, with the app reaching the database over a private in-region address. Custom domains are fronted by a CDN for cached assets, the same as anyone else.
Related questions
Render · Nigeria latency and regions
Does Render have an African region?
Fly.io · Nigeria latency and regions
Is Fly.io’s Johannesburg region good enough for Nigerian users?
Supabase · Nigeria latency and regions
Which Supabase region should a Nigerian project use?
Vercel · App hosting and runtime
Can I run a long-running Node process, WebSockets or a queue worker on Vercel?
Or read the full Naijacloud vs Vercel comparison, which covers pricing, databases, email and the rows we lose.
Try it against your own workload
Deploy one service from a Git repo in Port Harcourt and compare the numbers yourself. Free tier, no card, no FX.