IBSS Nepal and the Economics of Visible but Dependent Internet Infrast

IBSS Nepal and the Economics of Visible but Dependent Internet Infrastructure

Research thesis

IBSS Nepal is a small but analytically useful case because it separates three things that are often collapsed in public discussion of internet companies: ownership of visible internet-number resources, control of physical connectivity, and the commercial promise of managed business service. The public record shows a Kathmandu-focused enterprise ISP and network-services provider with APNIC-visible autonomous system records, portable IPv6 resources, RPKI-valid originated prefixes, NPIX peering, and an active website selling corporate fiber, public IPs, managed services, enterprise Wi-Fi, campus networks, hospitality networks, web/cloud services, and network consulting. It does not show, with equal clarity, a large national access network, independently controlled international capacity, a fully documented ownership chain, or a clean one-to-one relationship between brand, legal entity, registry holder, and successor network identity. That gap is the core economic fact. IBSS Nepal’s value is less the value of a mass-market broadband brand and more the value of a semi-visible infrastructure intermediary: a firm that can package scarce public IP space, local peering, last-mile execution, support labor, and vendor integration into business-grade connectivity in a market where upstream bandwidth, regulatory approvals, foreign-exchange permission, tax disputes, and supplier concentration can dominate unit economics. APNIC records associate AS18395 and AS23672 with “I.B.SYS. Solution Nepal Pvt. Ltd.” and ORG-IN13-AP / “IBSS Nepal,” while the active website presents IBSS Nepal Pvt. Ltd. as a corporate broadband and network-solutions provider.

The evidence supports a thesis with two parts. First, IBSS Nepal appears to be economically positioned as a niche enterprise-access and managed-network provider rather than a scale consumer ISP. Its own materials emphasize corporate-friendly SLAs, dedicated public IP addresses for SME and corporate plans, business fiber, point-to-point leased-line language, managed monitoring, hospitality Wi-Fi, campus connectivity, enterprise networks, cybersecurity, and data-center support services. Its FAQ says service is “only in Kathmandu,” while the home page says coverage is inside Kathmandu Valley and expanding across the country, a common ambiguity for operators whose commercial reach exceeds their physically owned access footprint.

Second, the network record shows that visible internet-number resources confer credibility but not full autonomy. AS23672 is currently the more important live object: BGP.tools records it as active, originating several IPv4 prefixes and one IPv6 allocation, with valid RPKI for the listed routes, and with visible upstream/peer dependency on AS151396 Sajilo Net. NPIX lists IBSS Nepal Pvt. Ltd. as a full member on AS23672 with a 10 Gbps connection at NPIX DataHub, open peering policy, and no route-server client status. Historical and adjacent records, however, introduce ambiguity: AS18395 is still in APNIC’s IBSS registry context but Hurricane Electric indicates it has not been visible in the global routing table since January 2024; PeeringDB still carries AS56196 as “IBSS Nepal Internet” at an NPIX DataHub exchange point; and older IBSSNET-NP abuse/role records are mixed with Airwave contact information.

Identity: a brand, a registry entity, and a set of names

The canonical operating target is best described as IBSS Nepal, operating publicly as IBSS Nepal Pvt. Ltd. and appearing in APNIC registry material as ORG-IN13-AP / “IBSS Nepal” and in aut-num descriptions as “I.B.SYS. Solution Nepal Pvt. Ltd.” The current APNIC WHOIS record for AS18395 lists as-name: IBSYS-AS-AP, description “I.B.SYS. Solution Nepal Pvt. Ltd.,” country Nepal, organization ORG-IN13-AP, abuse contact abuse@ibssnepal.com.np, and a Kathmandu address at Ram Mandir Marg, Battisputali. The APNIC organization object identifies “IBSS Nepal” as a local internet registry, with email info@ibssnepal.com.np and the same phone and address pattern. AS23672 carries the same APNIC identity.

The name-space is not clean. NPIX’s 2013 announcement welcomed “IBSS Nepal Pvt. Ltd.” and described “Integrated Business System Solution Nepal Pvt. Ltd.” as a Kathmandu ISP providing internet through wireless and fiber. JobsNepal describes IBSS Nepal Pvt. Ltd. as formed in 2007 and as part of a “syndicate of independent business groups,” with ambitions in networking, wireless internet services, telecom solutions, and IP phone business. LinkedIn presents “IBSS Nepal Pvt. Ltd.” as an ISP and managed network service provider for the corporate sector, founded in 2007, headquartered in Kathmandu, with 11–50 employees, but also labels the company type as “Partnership.” These are not fatal contradictions, but they matter economically because registry control, operating control, and shareholder control can diverge in small ISP markets.

The strongest working identity is therefore: IBSS Nepal is a Kathmandu-based enterprise ISP and network-services operator, active under the IBSS Nepal Pvt. Ltd. brand, using APNIC-visible resources linked to I.B.SYS. Solution Nepal Pvt. Ltd. and ORG-IN13-AP. The unresolved issue is whether “IBSS Nepal,” “IBSS Nepal Pvt. Ltd.,” “I.B.SYS. Solution Nepal Pvt. Ltd.,” and older “IBSSNET-NP / IBSS Nepal Internet” records refer to a single continuous corporate owner, a brand evolution, a registry clean-up, or a relationship with another operator such as Airwave. That distinction would change the economics: a continuous owner has resource continuity and accumulated customer equity; a successor brand may have inherited useful number resources without full customer continuity; a reseller or affiliated brand may depend more heavily on upstream and parent infrastructure than its public website implies.

