44 New African Regions

Expanding coverage across 20 countries.

Today we’re sharing something we’re really proud of: developers can now deploy workloads across 44 region codes in 20 African countries, seamlessly through the Monarch API. By footprint alone, Monarch now represents the largest coverage map available to African developers.

This coverage expansion marks a big step forward. Africa has often appeared on coverage maps as just a handful of dots—one or two data center hubs per region. Real-world infrastructure, users, and demand don’t sit neatly in one city. They’re spread across countries, provinces, and regions.

Why Regions Matter

A region is simply a location where your workloads can run. For developers, that means choosing where your applications, models, or data live. Sometimes that’s about being closer to your users for lower latency. Other times it’s about keeping workloads inside a particular country for compliance or data sovereignty.

When developers choose a region, they’re doing more than picking a location. They’re shaping:

  • Latency and user experience. Running closer to end users means faster responses and smoother apps.

  • Data sovereignty. Governments and enterprises often need data to stay within borders. Local identifiers make that possible.

  • Future growth. A clear map of regions today is also a roadmap for where capacity will come online tomorrow.

Right now, some of these regions route workloads through existing global hubs while we increase our compute capacity. The map is designed to give you a consistent interface today, while also showing where infrastructure is coming online tomorrow. If you code for a region now, your workloads will seamlessly shift to local capacity as soon as it’s available.

Global Parity

By giving developers access to regions in Kenya, Nigeria, South Africa, Egypt, Morocco, Ghana, Uganda, Tanzania, Rwanda, Ethiopia, Senegal, Côte d’Ivoire, Botswana, Namibia, Zambia, Zimbabwe, Mauritius, Tunisia, Algeria, and DRC, we’re creating a much more accurate and useful picture of how workloads can scale across Africa.

We also support established hubs in the United States, Europe, Asia, and South America. That makes it easy to mix and match local and global deployments in the same workflow.

Monarch coverage: 20 countries, 44 region codes available today.

The established global grid—anchored in international hubs.

The grid expands—adding 44 region codes across Africa alongside global hubs.

The Possibilities

For startups, this coverage means you can build products that feel truly local—anchored in your own markets—while still operating at a global scale. A business in Nairobi or Dakar will be able to serve its community with the same proximity and speed that users in London or New York enjoy.

For universities and researchers, it opens the door to compute tied directly to your country. No need to push projects into distant hubs. Instead, you can plan for access that aligns with national priorities, research mandates, and data sovereignty requirements.

For enterprises, the expanded map means more flexibility in how digital infrastructure is planned and deployed. Whether you’re thinking about compliance, latency, or disaster recovery, the ability to plan for 44 regions across 20 African countries creates options that simply didn’t exist before.

The coverage map is our north star. Over time, as demand grows, compute will come online directly under these region codes. The same strings you use today (kenya-nairobi-1, ghana-accra-1) will map to live in-country capacity as it’s added.

For now, we’re excited to share the new regions, and even more excited to see what people build on top of them.

Next
Next

The Monarch Africa Dataset