APNIC Pty Ltd.

11/20/2026 | Press release | Distributed by Public on 11/19/2026 22:34

What small ISPs told me about IPv6 adoption

Md. Rafeeun Noby Babir poses a question to the APNIC EC during the AMM at APNIC 62 in Mumbai.

I regularly talk to Internet Service Providers (ISPs) in Bangladesh as part of my work. Some of these conversations made me curious about a problem I kept seeing:

Many small ISPs had access to IPv6 resources but were not using IPv6 in their networks.

I wanted to know why.

So, whenever I had the opportunity to talk to an ISP operator, I started asking a simple question: What has stopped you from deploying IPv6?

These were informal conversations, not a formal survey. But after talking to a number of operators, I started hearing similar answers. What surprised me was that the problem was often not the technology itself. Cost concerns, a lack of knowledge, and uncertainty about IPv6 were also keeping them from moving forward.

Who did I talk to?

Most of the ISPs I spoke with were small operators serving around 1,000 to 3,000 customers.

They usually had small teams. In some cases, one technician was responsible for almost everything related to the network, from installation to troubleshooting. Other staff handled customer support and day-to-day operations.

These ISPs managed to keep their networks running, but they did not always have someone with experience in network design or IPv6 deployment. When they needed help with more complicated technical decisions, some relied on outside consultants. For a small ISP, deploying IPv6 is not just a matter of changing a few settings. Someone needs to understand how it works, plan the deployment, and be ready to fix problems if something goes wrong.

When the same person is already busy keeping the network running, learning, and deploying something new can be difficult.

Many think more IPv6 means more cost

Cost was one of the main concerns I heard during these conversations.

Small ISPs in Bangladesh work in a competitive market where customers are sensitive to price. They have to think carefully before spending money, especially on something that does not bring an immediate return.

This also affects how they think about IPv6.

Some operators were concerned that their existing IPv6 allocation would not be enough as their networks grew. They wanted to add more customers, serve multiple locations, and leave room for future expansion. But they were worried that getting more IPv6 addresses would mean paying higher APNIC membership fees.

I started looking more closely at what they were seeing when they visited the APNIC Get IP page.

The fee table mainly shows /48 and /32 as IPv6 options. Some operators understood this to mean that they had to choose between a /48 and a /32. If they needed more than a /48, they assumed they would have to move to a /32 and pay more.

This is where I saw a gap between what operators understood and what they needed to know.

Some operators were worried about the cost of getting more IPv6 space before they had even started using IPv6.

In some cases, a clearer explanation of the available options and fees could help them make a better decision.

They don't always know they can request more IPv6 space

The cost concern was closely linked to another issue: many operators were not familiar with APNIC's IPv6 allocation process.

They often approached IPv6 with the same mindset they used for IPv4. With IPv4, address space is limited, and getting more addresses can be difficult or expensive. It is understandable that operators carry this concern over to IPv6. During our conversations, operators asked about future growth, the number of customers they could serve, and whether their allocation would be enough for their long-term plans.

Some did not know that they could request a larger IPv6 allocation from APNIC if they could demonstrate a genuine need.

The IPv6 section of the application form currently presents options such as /48, /32, or an input field. Someone who is not familiar with IPv6 addressing may not know what to enter. And what many operators do not realize is that the cost is the same whether they request a /48, /44, /40, /36, or /34.

If you already have IPv4 and a /48 IPv6 but think you might need more IPv6, tell APNIC what you need and why. You may be able to get more IPv6 space, up to /34, without an additional IP-resource application fee.

They are not confident about deploying IPv6

Another issue I heard repeatedly was a lack of technical confidence. Most of the operators were comfortable with IPv4. They had been running IPv4 networks for years and knew how to handle the usual problems.

IPv6 was different. They had questions about configuration, routing, security, and how it would work alongside their existing networks.

For a small ISP, a mistake can affect customers. If there is no experienced engineer available to help, even a small problem can become stressful. Some operators were not necessarily against IPv6. They simply did not feel ready to deploy and maintain it.

I think this is where practical training can make a difference. Small ISPs need more than presentations explaining what IPv6 is. They need hands-on sessions showing how to configure it, troubleshoot common problems, and run it alongside their existing IPv4 networks.

Learning from other ISPs that have already deployed IPv6 could also help build confidence.