What the company sells: business access plus managed ambiguity

IBSS Nepal’s public offer is not a pure access product. The home page markets “IBSS Internet Services” with corporate-friendly SLAs, multiple redundancies, backup plans, global terminations, domestic peering, international peering with tier-1 network, and support systems. It highlights 24-hour fiber broadband, high-speed office broadband, public IP addresses for SME and corporate plans, quick installation, 24/7 support, engineering staff, and a wide range of products from broadband and intranet to web hosting, hardware, and networking devices. This is a service bundle rather than a commodity bandwidth proposition.

The dedicated broadband page pushes the same bundle further upmarket. It addresses corporate customers, large enterprises, and MNCs; uses leased-line vocabulary; promises dedicated bandwidth, symmetrical upload and download speeds, network redundancy, proactive monitoring, managed services, static IP, bundled voice lines, and Microsoft Office 365 tools. The economic significance is that IBSS is trying to convert bandwidth from a commodity into a managed service contract. A plain residential ISP competes mainly on Mbps, price, bundled TV, and installation speed. A corporate ISP can also charge for uptime, static addressing, last-mile resilience, firewall/routing design, monitoring, account management, and reduced operational hassle.

The enterprise-solutions page widens the addressable market into hotels, colleges, academic institutions, and enterprise networks. It offers hospitality Wi-Fi for star hotels, Campus Connect for academic institutions, enterprise network design using vendors such as Extreme Networks, Cisco, and Juniper, and cybersecurity services. The managed-services page adds network monitoring, network-level support, service relationship management, project oversight, data-center support, and network consultancy. These pages do not prove that IBSS owns a large data center or a national fiber backbone; they prove that IBSS sells itself as the party that can assemble connectivity, equipment, support labor, and vendor products into an operational service.

The customer interface reinforces this economics. The “Getting Started” page says the technical team installs an ONT at the customer premises, the customer connects a router, and a portal/mobile app is used for bills, data usage, plan upgrades, and support tickets. The FAQ says IBSS offers high-speed internet, dedicated corporate bandwidth, and customized networking solutions; it currently provides services only in Kathmandu; technical issues are targeted for resolution within two hours; installation takes one to two business days; routers are not included in the installation package; IBSS applies a fair-usage policy; and payments include online payments, bank transfers, eSewa, and Khalti. This is operationally important because it reveals a hybrid of enterprise service and mass-ISP process: portal billing and FUP imply standardized access economics, while dedicated bandwidth and SLA language imply premium service segmentation.

Geography and network layer

The public footprint is concentrated in Kathmandu. The website shows a Kathmandu Valley coverage map and says IBSS has large network coverage inside Kathmandu Valley, while the FAQ states that service is currently only in Kathmandu. NPIX’s current member listing places IBSS’s exchange connection at NPIX DataHub in Kathmandu, and APNIC contact addresses place the organization in Battisputali, Kathmandu. Older NPIX material from 2013 described IBSS as a Kathmandu ISP using wireless and fiber. Together, these sources point to a metropolitan enterprise-access operator, not a proved nationwide fixed-access platform.

The network-layer footprint is more substantial than a simple web-hosting shop but smaller than Nepal’s top consumer ISPs. AS23672 is active and originates multiple IPv4 prefixes and a /32 IPv6 allocation. BGP.tools classifies it as an “Eyeball” network, ranks it inside Nepal for estimated eyeballs, unique domains, originated IPv4 space, and originated IPv6 space, and shows current origination of five /24 IPv4 blocks plus one /32 IPv6 allocation. The APNIC IPv6 record shows 2402:3020::/32 as an allocated portable IPv6 resource for IBSYS-NP, associated with I.B.SYS. Solution Nepal Pvt. Ltd. This is real network infrastructure evidence: it means IBSS is not merely a reseller with no routing identity.

Yet the layer evidence is uneven. AS18395, the ASN given in the user’s starting evidence, remains in APNIC’s public context under the same IBSS/I.B.SYS organization, but Hurricane Electric indicates that AS18395 has not been globally visible since January 4, 2024, and had only one IPv4 prefix in the historical view. The economically relevant inference is not that AS18395 is worthless; it is that the live production network appears to have shifted toward AS23672 and possibly AS56196-related records. In small ISP markets, inactive ASNs can still have option value, documentation value, or legacy customer value, but live BGP visibility is what reveals actual traffic-bearing production.

AS56196 adds a second layer of ambiguity. PeeringDB lists “IBSS Nepal Internet” on AS56196, with public peering at NPIX DataHub and IPv4/IPv6 addresses, while the current NPIX member page lists IBSS Nepal Pvt. Ltd. as AS23672 at NPIX DataHub with the same IPv4 exchange address and says IPv6 is not enabled and the route-server client flag is “No.” Hurricane Electric shows AS56196 as visible, with two originated prefixes, RPKI-valid status, and observed peers including Ncell and Sajilo Net. This could be a stale PeeringDB record, a migration from AS56196 to AS23672, dual-AS operation, or a downstream/customer-routing relationship. The economic meaning is clear even if the corporate fact is unresolved: external databases can overstate or mislabel operational control, so counterparties should price IBSS’s network capability by live BGP, NPIX, APNIC, and contract evidence together, not by any one database.

