IXPN is Pumping Gigabits, But My Hotspot Still Thinks We Are in 2012

I spent three hours yesterday trying to deploy a small backend update over a shaky mobile hotspot during a rainy afternoon in Akure. The upload failed three times. Each time, my terminal hung, mocking me while my phone battery slowly cooked in my pocket.

So when I see headlines about the Internet Exchange Point of Nigeria (IXPN) hitting massive traffic milestones and advancing DNS localization, I feel a weird mix of hype and frustration.

On one hand, keeping traffic local is a massive technical win. On the other hand, the actual wire coming to your house—or lack thereof—is still a massive pain point.

Why IXPN’s Traffic Peak Matters to Your API Calls

If you build web apps in Nigeria, you know how painful latency can be.

Historically, when a user in Lagos clicked a button to query a database hosted on a local server, that request often had to travel across subsea cables to London, hit a routing server, and fly all the way back to Nigeria. It is wild when you think about it. It is like traveling to London just to send a WhatsApp message to your neighbor in Gbagada.

What IXPN does by keeping local traffic local—and what they are doing now with DNS localization—is cut out that overseas detour.

When DNS queries are resolved locally, the time-to-first-byte drops. Your database queries resolve faster. Your API calls to local fintech gateways do not mysteriously time out because of a undersea cable cut near Senegal. It makes the entire local web ecosystem feel snappier.

But here is where the reality check hits.

The 265k Fiber Problem

The National Communications Commission recently dropped a stat that made me sit back in my chair: Nigeria has only about 265,000 fiber-to-the-home (FTTH) connections.

For a country of over 200 million people, that is basically a drop in the ocean. Most of us are running our entire digital lives—and building our startups—off cellular data. We are relying on base stations that get congested the moment school lets out or everyone in the neighborhood starts streaming videos.

If you are working from a cold morning in Jos, or running a hub in Owerri, you are likely not on fiber. You are on a 4G router, praying the local telco mast does not lose power.

We talk a lot about building heavy, feature-rich web apps, but we forget that our users are paying ridiculous amounts for data on connections that are highly unstable. The ISPs are under pressure too—they want to raise tariffs to survive, and they are struggling to lay physical cables because digging up roads in Nigeria is an administrative nightmare.

How We Build Around the Bottlenecks

As developers, we cannot just wait around for fiber to magically appear at every doorstep. We have to design for the infrastructure we actually have.

First, stop building massive JavaScript bundles. If your React or Next.js app requires a 10MB download just to show a landing page, you are killing your conversion rate for users on mobile data in Onitsha. Keep it lean. Code-split everything.

Second, leverage local caching. If IXPN is keeping local traffic local, make sure your assets are cached at the edge.

Third, design for offline-first. If a user is filling out a form on your app and their network drops—which it will—do not just throw a generic network error and wipe their data. Store it in IndexedDB and sync it when the connection returns.

The infrastructure is getting better at the core, but the last mile is still a wild west. Until that fiber gap shrinks, our code has to be resilient enough to handle the chaos.