Security is another concern

Security came up in several conversations, particularly when we discussed customer devices.

Some operators were worried about giving globally routable IPv6 addresses to devices such as home surveillance cameras. They thought this might make the devices easier to access from the Internet.

These concerns should not simply be dismissed. Operators need to understand how IPv6 security works.

At the same time, a globally routable IPv6 address does not automatically make a device accessible from the Internet. Firewalls and proper security settings remain important.

For small ISPs, the challenge is knowing how to configure those protections correctly.

Practical examples of IPv6 firewall rules, customer network security, and common mistakes could help operators understand the risks and how to manage them. If IPv6 feels like a security risk that they do not know how to control, they are unlikely to make it a priority.

Customers don't ask for IPv6

Another answer was simple: Customers rarely ask for IPv6.

Most customers contact their ISP when something is not working or when they need a particular service. Some ask for public IPv4 addresses for online gaming, remote access, or applications that have problems working behind Carrier-Grade Network Address Translation (CGNAT).

Very few ask whether their Internet connection supports IPv6. From an ISP's point of view, it can be difficult to justify spending time and resources on something customers do not ask for, especially when the business is already operating on tight margins.

This creates a cycle. Customers do not ask for IPv6 because many do not know about it. ISPs see little immediate demand, so they delay deployment.

Breaking this cycle will take effort from more than just ISPs. Network operators, content providers, industry groups, and the wider Internet community all have a role in making IPv6 more common and helping people understand why it matters.

What can the Internet community do to help?

After these conversations, I believe there are several practical ways the Internet community can help small ISPs move forward with IPv6.

  1. Make IPv6 allocation and costs easier to understand. Organizations such as APNIC can help operators understand what IPv6 resources they are eligible to request and how the associated fees work. For example, an ISP that already has IPv4 resources and a /48 IPv6 allocation may be able to request more IPv6 space, up to /34, based on its actual requirements, without an additional IP-resource application fee. Many small operators are simply unaware of this. Sharing such information in simple language could remove one of the concerns holding them back.
  2. Make technical knowledge more accessible. Small ISPs need practical guidance, not just presentations about IPv6. APNIC, regional Internet communities, NOGs, and experienced network operators can help through hands-on training, configuration examples, and opportunities to learn from people who have already deployed IPv6.
  3. Help operators understand IPv6 security. Concerns about globally reachable customer devices, particularly home cameras and other connected equipment, can discourage deployment. Technical communities and experienced operators can share practical guidance on IPv6 firewalls, customer network security, and access controls.
  4. Encourage knowledge sharing among ISPs. Operators who have successfully deployed IPv6 can share their experiences, including the problems they faced and how they solved them. For a small ISP, learning from another operator with a similar network and limited resources can be more useful than reading technical documents alone.
  5. Create more awareness of IPv6 among customers and the wider Internet community. Content providers, network operators, industry groups, and technical communities all have a role in making IPv6 more visible. If customers begin to understand IPv6 and more services support it, ISPs will have greater motivation to deploy it.

Listening is a good place to start

Before I started these conversations, I expected technical problems to be the main reason small ISPs were not deploying IPv6.

Instead, I heard about cost concerns, confusion over address allocations, a lack of technical support, security worries, and customers who rarely asked for IPv6. These conversations were informal, so they do not represent every ISP in Bangladesh. But they gave me a better understanding of the challenges some small operators face.

For me, the biggest lesson is that making IPv6 available is not enough. We also need to make sure operators understand their options, know where to get help, and feel confident about deploying it.

APNIC and the wider Internet community have an important role to play here. Sometimes, a small ISP does not need another technical presentation. It needs a clear answer to a simple question:

Can I deploy IPv6 with the resources and budget I already have?

If we can answer that question clearly, we may be able to convince more small ISPs to take their first steps towards IPv6.

Ultimately, IPv6 adoption will not grow just because the technology is available. It will grow when operators understand it, see its value, and feel that they can afford and manage it.

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.

APNIC Pty Ltd. published this content on November 20, 2026, and is solely responsible for the information contained herein. Distributed via Public Technologies (PUBT), unedited and unaltered, on November 20, 2026 at 04:34 UTC. If you believe the information included in the content is inaccurate or outdated and requires editing or removal, please contact us at [email protected]