Visible internet-number resources as economic assets

IBSS Nepal’s visible number resources matter because they are scarce coordination assets. ASNs, route objects, RPKI-valid prefixes, and public IP assignments give a firm a place in the global routing system. They also make the firm legible to customers that need static IPs, VPNs, hosted services, whitelisting, firewall rules, point-to-point connectivity, and remote monitoring. IBSS’s website explicitly advertises dedicated public IP addresses for all SME and corporate plans. That is not just a technical feature; it is a monetizable complement to enterprise connectivity, especially when IPv4 addresses are scarce and corporate customers need stable addressing for inbound services, VPN endpoints, CCTV/NVR access, payment systems, office servers, remote administration, or cloud access controls.

The IPv4 evidence suggests a modest but meaningful resource base. BGP.tools lists AS23672 as originating five /24 IPv4 prefixes and one /32 IPv6 prefix, with the listed routes carrying valid RPKI certification. IPinfo and DB-IP mirrors show AS23672 associated with roughly 1,280 to 2,048 IPv4 addresses depending on counting method and route visibility, while some historical or secondary records attach Airwave or other labels to certain ranges. The exact address count is less important than the economic structure: a few /24s are enough to support a profitable enterprise ISP or managed-access niche, but not enough to make public IP allocation an unconstrained product. Public IPs can become a margin lever because the operator can ration them, bundle them with higher-tier plans, or reserve them for customers with greater willingness to pay.

RPKI validity is an underappreciated quality signal. It does not prove customer satisfaction, network diversity, or ownership clarity. It does show that the resource holder or its routing administrator has created route-origin authorization consistent with the visible announcements. In a market where small networks often run on inherited records, stale route objects, and third-party operational help, valid RPKI lowers one category of operational risk: accidental or malicious route-origin conflict. For corporate buyers, the value is indirect. A valid RPKI posture will not make a weak last mile reliable, but it improves the credibility of the provider’s routing hygiene and reduces the probability that traffic is rejected by networks enforcing route-origin validation.

Local exchange presence has a different economic role. NPIX says its purpose is to help ISPs keep local traffic local, and the current member page shows IBSS Nepal Pvt. Ltd. as a full member with a 10 Gbps connection at NPIX DataHub. Local peering can lower upstream transit costs, reduce latency to domestic services, improve resilience for in-country traffic, and make a small ISP more credible to enterprise customers whose users consume local content, government services, payment gateways, domestic cloud, and other Nepal-hosted resources. But NPIX also lists IBSS as not a route-server client. That may mean IBSS relies on bilateral sessions rather than the route server, or that the public listing is incomplete; either way, an open peering policy does not automatically equal full domestic reach.

Supplier dependence: upstreams, facilities, equipment, and foreign exchange

IBSS Nepal’s economics are supplier-heavy. The live AS23672 record on BGP.tools shows AS151396 Sajilo Net as its visible upstream/peer for IPv4 and IPv6. Sajilo Net itself is a Nepal ISP whose BGP.tools profile shows it peering with several networks and using WorldLink International Transit Services as upstream; IPinfo similarly lists AS151396 peers including AS23672 and upstream AS45274 WorldLink International Transit Services. If this live route view reflects IBSS’s current production dependence, then IBSS’s wholesale bargaining position is not that of a large national carrier buying diverse international transit directly at scale. It is closer to a downstream or lateral customer of another domestic ISP/network-services provider, with exposure to that provider’s transit quality, payment discipline, routing policy, and capacity planning.

The APNIC import/export policy is broader than the live BGP view. AS23672’s APNIC WHOIS record lists imports from AS135327, AS4613, AS58504, and AS45845 and exports to those ASes. Those names suggest historical or intended routing relationships with Asianet, Mercantile, TechMinds, and NIIG/related Nepal networks, but the current BGP.tools live view emphasizes Sajilo. This divergence is common: IRR and WHOIS policy objects can survive after commercial arrangements change. Economically, stale policy data can create a false impression of transit diversity. For a buyer of IBSS service, the important question is not whether old route policy objects name several networks; it is how many paid upstreams are active, capacity-provisioned, contractually committed, and independently routed today.

The facility dependency is also visible. NPIX lists IBSS’s exchange connection at NPIX DataHub, and DataHub markets itself as a Nepal cloud hosting and data-center services provider with colocation, backup, disaster recovery, DNS, firewall-as-a-service, object storage, private cloud, public cloud, and related services. A 10 Gbps NPIX port at DataHub is useful infrastructure, but it also means that IBSS’s peering economics depend on the exchange fabric, the facility, cross-connects, power, and physical access. If IBSS sells data-center support or enterprise connectivity around that ecosystem, the company can capture service margin without owning the facility. That is not a weakness by itself; it is a capital-light model. The risk is that the customer may perceive “data center solutions” as owned infrastructure when the public evidence supports a support/integration role more strongly than facility ownership.

Equipment and vendor dependence are embedded in the service offer. IBSS names Extreme Networks for switching and Cisco and Juniper for routing and firewall in its enterprise-network product. That can be valuable for quality perception, but it imports procurement exposure: foreign-currency hardware costs, lead times, spares, support contracts, licensing, software subscriptions, and certification labor. For a small provider, the gross margin on managed networking can be attractive when equipment resale and support are bundled with monthly service, but procurement leverage is limited. The provider must either pass equipment costs through to customers, hold inventory, or standardize designs tightly enough to avoid balance-sheet strain.

The largest supplier risk in Nepal is not vendor brand; it is international bandwidth and the state’s role in foreign-exchange clearance. In May 2024, AP reported broadband disruption across much of Nepal after Indian vendors from whom many private Nepali operators source bandwidth stopped service because of payment defaults. Private ISPs said they could not pay Indian bandwidth vendors because the government had not provided foreign currency access while tax disputes remained unresolved; AP quoted Wlink saying its upstream provider disconnected internal links due to nonpayment and inability to obtain government permission for foreign exchange. Kantipur reported before the disruption that ISPAN said about 70% of Nepal’s international bandwidth came from Airtel and that payments had been blocked for months amid disputes over maintenance-fee royalty and RTDF obligations.

For IBSS Nepal, no public source reviewed here proves a specific 2024 outage or nonpayment event at the company. The sector event nevertheless changes how its economics should be read. A small ISP can present redundancy, peering, and support while still being exposed to upstream payment chains and regulatory bottlenecks beyond its control. When the binding constraint is foreign-exchange recommendation, tax interpretation, or a large upstream’s receivables tolerance, the quality of the last-mile crew matters less than the credit and regulatory position of the upstream supply chain. This is the central lesson: in Nepal, outsourced connectivity is not a simple input; it is a political-financial dependency with outage characteristics.

Revenue logic and margin pressure

IBSS Nepal’s probable revenue logic is a three-part bundle. The first part is recurring internet access: dedicated or semi-dedicated fiber broadband sold to SMEs, offices, enterprises, colleges, and hotels. The second part is attachment revenue: static/public IPs, voice lines, cloud or hosting, Microsoft tools, cybersecurity, managed Wi-Fi, hardware, firewall/routing, portal billing, monitoring, and support. The third part is project revenue: campus networks, hospitality Wi-Fi design, enterprise LAN/WAN, data-center support, and consultancy. The website directly supports all three categories, though it does not disclose prices, customer counts, revenue, or margins.

The margin stack is likely uneven. Commodity bandwidth has the worst price dynamics because large Nepali ISPs can spread upstream capacity, advertising, billing systems, installation teams, and customer support over far more customers. IBSS’s better margin opportunities are in higher-touch enterprise support, managed Wi-Fi, static IP assignments, network monitoring, and customer-specific design. These services are less comparable by headline Mbps. They also create relationship-specific switching costs: an enterprise that has firewall rules, public IP whitelisting, VPN endpoints, on-premises ONT placement, Wi-Fi controllers, switch configurations, VLANs, monitoring dashboards, and ticketing history with one provider does not switch as easily as a residential household choosing a cheaper annual package.

Pricing power therefore comes less from monopoly access and more from operational embeddedness. IBSS can charge above commodity access rates when the buyer values uptime, local engineering response, static addressing, network design, and a single accountable party. Its FAQ’s two-hour support target and one-to-two-business-day installation window are commercial signals: the company is selling reduced downtime and reduced coordination cost, not just raw bandwidth. But this pricing power has a ceiling. Enterprise buyers in Kathmandu can benchmark against larger ISPs and systems integrators, and large customers may be able to multi-home, negotiate direct service with bigger carriers, or demand penalty-backed SLAs.

Gross-margin pressure comes from six places. Upstream transit and domestic backhaul consume recurring cost. Field installation and repair consume labor and vehicles. ONTs, routers, switches, firewalls, optics, cables, and spares introduce imported-hardware exposure. Power, batteries, UPS systems, and facility/cross-connect fees add fixed cost. Support and account management raise labor intensity, especially for corporate customers. Finally, regulatory fees, royalties, RTDF obligations, tariff approvals, tax disputes, and foreign-exchange permissions create working-capital risk. Nepal’s Telecommunications Act framework has been interpreted as requiring ISPs to pay royalty and RTDF, and Republica reported in 2025 that ISPs must pay 4% of revenue as royalty and 2% as RTDF, with a dispute over whether maintenance fees are included.

The regulatory cost is not merely a percentage. It can become an input-supply shock. New Business Age reported that the government suspended foreign-currency recommendations for international bandwidth payments while royalty and RTDF dues were unresolved, and that Airtel halted services in May 2024 due to unpaid fees from Nepali ISPs. This mechanism turns a tax interpretation into a network-quality event. For a provider like IBSS, whose public materials emphasize redundancy and support, the risk is that even good local operations may be undermined by upstream payment blockages at the sector level.

Competition, substitutes, and buyer power

Nepal’s ISP market is crowded. SAMENA’s 2025 industry update, citing Nepalitelecom, says Nepal had 107 licensed ISPs, that many operators have fewer than 20,000 customers, and that NTA was considering ISP mergers because the number of providers had become difficult to manage. The same source says WorldLink leads with over 10 lakh customers, Nepal Telecom and DishHome have over 3 lakh customers, and other top operators average over 2 lakh customers. HimalPress, citing NTA, reported that mobile broadband still accounts for more than 89% of Nepal’s broadband subscriptions, while fixed wired broadband is about 10.65%, with about 3.1 million fixed wired subscriptions and ISP-driven FTTH.

This structure matters for IBSS. If the company had been trying to compete as a mass consumer ISP, it would face large-player scale advantages in marketing, international bandwidth procurement, device purchasing, TV/content bundles, call centers, and geographic density. Its public posture instead looks like a niche strategy: corporate broadband, SME plans, colleges, hotels, and managed networking. That strategy is rational in a crowded market because the operator can trade scale for service intensity. A small ISP can survive if it owns relationships in a dense business geography, responds faster than large competitors, and bundles integration work that larger ISPs treat as outside their core product.

Buyer power differs by segment. Small offices and SMEs have moderate buyer power because they can compare fixed broadband packages and may not need deep customization. Larger enterprises, hotels, and campuses have stronger bargaining power on price but also higher switching costs once the provider controls LAN design, Wi-Fi deployment, public IP allocation, and monitoring. Colleges and hotels are attractive because guest/user density creates high bandwidth demand and support sensitivity, but these customers can also demand service credits, redundancy, and on-site response. IBSS’s public promise to contact enterprise prospects within 24 hours and provide tailored solutions indicates a sales model built around consultation rather than self-service package selection.

Substitutes include direct service from larger ISPs, Nepal Telecom enterprise products, mobile broadband for backup or small offices, fixed wireless, other managed-service providers, systems integrators, and in some cases cloud-hosted applications that reduce the need for static on-premises IP infrastructure. However, these substitutes are imperfect. Mobile broadband can back up an office but cannot fully replace symmetrical business fiber for many enterprises. A systems integrator can design LAN/Wi-Fi but may not control public IPs, routing, or last-mile support. A large ISP may provide better upstream diversity but weaker bespoke service for a small or mid-market enterprise. IBSS’s economic niche lies in the cracks between these substitutes.

Ownership, financing, management, and control context

Public ownership evidence is thin. The active website gives contact details and product pages but no shareholder register, audited financials, board, capital history, or M&A record. LinkedIn lists the company as founded in 2007, 11–50 employees, and type “Partnership,” while JobsNepal describes formation in 2007 and a “syndicate of independent business groups.” Tracxn describes IBSS Nepal as an unfunded Kathmandu company founded in 2007 and providing wireless/fiber optic internet, but that is a secondary aggregator, not a filing. No public record reviewed here proves external equity financing, debt financing, acquisition, sale, or a named controlling shareholder.

The control question is complicated by Airwave-linked legacy records. An APNIC abuse role for IBSSNET-NP shows “IBSS Nepal Pvt. Ltd - network administrator” but lists abuse@airwave.com.np and kniroula@airwave.com.np in the abuse/validation context. Separate AS23866 material shows IBSSNET-NP / “IBSS Nepal Internet” as inactive in some mirrors, while another APNIC-adjacent record associates AS23866 with Airwave Pvt. Ltd. These facts do not prove that Airwave owns IBSS Nepal, that IBSS owns Airwave resources, or that there was an M&A event. They do prove that older registry and abuse-contact material intertwines IBSSNET-NP and Airwave in a way that should be resolved before assigning control value to legacy ASNs or IPv4 blocks.

Economically, each interpretation leads to a different model. If IBSS is independent and simply has stale Airwave-linked records, then the issue is record hygiene and reputational due diligence. If IBSS operates as a brand or affiliate within a broader Airwave/Sajilo/partner network chain, then its cost base and resilience depend heavily on related-party infrastructure and upstream contracts. If IBSS provides routing, address, or managed services for downstream networks whose records retain older descriptors, then the firm may have a wholesale or network-management business not fully visible on its public website. If the resources were transferred or re-papered around 2025, as suggested by recent APNIC organization updates, then the most important question is whether customer contracts, IP rights, and routing control moved together.

The APNIC records were modified recently: AS18395 and AS23672 show last modification in March 2026, and ORG-IN13-AP shows recent organization-object changes in 2025. This can mean ordinary registry maintenance, resource clean-up, abuse-contact validation, control migration, or preparation for operational changes. Without corporate filings, the safest conclusion is not that IBSS changed ownership, but that its public registry layer is being actively maintained. In a small ISP, active registry maintenance is itself meaningful because it implies someone has operational access to APNIC objects, maintainer credentials, abuse contacts, and route-authentication processes.

Regulatory and service-quality risk

IBSS operates in a regulated telecom environment. NTA’s license-fee page lists an Internet including e-mail service license fee of NRs 300,000 and renewal fee of NRs 270,000. An NTA MIS report from Ashoj 2076 shows “I.B.Sys.Solution Nepal Pvt. Ltd., Sinamangal, Kathmandu” renewing an Internet with e-mail service license, and the same MIS appendix lists IBSS Nepal Pvt. Ltd. with 350 wireless, 759 fiber, and 1,109 total internet subscribers as of that 2019 reporting period. That older subscriber count should not be treated as current, but it is useful as a scale anchor: IBSS was publicly recorded as a small operator relative to WorldLink, Subisu, Vianet, and Classic Tech in that period.

IBSS has appeared in at least one public regulatory-payment complaint. The Himalayan Times reported in 2018 that NTA warned eight ISPs, including “IBSS Nepal of Old Baneshwor,” to clear outstanding royalty fees or face legal action. This is dated and does not prove current delinquency. It does show that IBSS has been inside the same royalty-compliance regime that later became a sector-level dispute over maintenance fees, RTDF, and foreign-exchange recommendations.

No public evidence reviewed here shows an IBSS-specific major outage, cyber incident, court judgment, license cancellation, customer class action, procurement dispute, or large abuse event. That absence should be interpreted carefully. Small ISPs often leave little searchable public trace unless the regulator names them, customers post complaints, or routing/security events are externally indexed. The absence of public incidents is not proof of high service quality; it is only absence of visible negative signals in the sources reviewed.

License fragility is a sector risk. Republica reported in 2024 that NTA revoked the licenses of C Data Communication and Life Net, one for not operating according to terms and one for failing to initiate renewal. Another report described NTA revoking licenses of United Telecom, Max Net Solution, and Chitwan Network for renewal failures. These were not IBSS cases, but they illustrate the regulator’s ability to remove inactive or noncompliant operators. In a market with many small ISPs, license renewal and dues compliance are not administrative afterthoughts; they are part of the business model.

Infrastructure-service ambiguity as a business model

The most interesting feature of IBSS Nepal is not that it is obscure. It is that its obscurity is economically functional. The company’s public website lets it look like a corporate ISP, a managed-service provider, an enterprise Wi-Fi integrator, a web/cloud service provider, and a data-center support firm. Its registry layer lets it look like a real network operator, with ASNs, IP resources, RPKI-valid routes, and exchange presence. Its dependency layer suggests it may rely heavily on upstream domestic providers, facility providers, and vendor ecosystems. Those three surfaces are not contradictory. They are the normal production function of a small infrastructure-service company.

This ambiguity creates commercial flexibility. IBSS can sell to a hotel as a Wi-Fi and bandwidth solution, to a college as campus connectivity, to an SME as static-IP fiber, and to an enterprise as network support. It can use public IP resources and BGP visibility as trust signals while outsourcing parts of international capacity and facility infrastructure. It can compete against larger ISPs by offering more customized support and against systems integrators by bundling actual connectivity. In other words, the firm monetizes coordination costs. Its product is not only internet access; it is the reduction of the customer’s need to coordinate between ISP, router vendor, firewall vendor, Wi-Fi installer, data-center provider, and support desk.

The same ambiguity creates diligence risk. A customer or investor must ask which parts of the service are owned, leased, resold, integrated, or merely arranged. “Domestic peering” is supported by NPIX evidence; “international peering with tier-1 network” is less directly proven by live BGP for AS23672, which visibly depends on Sajilo Net. “Data Center Solutions” are presented as support services rather than owned data-center facilities. “Large network coverage” inside Kathmandu Valley is plausible, but the FAQ’s “only in Kathmandu” limits national interpretation. “Dedicated public IP addresses” are supported by the company’s public claim and by visible number resources, but the exact IP allocation policy and utilization are unknown.

Alternative hypotheses and what each would change

The base-case hypothesis is that IBSS Nepal is an independent Kathmandu enterprise ISP and managed-network provider with live routing on AS23672, local peering at NPIX DataHub, modest IP resources, and upstream dependence on Sajilo Net or related domestic suppliers. Under this model, the company’s economics are viable if it maintains dense enterprise accounts, converts public IP and support into premium pricing, and avoids a commodity price war with larger FTTH providers. The main constraints are procurement leverage, upstream concentration, regulatory dues, and working-capital exposure.

A second hypothesis is that IBSS is a successor or cleaned-up continuation of older IBSSNET-NP / IBSS Nepal Internet resources, with AS18395 and AS56196 representing legacy or transitional routing identities. This would explain why AS18395 remains in APNIC records but is not live, why PeeringDB still shows AS56196 at NPIX, and why current NPIX lists AS23672. Under this model, the economic asset is continuity: the company may have accumulated customer relationships, regulatory permissions, and address resources across several network identities. The risk is documentation friction: stale databases can confuse customers, peers, abuse reporters, and regulators.

A third hypothesis is that IBSS’s registry resources or operating rights are entangled with Airwave or another partner. The Airwave-linked abuse contacts in older IBSSNET-NP material and secondary IP-range labels make this plausible but not proven. If true, the company’s economics would depend on related-party arrangements: Who owns the IPv4 space? Who controls route objects and RPKI? Who pays APNIC fees? Who signs upstream transit contracts? Who bears outage penalties? Related-party infrastructure can be efficient if it lowers cost, but risky if customers do not know where accountability sits.

A fourth hypothesis is that IBSS has only a small owned access footprint and relies heavily on upstream/backhaul/facility partners while selling a high-touch managed service wrapper. This is common and commercially rational. It would mean that the company’s durable advantage is not hard infrastructure scale but customer intimacy, engineering responsiveness, static-IP capability, and local business relationships. Under this model, gross margin is protected by services rather than bandwidth, and the main threat is larger ISPs moving downmarket into managed enterprise support.

A fifth hypothesis is that the public footprint understates IBSS’s business because many enterprise service contracts, campus networks, or managed Wi-Fi deployments are not publicly named. The website’s hotel, college, enterprise, and campus offerings could represent real deployments that do not appear in press releases. If true, public BGP scale would understate economic scale because managed LAN/Wi-Fi and support revenue can be meaningful without large originated address space. The watchpoint would be hiring, partner certifications, project references, and named customer case studies rather than BGP prefixes alone.

What the evidence proves, suggests, and leaves unresolved

The evidence proves that IBSS Nepal is an active public-facing corporate broadband and network-services brand in Kathmandu; that APNIC maps AS18395 and AS23672 to I.B.SYS. Solution Nepal Pvt. Ltd. and ORG-IN13-AP / IBSS Nepal; that AS23672 is live and originates RPKI-valid prefixes; that IBSS Nepal Pvt. Ltd. is listed as a full NPIX member with a 10 Gbps DataHub connection; that the company markets public IPs, fiber business internet, enterprise Wi-Fi, campus networks, cybersecurity, managed services, and data-center support; and that older public regulatory material recorded IBSS as a small ISP and license renewer in Nepal.

The evidence suggests, but does not prove, that IBSS’s current production network is centered on AS23672 rather than the starting AS18395; that it has moved through or alongside AS56196/IBSS Nepal Internet records; that it has meaningful supplier dependence on domestic upstreams; that its public IP pool is commercially valuable but limited; that its address and registry history may involve stale Airwave-linked records or a legacy relationship; and that its market strategy is niche enterprise service rather than national mass broadband scale.

The evidence leaves unresolved the legal shareholder identity, audited financial condition, exact customer count today, current license status beyond public indicators, exact upstream contracts, whether all announced resources are owned or managed on behalf of others, whether Airwave-linked records reflect stale data or economic control, whether the company owns any substantial fiber plant outside Kathmandu Valley, and whether its claimed redundancy includes independently contracted international transit or only upstream-provided redundancy. Those unresolved facts are not peripheral. They determine whether IBSS should be valued as a small asset-owning ISP, a managed-services wrapper on partner networks, a successor to older number resources, or a hybrid of all three.

Evidence ledger

APNIC WHOIS for AS18395. Primary registry evidence tying the starting ASN to IBSYS-AS-AP, “I.B.SYS. Solution Nepal Pvt. Ltd.,” country Nepal, ORG-IN13-AP / IBSS Nepal, Kathmandu address, and IBSS abuse contacts.
APNIC WHOIS for AS23672. Primary registry evidence showing the same IBSS/I.B.SYS organization, imports/exports, abuse contact, and recent modification date for the currently more visible ASN.
APNIC IPv6 WHOIS for 2402:3020::/32. Primary resource evidence showing an allocated portable IPv6 block, netname IBSYS-NP, and ORG-IN13-AP association.
APNIC/RDAP mirror for AS23672. Secondary but detailed RDAP evidence listing ORG-IN13-AP, contact data, abuse validation, and IP ranges associated with AS23672.
BGP.tools AS23672. Live routing evidence showing active status, originated IPv4 and IPv6 prefixes, valid RPKI, eyeball classification, rankings, and visible upstream/peer relationship with Sajilo Net.
NPIX current member page for IBSS Nepal Pvt. Ltd. Primary exchange evidence showing AS23672 as a full member, open peering policy, join date, 10 Gbps DataHub connection, IPv4 exchange address, no route-server client status, and IPv6 not enabled in that listing.
Hurricane Electric BGP Toolkit for AS18395. Live/historical BGP evidence indicating that AS18395 has not been globally visible since January 2024 and previously showed one IPv4 prefix.
Hurricane Electric BGP Toolkit for AS56196. Routing evidence for the adjacent IBSS Nepal Internet ASN, including originated prefixes, RPKI-valid status, and observed peers.
PeeringDB AS56196 / IBSS Nepal Internet. User-maintained interconnection database evidence showing older or parallel IBSS Nepal Internet peering records at NPIX DataHub, useful mainly for identifying ambiguity and possible staleness.
APNIC role object for IBSSNET-NP. Primary registry-adjacent evidence showing older IBSS Nepal administrator language with Airwave abuse-contact fields, central to the control-ambiguity issue.
APNIC/WHOIS mirror for AS23866 / Airwave. Secondary registry evidence indicating that older IBSSNET-NP / IBSS Nepal Internet records are entangled with Airwave Pvt. Ltd. in public databases.
IBSS Nepal home page. Primary operating evidence for corporate broadband positioning, SLAs, redundancy claims, Kathmandu Valley coverage, dedicated public IPs, 24/7 support, web hosting, intranet, hardware, and networking services.
IBSS Dedicated Broadband page. Primary product evidence for corporate fiber, leased-line language, dedicated bandwidth, symmetrical speeds, redundancy, monitoring, managed services, static IPs, and bundled tools.
IBSS Enterprise Solutions page. Primary product evidence for hospitality Wi-Fi, Campus Connect, academic institutions, enterprise networks, Cisco/Juniper/Extreme vendor references, and cybersecurity.
IBSS Managed Services page. Primary product evidence for monitoring, network-level support, service relationship management, project oversight, data-center support, and network consultancy.
IBSS Getting Started page. Primary operations evidence for ONT installation, customer router connection, portal billing, data usage, plan upgrades, support tickets, mobile app, and support channels.
IBSS FAQ. Primary evidence for Kathmandu-only service statement, service categories, two-hour support target, installation timing, router policy, FUP, payment methods, and refund policy.
IBSS LinkedIn profile. Semi-public company-channel evidence for founding year, employee-size range, headquarters, specialties, corporate ISP positioning, and recent B2B marketing hiring.
JobsNepal IBSS profile. Semi-public channel evidence for the “syndicate of independent business groups” language, 2007 formation, and product ambitions in networking, wireless internet, telecom solutions, and IP phone business.
NPIX 2013 announcement. Historical exchange evidence that IBSS Nepal joined NPIX and was described as a Kathmandu ISP providing wireless and fiber internet.
NTA MIS Ashoj 2076 PDF screenshots. Regulatory/statistical evidence that I.B.Sys.Solution Nepal renewed an Internet with e-mail service license in 2019 and that IBSS Nepal was listed with 1,109 total subscribers in that period.
NTA license-fee page. Regulatory evidence for Nepal’s Internet including e-mail service license fee and renewal fee.
Himalayan Times 2018 NTA warning. Public regulatory-risk evidence that NTA warned IBSS Nepal and other ISPs to clear royalty dues.
Kantipur April 2024 ISPAN/bandwidth dispute report. Local press evidence for Airtel concentration, foreign-exchange recommendation blockage, maintenance-fee royalty/RTDF dispute, and potential internet disruption.
Associated Press May 2024 Nepal broadband disruption. International press evidence that Indian vendors stopped bandwidth service to private Nepali operators due to payment defaults and foreign-exchange constraints.
New Business Age November 2024 royalty dispute report. Local business press evidence for Supreme Court-linked royalty/RTDF dispute, installment requests, suspended foreign-currency recommendations, and Airtel service impact.
Republica February 2025 Vianet dues report. Local press evidence that ISPs face 4% royalty and 2% RTDF obligations and that maintenance-fee applicability was disputed.
SAMENA/Nepalitelecom 2025 ISP merger report. Market-structure evidence for 107 licensed ISPs, many small operators below 20,000 customers, top-player scale, and NTA merger interest.
HimalPress/NTA broadband subscriber report. Market evidence for Nepal’s mobile-broadband dominance, fixed wired share, FTTH connection count, and ISP role in fixed broadband.
Republica and other license-revocation reports. Sector-risk evidence that NTA can revoke ISP licenses for non-operation or renewal failure, relevant to small-operator regulatory risk even though not IBSS-specific.
Sajilo Net BGP/IPinfo records. Supplier-context evidence for AS151396’s network role, peers, upstream relationship with WorldLink International Transit Services, and relationship with AS23672.
DataHub public site and NPIX facility record. Facility-context evidence that IBSS’s NPIX connection is at DataHub and that DataHub markets cloud hosting, colocation, DNS, backup, and other data-center services.

Watchpoints

AS23672 upstream diversity. A move from a single visible Sajilo Net dependence toward multiple independently active upstreams would improve resilience and bargaining power; further concentration would increase outage and pricing risk.
AS18395 reactivation or retirement. If AS18395 becomes visible again, it may indicate dual-homing, customer migration, or resource re-use. If it is formally retired or transferred, it would clarify whether the starting ASN is legacy rather than operating infrastructure.
AS56196 / PeeringDB cleanup. Alignment between PeeringDB, NPIX, APNIC, and live BGP would reduce identity ambiguity. Continued inconsistency would remain a diligence discount for counterparties.
Airwave-linked registry resolution. Any formal evidence that Airwave records are stale, affiliated, transferred, or customer-related would materially change the control analysis of legacy resources and abuse accountability.
RPKI and prefix-origin changes. New valid ROAs, additional originated prefixes, or withdrawals would show whether IBSS is expanding, consolidating, or reconfiguring its number-resource base.
NPIX route-server status and IPv6 activation. Becoming a route-server client or enabling IPv6 at the exchange would improve local reach and technical maturity; continued non-use may indicate limited peering automation.
Named enterprise references. Public case studies for hotels, colleges, banks, campuses, or large SMEs would confirm that the company monetizes managed enterprise service rather than only advertising it.
Regulatory dues and license status. Any NTA notice, renewal failure, royalty/RTDF dispute, or tariff-approval issue would affect service continuity and working capital more than ordinary commercial competition.
Nepal foreign-exchange and upstream-payment policy. Sector-level changes in FX recommendation, bandwidth-payment clearance, or maintenance-fee taxation will directly affect IBSS-like operators even without IBSS-specific misconduct.
Consolidation pressure. If NTA-backed ISP mergers accelerate, IBSS may become an acquisition target, a forced consolidator, or a niche survivor depending on customer quality and resource control.
Public IP monetization. A tightening of IPv4 availability or a shift in customer demand for static IPs would raise the value of IBSS’s address inventory; widespread CGNAT acceptance or IPv6-only enterprise adoption would reduce that premium.
Evidence of owned fiber expansion outside Kathmandu. Verified fiber footprint beyond Kathmandu Valley would shift the company from a metropolitan niche operator toward a broader access-network story.
Data-center ownership versus integration clarity. Proof that IBSS owns facility infrastructure would raise asset intensity and potential control; proof that it only integrates third-party facilities would keep the model capital-light but supplier-dependent.
Large-player enterprise push. If WorldLink, Vianet, Subisu, Nepal Telecom, DishHome, or other large ISPs aggressively bundle managed Wi-Fi, static IPs, security, and campus support, IBSS’s service-margin niche would face direct scale competition.
Customer-visible outage record. A pattern of public complaints or uptime failures would weaken the SLA premium; a clean and verifiable service record would strengthen the case for a profitable enterprise niche.